kern/122961: write operation on msdosfs file system causes panic

[Dominic Fandrey]

Bruce Evans wrote:
> On Mon, 21 Apr 2008, Dominic Fandrey wrote:
> This seems to be a bug in usb (umass) or the particular usb drive...
> ...
> 
> To check that this is the bug, mount msdosfs with -o noclusterr,noclusterw
> under RELENG_7 or later (the bug also affects RELENG_6, but these mount
> options are broken in RELENG_6). ...

# mount -t msdosfs -o noatime,noexec,-L=en_GB.UTF-8,noclusterr,noclusterw 
/dev/da0 /mnt/tmp
mount_msdosfs: /dev/da0: mount option <noclusterw> is unknown: Invalid argument

It seems they are also broken under RELENG_7 from the day before yesterday.

> 
>> # mount
>> /dev/ufs/2root on / (ufs, local)
>> devfs on /dev (devfs, local)
>> /dev/ufs/2tmp on /tmp (ufs, local, soft-updates)
>> /dev/ufs/2usr on /usr (ufs, NFS exported, local, soft-updates)
>> /dev/ufs/2var on /var (ufs, local, soft-updates)
>> pid874 at mobileKamikaze:/var/run/automounter.amd.mnt on 
>> /var/run/automounter.amd.mnt (nfs)
>> /dev/msdosfs/APRIL RYAN on 
>> /var/run/automounter.mnt/msdosfs/bb8a40b99a061c33a35f4e7275d1842a 
>> (msdosfs, local, noatime, noexec)
> 
> The labels obfuscate the device type for all mountpoints very well.

The ufs mounts are on an SATA drive. The msdosfs slice is the USB stick at 
/dev/da0. The nfs mount is from amd.