kenny i also have the exact same issue on 64bit with 2.1.9 ..
but it effects my shutdown and i watch it in verbose mode and it seems its a recursive loop preventing the machine from full shut down... it was working fine the past few months so im not sure if it was an apple update that caused this or 3rd party software i did just install VMware so that might be a cause as well... On Fri, Jun 24, 2011 at 1:38 AM, Kenny <[email protected]> wrote: > Hello, thanks for the quick response. > > The Preference pane tells me that the version installed in 2.1.9 () > To my knowledge this is still the latest (semi-stable) version that > supports 64-bit? > Is there another version I should try out? > > When MacFuse is unmounted (crashed), the encfs process is gone too. > > In case it helps, this is the output from dmesg: > > ffff8014974120... > fuse_biglock_vnop_reclaim: biglock 0xffffff8014974120 released! > fuse_biglock_vnop_fsync: Locking node 0xffffff801acc7450... > fuse_biglock_vnop_fsync: node 0xffffff801acc7450 locked! > fuse_biglock_vnop_fsync: Aquiring biglock 0xffffff8014974120... > fuse_biglock_vnop_fsync: biglock 0xffffff8014974120 aquired! > fuse_biglock_vnop_fsync: Releasing biglock 0xffffff8014974120... > fuse_biglock_vnop_fsync: biglock 0xffffff8014974120 released! > fuse_biglock_vnop_fsync: Unlocking node 0xffffff801acc7450... > fuse_biglock_vnop_fsync: node 0xffffff801acc7450 unlocked! > fuse_biglock_vnop_reclaim: Aquiring biglock 0xffffff8014974120... > fuse_biglock_vnop_reclaim: biglock 0xffffff8014974120 aquired! > fuse_biglock_vnop_reclaim: Releasing biglock 0xffffff8014974120... > fuse_biglock_vnop_reclaim: biglock 0xffffff8014974120 released! > fuse_biglock_vnop_fsync: Locking node 0xffffff8018fc4c50... > fuse_biglock_vnop_fsync: node 0xffffff8018fc4c50 locked! > fuse_biglock_vnop_fsync: Aquiring biglock 0xffffff8014974120... > fuse_biglock_vnop_fsync: biglock 0xffffff8014974120 aquired! > fuse_biglock_vnop_fsync: Releasing biglock 0xffffff8014974120... > fuse_biglock_vnop_fsync: biglock 0xffffff8014974120 released! > fuse_biglock_vnop_fsync: Unlocking node 0xffffff8018fc4c50... > fuse_biglock_vnop_fsync: node 0xffffff8018fc4c50 unlocked! > fuse_biglock_vnop_reclaim: Aquiring biglock 0xffffff8014974120... > fuse_biglock_vnop_reclaim: biglock 0xffffff8014974120 aquired! > fuse_biglock_vnop_reclaim: Releasing biglock 0xffffff8014974120... > fuse_biglock_vnop_reclaim: biglock 0xffffff8014974120 released! > fuse_vfsop_unmount: Aquiring biglock 0xffffff8014974120... > fuse_vfsop_unmount: biglock 0xffffff8014974120 aquired! > fuse_vfsop_unmount: Calling vflush(mp, fuse_rootvp, flags=0x0); > fuse_vfsop_unmount: Releasing biglock 0xffffff8014974120... > fuse_vfsop_unmount: biglock 0xffffff8014974120 released! > fuse_vfsop_unmount: Aquiring biglock 0xffffff8014974120... > fuse_vfsop_unmount: biglock 0xffffff8014974120 aquired! > fuse_vfsop_unmount: Done. > fuse_vfsop_unmount: Calling vnode_rele(fuse_rootp); > fuse_vfsop_unmount: Releasing biglock 0xffffff8014974120... > fuse_vfsop_unmount: biglock 0xffffff8014974120 released! > fuse_biglock_vnop_inactive: Locking node 0xffffff801acc3850... > fuse_biglock_vnop_inactive: node 0xffffff801acc3850 locked! > fuse_biglock_vnop_inactive: Aquiring biglock 0xffffff8014974120... > fuse_biglock_vnop_inactive: biglock 0xffffff8014974120 aquired! > fuse_biglock_vnop_inactive: Releasing biglock 0xffffff8014974120... > fuse_biglock_vnop_inactive: biglock 0xffffff8014974120 released! > fuse_biglock_vnop_inactive: Unlocking node 0xffffff801acc3850... > fuse_biglock_vnop_inactive: node 0xffffff801acc3850 unlocked! > fuse_vfsop_unmount: Aquiring biglock 0xffffff8014974120... > fuse_vfsop_unmount: biglock 0xffffff8014974120 aquired! > fuse_vfsop_unmount: Done. > fuse_vfsop_unmount: Calling vflush(mp, NULLVP, FORCECLOSE); > fuse_vfsop_unmount: Releasing biglock 0xffffff8014974120... > fuse_vfsop_unmount: biglock 0xffffff8014974120 released! > fuse_biglock_vnop_fsync: Locking node 0xffffff801acc3850... > fuse_biglock_vnop_fsync: node 0xffffff801acc3850 locked! > fuse_biglock_vnop_fsync: Aquiring biglock 0xffffff8014974120... > fuse_biglock_vnop_fsync: biglock 0xffffff8014974120 aquired! > fuse_biglock_vnop_fsync: Releasing biglock 0xffffff8014974120... > fuse_biglock_vnop_fsync: biglock 0xffffff8014974120 released! > fuse_biglock_vnop_fsync: Unlocking node 0xffffff801acc3850... > fuse_biglock_vnop_fsync: node 0xffffff801acc3850 unlocked! > fuse_biglock_vnop_reclaim: Aquiring biglock 0xffffff8014974120... > fuse_biglock_vnop_reclaim: biglock 0xffffff8014974120 aquired! > fuse_biglock_vnop_reclaim: Releasing biglock 0xffffff8014974120... > fuse_biglock_vnop_reclaim: biglock 0xffffff8014974120 released! > fuse_vfsop_unmount: Aquiring biglock 0xffffff8014974120... > fuse_vfsop_unmount: biglock 0xffffff8014974120 aquired! > fuse_vfsop_unmount: Done. > fuse_vfsop_unmount: Releasing biglock 0xffffff8014974120... > fuse_vfsop_unmount: biglock 0xffffff8014974120 released! > > > > On Jun 23, 5:13 pm, Sam Moffatt <[email protected]> wrote: > > If you're using one of the early 64-bit builds that didn't have some > > of the checks in place then it is entirely possible there is an access > > issue that is happening behind the scenes with the requests that is > > resulting in something getting terminated. What version of 64-bit > > compatible MacFUSE are you using? > > > > When you get the socket not connected, does the encfs process still > > live on? Have you looked for any crash reporter files? It could be a > > bug in encfs as well, I've had incorrectly built semaphore code > > (*cough* e.g. my own) result in a state where the process gets > > terminated because the number of requests hitting it simultaneously > > overloaded the implementation and resulted in a failure. > > > > Cheers, > > > > Sam Moffatthttp://pasamio.id.au > > > > > > > > > > > > > > > > On Thu, Jun 23, 2011 at 11:32 PM, Kenny <[email protected]> wrote: > > > Hi, > > > > > We've been using MacFuse for a long time with EncFS, on multiple > > > machines. > > > It's never given me any problems. (on 32 bit machines with both > > > Leopard and Snow Leopard). > > > However, we've recently added a few new machines. They come standard > > > with Snow Leopard and 64 bit enabled now. > > > > > On the 64bit machines, it seems the images are regularly unmounted > > > without notice. > > > I wrote a small script that can reproduce quite fast. > > > It doesn't do much, it just continuously creates new directories and > > > touches (creates) files in them. > > > This works fine for a long time, but after a while, the 'touch' seems > > > to take very long, and eventually 'times out' with the error: > > > > > Socket is not connected. > > > > > At this point, the drive is no longer mounted. > > > (mount doesn't display it anymore, mountpoint directory inode is no > > > longer the same as the data directory inode) > > > > > It just disappeared.... > > > I looked at the logs in Console.app, and in /var/log/syslog, but > > > nothing is added in there. > > > In dmesg, I do see fuse references, but nothing that points to a bug/ > > > crash. > > > > > Is this a known problem? Is there a fix/workaround? > > > Where should I look for more logging? > > > Is this a MacFuse error, or is this specific to EncFS and should I > > > report a bug there? > > > > > Do you guys use 64bit macs? Have you encountered the same problems? > > > > > -- > > > 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 athttp:// > groups.google.com/group/macfuse?hl=en. > > -- > 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. > > -- 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.
