[Bug 35054] Re: Cannot mount FAT partitions

[Andrew Preston]

I have this problem in 9.10 (and previously 9.04).

:~$ mount
...
/dev/sdb1 on /media/Data type vfat (rw,nosuid,nodev,uhelper=devkit,uid=1000,gid=1000,shortname=mixed,dmask=0077,utf8=1,flush)

:~$ dmesg
...
[33388.654747] FAT: Filesystem error (dev sdb1)
[33388.654754]     fat_free_clusters: deleting FAT entry beyond EOF
[33388.654759]     File system has been set read-only

:~$ uname -r
2.6.31-14-generic

The issue is repeatably caused by running something like
rsync --delete -a --modify-window=1 $FROM $TO
($FROM contains a lot of folders/files/data)

For completeness, here is the dmesg output when inserting the usb drive:
:~$ dmesg
...
[   75.252227] usb 2-2: new high speed USB device using ehci_hcd and address 5
[   75.385611] usb 2-2: configuration #1 chosen from 1 choice
[   75.415907] Initializing USB Mass Storage driver...
[   75.416148] scsi5 : SCSI emulation for USB Mass Storage devices
[   75.416606] usbcore: registered new interface driver usb-storage
[   75.416610] USB Mass Storage support registered.
[   75.416729] usb-storage: device found at 5
[   75.416731] usb-storage: waiting for device to settle before scanning
[   80.412422] usb-storage: device scan complete
[   80.413012] scsi 5:0:0:0: Direct-Access     WD       3200BMV External 1.75 PQ: 0 ANSI: 4
[   80.413366] sd 5:0:0:0: Attached scsi generic sg2 type 0
[   80.418103] sd 5:0:0:0: [sdb] 625142448 512-byte logical blocks: (320 GB/298 GiB)
[   80.418658] sd 5:0:0:0: [sdb] Write Protect is off
[   80.418661] sd 5:0:0:0: [sdb] Mode Sense: 23 00 00 00
[   80.418663] sd 5:0:0:0: [sdb] Assuming drive cache: write through
[   80.419984] sd 5:0:0:0: [sdb] Assuming drive cache: write through
[   80.419990]  sdb: sdb1
[   80.462590] sd 5:0:0:0: [sdb] Assuming drive cache: write through
[   80.462595] sd 5:0:0:0: [sdb] Attached SCSI disk
...

I believe fsck to be useless for fat32 systems. Correct me if I'm wrong.

-- 
Cannot mount FAT partitions
https://bugs.launchpad.net/bugs/35054
You received this bug notification because you are a member of Kernel
Bugs, which is a direct subscriber.