From: <bz...@ao...> - 2014-10-22 08:24:23
|
On Tue, 21 Oct 2014 11:44:44 +0200 bz...@ao... wrote: > since two days, I have been experiencing a very strange bug with sshfs. > ... > I can spawn no shells anymore after that, running processes continue to run but new processes (presumably accessing $HOME) won't start. > > To recover, I can run fusermount -u -z /home/bzk/data/media/music/sks as root. > > I checked the filesystem with fsck -f (since it was reportedly clean) but that did not change anything. The error occurs on Arch as well as Gentoo. I tested with openssh 6.5, 6.6, 6.7, fuse-sshfs 2.4, 2.5 and openssl 1.0.1i, 1.0.1j, the error persists. > > I can by no means make sense of that behavior and hope one of you can. Hi again, just to give you an update on this. Today I experience the same behavior, but on a different directory. It is the 'server' directory on which it worked the last time, and where sshfs was presumably mounted when I last shut down my machine. Also interesting: the sks mount point which failed yesterday works again. It seems like somehow the mount point is left in an unclean state if the machine goes down and that it persists a reboot and re-creation of the mount point with rm and mkdir. If you need any further information or debugging from my side please tell me. Best regards, -- Patric Schmitz <bz...@ao...> |