sys-apps/hal-0.5.9.1-r3 fails to mount USB stick dmesg reports "FAT: Unrecognized mount option "flush" or missing value" This appears to be an issue with /usr/share/hal/fdi/policy/10osvendor/20-storage-methods.fdi Under the VFAT section it lists flush as an option. I suspect it should either not be there or mount (i assume) should be patched to accept it. Reproducible: Always Steps to Reproduce: Just plug in a USB stick then look at dmesg | tail sdb: Mode Sense: 43 00 00 00 sdb: assuming drive cache: write through SCSI device sdb: 1965056 512-byte hdwr sectors (1006 MB) sdb: Write Protect is off sdb: Mode Sense: 43 00 00 00 sdb: assuming drive cache: write through sdb: sdb1 sd 3:0:0:0: Attached scsi removable disk sdb usb-storage: device scan complete KDE kicks in with its dialog asking what you want to do with it but if you answer to open the drive in konquerer it fails reporting "mount: wrong fstype ..." and dmesg adds FAT: Unrecognized mount option "flush" or missing value. Mount the stick by hand as root "mount -t vfat /dev/sdb1 /media" and it works OK. Actual Results: Just plug in a USB stick then look at dmesg | tail sdb: Mode Sense: 43 00 00 00 sdb: assuming drive cache: write through SCSI device sdb: 1965056 512-byte hdwr sectors (1006 MB) sdb: Write Protect is off sdb: Mode Sense: 43 00 00 00 sdb: assuming drive cache: write through sdb: sdb1 sd 3:0:0:0: Attached scsi removable disk sdb usb-storage: device scan complete KDE kicks in with its dialog asking what you want to do with it but if you answer to open the drive in konquerer it fails reporting "mount: wrong fstype ..." and dmesg adds FAT: Unrecognized mount option "flush" or missing value. Mount the stick by hand as root "mount -t vfat /dev/sdb1 /media" and it works OK. Expected Results: It should have just mounted the device and caused kde to put up the dialog box. The click OK to the dialog and Bob's your mother's brother konquerer opens with the disk ready to go.
HAL is not passing this option down. KDE is. That HAL file is merely stating that this option is allowed for this filesystem type. Additionally, this is the recommended way to mount USB drives so that the data is immediately flushed out to the device rather then the queue the changes and result in corrupting the filesystem or potentially letting a user pull out the drive thinking the data is on there and the data hasn't been written out yet. This option has been added to the Linux kernel as of 2.6.19 and we do only mandate 2.6.17 or higher to compile HAL but we do recommend at least 2.6.19 to run. Unfortunately, you didn't include emerge --info, as required by all Bugzilla tickets so it's impossible to see your configuration info or kernel version. For reference, here's the change in the Linux kernel, http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=ae78bf9c4f5fde3c67e2829505f195d7347ce3e4
