Yes, as stated in the original ticket, I could easily reproduce this by touching a lot of files. The bash script I use for this can be found here: http://pastebin.com/4vq7eetU
Mount an encfs drive on /tmp/mount and run the script. After a few minutes, you'll notice that the drive is no longer mounted. The encfs process is gone at this point. This only happens on 64bit macs (including Snow Leopard and Lion). I cannot reproduce on 32bit Leopard or 32bit Snow Leopard machines regards, - Kenny On Aug 4, 7:42 am, Bryan Pham <[email protected]> wrote: > Hey Erik, > > A large data-set copy 10k files seems to reproduce this very often. > > 8/3/11 10:29:01.000 PM kernel: fuse_vfsop_unmount: Calling vflush(mp, > fuse_rootvp, flags=0x0); > 8/3/11 10:29:01.000 PM kernel: fuse_vfsop_unmount: Done. > 8/3/11 10:29:01.000 PM kernel: fuse_vfsop_unmount: Waiting for reply from > FUSE_DESTROY. > 8/3/11 10:29:01.000 PM kernel: fuse_vfsop_unmount: Reply received. > 8/3/11 10:29:01.000 PM kernel: fuse_vfsop_unmount: Calling > vnode_rele(fuse_rootp); > 8/3/11 10:29:01.000 PM kernel: fuse_vfsop_unmount: Done. > 8/3/11 10:29:01.000 PM kernel: fuse_vfsop_unmount: Calling vflush(mp, > NULLVP, FORCECLOSE); > 8/3/11 10:29:01.000 PM kernel: fuse_vfsop_unmount: Done. > 8/3/11 10:39:33.000 PM kernel: MacFUSE: force ejecting (no response from > user space 5) > 8/3/11 10:39:33.000 PM kernel: fuse_vfsop_unmount: Calling vflush(mp, > fuse_rootvp, flags=0x0); > 8/3/11 10:39:33.000 PM kernel: fuse_vfsop_unmount: Done. > 8/3/11 10:39:33.000 PM kernel: fuse_vfsop_unmount: Calling > vnode_rele(fuse_rootp); > 8/3/11 10:39:33.000 PM kernel: fuse_vfsop_unmount: Done. > 8/3/11 10:39:33.000 PM kernel: fuse_vfsop_unmount: Calling vflush(mp, > NULLVP, FORCECLOSE); > 8/3/11 10:39:33.000 PM kernel: fuse_vfsop_unmount: Done. > > > > > > > > > > On Wed, Aug 3, 2011 at 11:04 AM, Erik Larsson <[email protected]> wrote: > > ** > > [email protected] wrote 2011-08-03 18.47: > > > > 03/08/2011 16:30:53.000 kernel: MacFUSE: force ejecting (no response > > from user space 5) > > The message is a little bit cryptic but most likely it means that fuse > > daemon died. To make sure that it is true run encfs (or other filesystem > > that crashed) with "-d -f" flags and show us a few latest messages from > > encfs. Also make sure that after this message the encfs process is still > > alive "ps ax | grep encfs". > > > And a reproduce test case will be *very* helpful. > > > I would also be very interested in a reproducible test case. > > The first thing to investigate in this case is obviously the encfs binary, > > as the kernel module indicates that it doesn't get any response through the > > fuse device, and thus force ejects the file system. > > > Regards, > > > - Erik > > > -- > > You received this message because you are subscribed to the Google Groups > > "MacFUSE" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]. > > For more options, visit this group at > >http://groups.google.com/group/macfuse?hl=en. > > -- > Best Regards, > > http://www.linkedin.com/in/bryantripham > Bryan Tri Pham -- You received this message because you are subscribed to the Google Groups "MacFUSE" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/macfuse?hl=en.
