Date: Tue, 2 Jul 2013 15:07:39 -0700 From: Kevin Oberman <rkoberman@gmail.com> To: fs@freebsd.org Cc: Attilio Rao <asmrookie@gmail.com> Subject: New fusefs implementation not usable with multiple fusefs mounts Message-ID: <CAN6yY1sMxAwq1DR4RW-=d2JwHUsJPJuMj3R5CmTPb9Sogj6pPQ@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
I have been using the new fusefs for a while and have had to back it out and go back to the old kernel module. I keep getting corrupted file NTFS systems and I think I understand why, I mount two NTFS systems: /dev/fuse 184319948 110625056 73694892 60% /media/Media /dev/fuse 110636028 104943584 5692444 95% /media/Windows7_OS Note that both systems are mounted on /dev/fuse and I am assured that this is by design. Both work fine for reads and seem to work for writes. Then I unmount either of them. Both are unmounted, at least as far as the OS is concerned. There is no way to unmount one and leave the other mounted. It appears that any attempt to unmount either system does a proper unmount of /media/Media, but, while marking /media/Windows7_OS as unmounted, actually does not do so. The device ends up corrupt and the only way I have been able to clean it is to boot Windows and have a disk check run. Media never seems to get corrupted. Any further information I might gather before filing a PR? I am running on 9.1 stable, but havehad the problem since the patch set first became available on 9.0-stable. -- R. Kevin Oberman, Network Engineer E-mail: rkoberman@gmail.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN6yY1sMxAwq1DR4RW-=d2JwHUsJPJuMj3R5CmTPb9Sogj6pPQ>