SSHfs crashes when trying to write files

This forum is for Marvell Kirkwood devices such as the GoFlex Home/Net, PogoPlug v1/v2, SheevaPlug, and ZyXEL devices.

SSHfs crashes when trying to write files

Postby harrim4n » Wed Dec 26, 2012 2:56 pm

I recently decided to connect my dockstar (arch arm) to my pogoplug (also arch arm) via sshfs. Everything works fine, the mount works without any problems, but as when I try to write into the folder the sshfs crashes. For example I can do 10 ls in a row, but when I try a touch everything goes down the drain, but not always. Sometimes I can rm and touch 5 files or so, but eventually it crahes.Here is the output when I touched /media/Data/test and then rm it and then touched it again, after which it crashed with the return value 139.
$this->bbcode_second_pass_code('', '
[harrim4n@DockStar ~]$ sudo sshfs root@plug:/media/Data /media/Data/ -o allow_other -o sshfs_sync -d
[...]
LOOKUP /test
getattr /test
NODEID: 13
unique: 38, success, outsize: 144
unique: 39, opcode: OPEN (14), nodeid: 13, insize: 48, pid: 24065
open flags: 0x20801 /test
open[204824] flags: 0x20801 /test
unique: 39, success, outsize: 32
unique: 40, opcode: FLUSH (25), nodeid: 13, insize: 64, pid: 24065
flush[204824]
unique: 40, success, outsize: 16
unique: 41, opcode: SETATTR (4), nodeid: 13, insize: 128, pid: 24065
utime /test 1356350916 1356350916
getattr /test
unique: 41, success, outsize: 120
unique: 42, opcode: FLUSH (25), nodeid: 13, insize: 64, pid: 24065
flush[204824]
unique: 42, success, outsize: 16
unique: 43, opcode: RELEASE (18), nodeid: 13, insize: 64, pid: 0
release[204824] flags: 0x20801
unique: 43, success, outsize: 16
unique: 44, opcode: LOOKUP (1), nodeid: 1, insize: 45, pid: 24066
LOOKUP /test
getattr /test
NODEID: 13
unique: 44, success, outsize: 144
unique: 45, opcode: ACCESS (34), nodeid: 13, insize: 48, pid: 24066
unique: 45, error: -38 (Function not implemented), outsize: 16
unique: 46, opcode: UNLINK (10), nodeid: 1, insize: 45, pid: 24066
unlink /test
unique: 46, success, outsize: 16
unique: 47, opcode: FORGET (2), nodeid: 13, insize: 48, pid: 0
FORGET 13/3
DELETE: 13
unique: 48, opcode: LOOKUP (1), nodeid: 1, insize: 45, pid: 24067
LOOKUP /test
getattr /test
unique: 48, error: -2 (No such file or directory), outsize: 16
unique: 49, opcode: CREATE (35), nodeid: 1, insize: 61, pid: 24067
create flags: 0x20841 /test 0100644 umask=0022
create[204560] flags: 0x20841 /test
fgetattr[204560] /test
NODEID: 28
unique: 49, success, outsize: 160
unique: 50, opcode: FLUSH (25), nodeid: 28, insize: 64, pid: 24067
flush[0]
')
The output of the other shell in which I did the touch and rm is:
$this->bbcode_second_pass_code('', '
[harrim4n@DockStar ~]$ touch /media/Data/test
[harrim4n@DockStar ~]$ rm /media/Data/test
[harrim4n@DockStar ~]$ touch /media/Data/test
touch: closing ‘/media/Data/test’: Transport endpoint is not connected
')
Now, if I do an umount after the crash and execute the sshfs command again, everything's fine until the next crash.I really don't know what the problem is here and hope to get some help from any of you guys.

harrim4n
harrim4n
 
Posts: 3
Joined: Wed Dec 26, 2012 2:53 pm

Return to Marvell Kirkwood

Who is online

Users browsing this forum: No registered users and 7 guests