------- Comment From [email protected] 2016-03-21 09:22 EDT------- (In reply to comment #24) > The race can also be triggered w/o ssh, by using "setsid -c", and I can also > reproduce it w/o cmsfs-fuse but with sshfs: > > root@s3545003:~# setsid -c sshfs geraldsc@tuxmaker: sshfs/ > root@s3545003:~# ls sshfs > ls: cannot access 'sshfs': Transport endpoint is not connected
I verified that Hendriks suggested fix (using a pipe for synchronization) does fix the problem for cmsfs-fuse. For sshfs though, there seem to be more problems, probably inside sshfs itself, instead of generic fuse code. The "Transport endpoint" issue is also fixed for sshfs, but now there is nothing mounted. Since sshfs does some forks on its own, there probably is some issue left within sshfs, but that would be a different story. So, for the issue reported here, with cmsfs-fuse, the pipe synchronization fix would help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1558967 Title: libfuse2: race in fuse_daemonize() causes ' Transport endpoint is not connected' (found with cmsfs-fuse) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fuse/+bug/1558967/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
