FS#42380 - [curlftpfs] Input/output error

Attached to Project: Community Packages
Opened by Jonathan Steel (jsteel) - Tuesday, 14 October 2014, 19:31 GMT
Last edited by Ivy Foster (escondida) - Friday, 11 October 2019, 19:46 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Felix Yan (felixonmars)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Input/output error after mounting ftp location. Tried as root.

Steps to reproduce:

(login info in ~/.netrc)
% curlftpfs ftp.my_ftp_site ./ftp
% ls ./ftp/
ls: reading directory ./ftp/: Input/output error

Debug log (when performing an "ls"):

unique: 6, opcode: GETATTR (3), nodeid: 1, insize: 56, pid: 23808
getattr /
unique: 6, success, outsize: 120
unique: 7, opcode: OPENDIR (27), nodeid: 1, insize: 48, pid: 23808
unique: 7, success, outsize: 32
unique: 8, opcode: READDIR (28), nodeid: 1, insize: 80, pid: 23808
getdir[0]
unique: 8, error: -5 (Input/output error), outsize: 16
unique: 9, opcode: RELEASEDIR (29), nodeid: 1, insize: 64, pid: 0
unique: 9, success, outsize: 16
This task depends upon

Closed by  Ivy Foster (escondida)
Friday, 11 October 2019, 19:46 GMT
Reason for closing:  Works for me
Additional comments about closing:  Even back when it was reported it was inconsistent to reproduce, OP can no longer confirm issue.
Comment by Jonathan Steel (jsteel) - Tuesday, 14 October 2014, 19:41 GMT
I guess this is more of an upstream issue, but it looks like they haven't fixed a bug in 7 years. Does this work for anyone though?
Comment by Christian (mantiz) - Thursday, 05 February 2015, 23:32 GMT
I found this bug report after facing the same or similar issue (successful connect but input/output error on listing).
I cannot provide a fix but I found using a subdirectory on the ftp side worked for me.

So, if that's an option for you, using

% curlftpfs ftp.example.com/sub_directory ./ftp

may work.
Comment by Jonathan Steel (jsteel) - Friday, 06 February 2015, 20:17 GMT
Thanks for the suggestion but I get the same error even when specifying a directory.
Comment by Ivy Foster (escondida) - Thursday, 10 October 2019, 03:16 GMT
Tested with "curlftpfs ftp.gnu.org foo/" and it worked fine. Though there seems to have been no new upstream release, can anybody still reproduce this bug?
Comment by Jonathan Steel (jsteel) - Friday, 11 October 2019, 19:06 GMT
I don't have access to the site I had an issue with now but I can confirm it works with ftp.gnu.org so maybe it depends on the FTP server being used. One user needed to specify a sub directory, for me it didn't work at all. I don't mind if this is closed now (as the original reporter, gosh has it been 5 years?!).
Comment by Ivy Foster (escondida) - Friday, 11 October 2019, 19:45 GMT
Fair enough! Thanks for the input, jsteel.

Loading...