[Bug 281524] msdosfs error over USB causes a kernel panic

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281524

Tomasz "CeDeROM" CEDRO <tomek@cedro.info> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tomek@cedro.info

--- Comment #1 from Tomasz "CeDeROM" CEDRO <tomek@cedro.info> ---
Does the problem occur when you use different mount_msdosfs (8) options for the
filesystem? For instance try -o longsnames/shortnames/nowin95 and/or -s / -9
flags.

These embedded FAT12/16 emulation implementations are usually limited and may
not support all calls (i.e. metadata access).

For instance some time ago I was playing with DAPLink FAT12 implementation.. it
only supported single sector due RAM limitations in MCU but was sufficient
store a firmware file.. and partition table was not compatible with some FAT
implementations (for instance Android always try fsck on disk attach and that
failed).. etc etc.

Are you sure nothing in the background (i.e. gvfs / file manager) tries to
access the drive, write anything on it (i.e. trashbin), check metadata? Can you
try using the disk with no Xorg WM in plain terminal, mount, read files, write
files, and see if that helps?


Maybe this macOS / msdosfs issue is somehow related?

https://github.com/adafruit/circuitpython/issues/8449

They had problems with slow writes and IO errors.. but the solution was not to
fix the CircuitPython (CP) FAT emulation implementation but the host side.
Looks like something similar happens here?

I am not sure but if FreeBSD msdosfs provided some sort of trace / debug it
could be possible to pinpoint the issue and fix the CP?

-- 
You are receiving this mail because:
You are the assignee for the bug.