[sshfs] freezing sshfs system

[Jelle de J. <jel...@po...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello everybody,

My name is Jelle, and I am new to this list, so let me say thanks to
everybody doing so much hard work on the sshfs tool.

I am a heavy user of sshfs, and would like to include it as a service to
our thick clients as remote storage/sharing option. I have been testing
its stability for the last year intensive and I got some major problems
like, lost connections, freezing sshfs mounts, requiring to killall ssh
and sshfs or complete reboots of the clients.

Sometimes the client with a frozen sshfs can drag down our complete ssh
servers, they then seems to behaving as some major firewall block,
because something the clients sshfs mount is doing. Sometimes the server
recover automatically in a few minutes but sometimes they because
unresponsive to anything, even manual local logins will not work and a
hard reset is required causing all kinds of problems like corrupted sql
tables.

These problems mostly accure when using sshfs heavy with multimedia
programs -> playing dvd, ogg files, writing data to the remote share.

I know this description probably does not point directly to the problem,
so i contacted the fuse-devel mailinglist and ask them how I could help
to create some usefull bug reports, they told me to do some backtrace
with gdb: (the archive does not seem to be working on this moment)
Message-ID: <487...@po...>
https://lists.sourceforge.net/lists/listinfo/fuse-devel

I use debian sid and there were no sshfs-dbg packages, so I created a
bug-report and attached my debdiff and new deb packages for debugging:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=491210

I also contacted the gdb mailing list to figure out how to do a
backtrace of a frozen running process:
Message-ID: <488...@po...>
http://sourceware.org/ml/gdb/2008-07/msg00222.html

I the last few days I managed to create three backtraces reports after
my sshfs mount froze. I hope this provide the sshfs developers with
enough information to pin-point the problem. If not please tell me what
to provide more useful information.

I attached the backtrace reports and some used command info as attachments.

I hope this helps everybody.

Thanks in advance,

Jelle
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iJwEAQECAAYFAkiDexEACgkQ1WclBW9j5HnVtgP/Qs8+Rcnss8zepjqAIm2zE3uG
LUieu8teRzMz3qM2SH2wUY53vQQt1Tai/psZXeXV0TaPiRg24fCf34ulUlwf4tRY
mDtF1FD3geBY9/dHkgO4izmzTtR7gGjhfiHZ8M6jnXV+xMSgtdvoQoIwnwXz69xa
+37iq2gdL1ZfyllqYeM=
=B/dx
-----END PGP SIGNATURE-----