On Monday 25 May 2009 16:35:31 roucaries bastien wrote: > Does the host or client side kernel crash ? Or it is only a hang of > process using sshfs file ?
No. The kernels are not crashing. I explored more about it. * cat < /mount/point/kmsg * echo X > /mount/point/sysrq-trigger These are the 2 commands that need to be read and written. I can use the cat command on top of sshfs. With only cat executed, it looks like this: root 2246 0.0 0.1 3100 516 pts/1 S<+ 16:12 0:00 cat At this moment, I can go to the ssh host, and trigger the echo command there, and I will be able to see the cat read on the client. That way it works. But if I run the echo command on the client (using the sshfs interface): Do you have an idea what state the following process is in: ???? root 2283 0.0 0.3 4312 1708 pts/2 S<s+ 17:03 0:00 -bash I tried to run echo h > /mount/point/sysrq- and hit the tab button, and it hung. At this moment, this is what the sshfs, running in debug mode, says: unique: 8, opcode: GETATTR (3), nodeid: 1, insize: 56 Why would it fail to get the attributes for sysrq-trigger ? If I give the full path to echo (without the auto-completion of bash), it still hangs and sshfs spits this: unique: 10, opcode: LOOKUP (1), nodeid: 1, insize: 54 LOOKUP /sysrq-trigger Anything else you'd want me to try ? Ritesh -- Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com "Necessity is the mother of invention."
signature.asc
Description: This is a digitally signed message part.
