From: Miklos S. <mi...@sz...> - 2008-08-21 18:07:18
|
On Thu, 07 Aug 2008, Jelle de Jong wrote: > I got two other reports of sshfs freezes, I encrypted them for your gpg > key. I have the feeling that the client locks up when the server does > not respond directly. I need to restart the client to get my sshfs up > again. Simply restarting or killing and restarting sshfs does not work > to get it kicking again. > > http://www.powercraft.nl/temp/sshfs-debug-v4.txt.tar.gz.gpg > http://www.powercraft.nl/temp/sshfs-debug-v5.txt.tar.gz.gpg > > # decrypt commands for recipient > wget http://www.powercraft.nl/temp/sshfs-debug-v4.txt.tar.gz.gpg > gpg --decrypt --output sshfs-debug-v4.txt.tar.gz > sshfs-debug-v4.txt.tar.gz.gpg > tar xvzf sshfs-debug-v4.txt.tar.gz > less sshfs-debug-v4.tx Thanks for the traces, and sorry for the long delay (I was on vacation). What I can see from all four logs is that a READ request is sent to the sftp-server, yet no answer is received. The problem could be in quite a few places: - sshfs - ssh client - ssh server - sftp-server Can you check the version of SSH on the client and server? The next step in identifying the problem would be to make system call traces (with "strace") of each of the above components. You could start with the sftp-server, because that is the easiest to trace, and possibly the likeliest to be the cause. The way to do it is to first mount the filesystem, then on the server start tracing the sftp-server process with the following command: strace -p `pidof sftp-server` -o /tmp/strace then proceed with the testing. Thanks, Miklos |