On Tuesday 26 May 2009 18:27:44 roucaries bastien wrote: > proc file are not seekable. Try to open it with mcedit and it will > hang. Could you after the hang ls some other file on the sshfs system > or the whole mount point is hang ? > > If you could it is a feature, if you could not it is a bug.
Ah!!! They all went into 'D' State: 4928 pts/1 S< 0:00 cat 4931 ? S<s 0:00 sshd: r...@pts/2 4934 pts/2 S<s 0:00 -bash 4938 pts/2 D<+ 0:00 ls /var/tmp/foo/tmp 4940 ? S<s 0:00 sshd: r...@pts/3 4942 pts/3 S<s 0:00 -bash 4946 pts/3 D<+ 0:00 ls /var/tmp/foo/ 4948 ? S<s 0:00 sshd: r...@pts/4 Point to note here is that it happened after firing the 'cat' command, which is in 'S' state as shown above. Before executing the cat command (cat </var/tmp/foo/proc/kmsg), ls was working. Even an echo to /var/tmp/foo/proc/sysrq-trigger was working. But why is that? /proc/kmsg is listed as a regular (0 byte) file. -r-------- 1 root root 0 2009-05-26 06:25 /proc/kmsg 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.
