On Tue, May 26, 2009 at 2:44 PM, Ritesh Raj Sarraf <[email protected]> wrote: > Any ideas!! > I am wondering if such usage is even expected of sshfs/fuse ? > > Ritesh > > On Monday 25 May 2009 17:19:47 Ritesh Raj Sarraf wrote: >> On Monday 25 May 2009 17:12:26 Ritesh Raj Sarraf wrote: >> > Anything else you'd want me to try ? >> >> Actually, just doing a: >> ls /mount/point/sshfs is resulting in a hang and the sshfs process gives >> this: >> >> unique: 11, opcode: GETATTR (3), nodeid: 1, insize: 56 >> >> And the ls process also gets the same process status: >> root 2309 0.0 0.1 3464 800 pts/4 S<+ 17:11 0:00 ls >> /var/tmp/foo/ >>
> What's interesting is that the cat command is not affected with it even >> though it is reading a file from the same mount path. >> root 2246 0.0 0.1 3100 516 pts/1 S<+ 16:12 0:00 cat >> >> >> The file permissions as exported by sshfs are as follows: >> --w------- 1 root root 0 2009-05-25 17:15 sysrq-trigger >> -r-------- 1 root root 0 2009-05-22 18:37 kmsg >> >> which is identical to the permission as on the host machine. >> >> >> Ritesh 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. Bastien -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
