Bug 167260 - [msdosfs] msdosfs disk was mounted the second time when the first umount was not clean and mount record still exists
Summary: [msdosfs] msdosfs disk was mounted the second time when the first umount was ...
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: Unspecified
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-24 08:10 UTC by yuri
Modified: 2017-12-31 22:32 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description yuri 2012-04-24 08:10:08 UTC 
I had the broken flash disk, and few write operations failed. And umount operation hanged. So I had to pull the USB drive out.

After checking, I mounted it again, and it works now.

However, mount command shows it mounted twice (!!!):

Filesystem   1K-blocks       Used     Avail Capacity  Mounted on
/dev/da0s1      7753672   7039040    714632    91%    /mnt/fat1
/dev/da0s1      7753672   7608888    144784    98%    /mnt/fat1

=== log of the failed disk operations ===
ugen3.3: <vendor 0xffee> at usbus3
umass0: <vendor 0xffee product 0x0100, class 0/0, rev 2.00/1.00, addr 3> on usbus3
umass0:  SCSI over Bulk-Only; quirks = 0x4100
umass0:7:0:-1: Attached to scbus7
da0 at umass-sim0 bus 0 scbus7 target 0 lun 0
da0: <FNK TECH USB CARD READER 2.33> Removable Direct Access SCSI-2 device 
da0: 40.000MB/s transfers
da0: 7580MB (15523840 512 byte sectors: 255H 63S/T 966C)
g_vfs_done():da0s1[WRITE(offset=7208050688, length=8192)]error = 5
g_vfs_done():da0s1[WRITE(offset=7208050688, length=8192)]error = 5
g_vfs_done():da0s1[WRITE(offset=7208050688, length=8192)]error = 5
g_vfs_done():da0s1[WRITE(offset=7208050688, length=8192)]error = 5
fsync: giving up on dirty
0xfffffe02a583b000: tag devfs, type VCHR
    usecount 1, writecount 0, refcount 989 mountedhere 0xfffffe01378d9c00
    flags ()
    v_object 0xfffffe024d34c658 ref 0 pages 1025
    lock type devfs: EXCL by thread 0xfffffe020d2a78c0 (pid 8156)
        dev da0s1
g_vfs_done():da0s1[WRITE(offset=7208050688, length=8192)]error = 5
fsync: giving up on dirty
0xfffffe02a583b000: tag devfs, type VCHR
    usecount 1, writecount 0, refcount 989 mountedhere 0xfffffe01378d9c00
    flags ()
    v_object 0xfffffe024d34c658 ref 0 pages 1025
    lock type devfs: EXCL by thread 0xfffffe0042809460 (pid 8168)
        dev da0s1
ugen3.3: <vendor 0xffee> at usbus3 (disconnected)
umass0: at uhub3, port 3, addr 3 (disconnected)
(da0:umass-sim0:0:0:0): lost device - 0 outstanding, 1 refs
(da0:umass-sim0:0:0:0): removing device entry
Device da0s1 went missing before all of the data could be written to it; expect data loss.
<!!! Here device mount record was left !!!>
Comment 1 Yuri Victorovich freebsd_committer freebsd_triage 2012-04-24 08:33:57 UTC 
mount -v shows more info:
/dev/da0s1 on /mnt/fat1 (msdosfs, local, writes: sync 3 async 6, reads: 
sync 37 async 0, fsid 8e00000032000000)
/dev/da0s1 on /mnt/fat1 (msdosfs, local, writes: sync 30 async 15070, 
reads: sync 37 async 6, fsid 8d00000032000000)
Comment 2 Mark Linimon freebsd_committer freebsd_triage 2012-04-25 06:09:10 UTC 
Responsible Changed
From-To: freebsd-bugs->freebsd-fs

Over to maintainer(s).
Comment 3 Eitan Adler freebsd_committer freebsd_triage 2017-12-31 08:00:50 UTC 
For bugs matching the following criteria:

Status: In Progress Changed: (is less than) 2014-06-01

Reset to default assignee and clear in-progress tags.

Mail being skipped