[Bug 200513] [FUSEFS] Race at shutdown and corrupt fusefs systems

[bugzilla-noreply at freebsd.org]

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

--- Comment #8 from rkoberman at gmail.com ---
(In reply to Alan Somers from comment #7)
You may be right. I only saw the issue with ntfs-3g (sysutils/fusefs-ntfs). If
I shutdown my system with an NTFS volume mounted and after the file system had
been written to, I would see corruption. I would be unable to open many
directories and get lots of file system errors. Files would simply be gone.

I would boot up Windows 7 and run a file check which claimed the volume was OK
and asked whether I wanted to run the full check. The full check reported
errors and required a reboot to fix the problem. 

After the rebuild completed, the file system would mount and run fine on
FreeBSD. In a mail thread, someone, probably either Florian Smeets or Attilio
Rao, it was suggested that the fuse daemon was likely existing before the file
system was unmounted completely and that led me to write a simple rc.d script
to unmount all FUSE file systems (umount -Avt fusefs) during shutdown. Since
then, I have seen no corruption issues. (I have seen other issues, notably
confusion between mtime and ctime on files.

This all goes back to around 2012, so my memory is hazy.

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