[Bug 345226] Re: after resume, sshfs mounted dir can't be remounted immediately
We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again! ** Changed in: sshfs-fuse (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/345226 Title: after resume, sshfs mounted dir can't be remounted immediately -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 345226] Re: after resume, sshfs mounted dir can't be remounted immediately
Any further results on the test? I don't really want these bugs to expire, we get some good workaround information from them even if I can't seem to get them fixed yet. -- after resume, sshfs mounted dir can't be remounted immediately https://bugs.launchpad.net/bugs/345226 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 345226] Re: after resume, sshfs mounted dir can't be remounted immediately
This time I had no problems after resume. Either the time was too short for the network to timeout, or the extra options for debugging resolved the issue. I'll try leaving the machine in suspend for a longer period this time. ** Attachment added: "Full log after suspend and resume." https://bugs.launchpad.net/ubuntu/+source/sshfs-fuse/+bug/345226/+attachment/1590696/+files/sshfs.log -- after resume, sshfs mounted dir can't be remounted immediately https://bugs.launchpad.net/bugs/345226 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 345226] Re: after resume, sshfs mounted dir can't be remounted immediately
** Attachment added: "Here is the debugging output from sshfs, before putting machine into suspend." https://bugs.launchpad.net/ubuntu/+source/sshfs-fuse/+bug/345226/+attachment/1590645/+files/sshfs.log -- after resume, sshfs mounted dir can't be remounted immediately https://bugs.launchpad.net/bugs/345226 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 345226] Re: after resume, sshfs mounted dir can't be remounted immediately
I confirm this issue. Will try the debugging steps above and post results. -- after resume, sshfs mounted dir can't be remounted immediately https://bugs.launchpad.net/bugs/345226 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 345226] Re: after resume, sshfs mounted dir can't be remounted immediately
Please try running sshfs with the following options: sshfs -odebug,sshfs_debug,loglevel=debug ... this should produce a log that can be used to resolve this issue. -- after resume, sshfs mounted dir can't be remounted immediately https://bugs.launchpad.net/bugs/345226 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 345226] Re: after resume, sshfs mounted dir can't be remounted immediately
Thanks for the confirmation in Lucid. Logs with debugging output can be useful for diagnosing the problem. Try running sshfs with the following options: sshfs -odebug,sshfs_debug,loglevel=debug ... this should produce a log that can be used to resolve this issue. -- after resume, sshfs mounted dir can't be remounted immediately https://bugs.launchpad.net/bugs/345226 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 345226] Re: after resume, sshfs mounted dir can't be remounted immediately
I am now at 10.04 and the problem persists. swm...@swm-laptop:~$ apport-collect 345226 The authorization page: (https://edge.launchpad.net/+authorize-token?oauth_token=7279kJBV8SnpTzLLrL0w&allow_permission=WRITE_PRIVATE) should be opening in your browser. After you have authorized this program to access Launchpad on your behalf you should come back here and press to finish the authentication process. Package sshfs-fuse not installed and no hook available, ignoring swm...@swm-laptop:~$ sudo dpkg --list | grep sshfs [sudo] password for swmike: ii sshfs 2.2-1build1 filesystem client based on SSH File Transfer But basically what's happening is that the tcp session sshfs is running over has stalled after resuming suspend. I believe just as an IPv4 address is flushed after suspend, all active TCP sessions depending on that tcp session needs to be flushed as well. I am sshfs:ing from a 10.04 server as well, and the weird thing is that I can't find any TCP/22 corresponding to sshfs on either server or client, the only thing I can find is a unix socket: swm...@swm-laptop:~$ netstat -anp | grep sshfs unix 2 [ ] STREAM CONNECTED 889086 2201/sshfs swm...@swm-laptop:~$ ps auxw | grep sshfs swmike2201 0.0 0.0 44916 1240 ?Ssl May13 0:00 sshfs ub6: ub I'm doing this over IPv6 btw. After killing sshfs and re-establishing the sshfs session I now see a TCP/22 session belonging to ssh process, so I guess sshfs talks to ssh via a stream socket. -- after resume, sshfs mounted dir can't be remounted immediately https://bugs.launchpad.net/bugs/345226 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 345226] Re: after resume, sshfs mounted dir can't be remounted immediately
We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks! -- after resume, sshfs mounted dir can't be remounted immediately https://bugs.launchpad.net/bugs/345226 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 345226] Re: after resume, sshfs mounted dir can't be remounted immediately
** Changed in: sshfs-fuse (Ubuntu) Status: New => Incomplete -- after resume, sshfs mounted dir can't be remounted immediately https://bugs.launchpad.net/bugs/345226 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 345226] Re: after resume, sshfs mounted dir can't be remounted immediately
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. If you could test the current Ubuntu development version, this would help us a lot. If you can test it, and it is still an issue, we would appreciate if you could upload updated logs by running apport-collect 345226. -- after resume, sshfs mounted dir can't be remounted immediately https://bugs.launchpad.net/bugs/345226 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
