FS#14753 - [curlftpfs] 0.9.2 unusable due to remote file creation/update bug
Attached to Project:
Community Packages
Opened by Olivier (litemotiv) - Monday, 18 May 2009, 16:34 GMT
Last edited by Chris Brannon (cmb) - Wednesday, 01 July 2009, 16:46 GMT
Opened by Olivier (litemotiv) - Monday, 18 May 2009, 16:34 GMT
Last edited by Chris Brannon (cmb) - Wednesday, 01 July 2009, 16:46 GMT
|
Details
[Description:]
There is a serious problem with remote file creation/update in curlftpfs 0.9.2, as reported here: http://sourceforge.net/tracker/?func=detail&aid=2652901&group_id=160565&atid=816357 https://bugs.launchpad.net/ubuntu/+source/curlftpfs/+bug/120018 Supposedly this problem is not present in 0.9.1, perhaps we can consider a downgrade of the package until this is fixed? There seems to be little activity from the original developer, so it might take a while until a fixed version is available. [Steps to reproduce:] - Mount remote FTP server with curlftpfs, go to directory, create or edit random file with nano or vim. This results in either an "input/output error" with nano, or a "E667: Fsync failed" with vim. Sometimes the file in question *is* created or edited, but most of the time it fails. In some strange cases vim's swap files do get created but the actual save fails. - Remote file write or copy with pcmanfm-fuse (which relies on curlftpfs) is very unrealiable, most of the time it fails with a "File or directory not found" error. |
This task depends upon
Closed by Chris Brannon (cmb)
Wednesday, 01 July 2009, 16:46 GMT
Reason for closing: Deferred
Additional comments about closing: I'm marking this task as deferred, for now. We can reopen it at some point.
Wednesday, 01 July 2009, 16:46 GMT
Reason for closing: Deferred
Additional comments about closing: I'm marking this task as deferred, for now. We can reopen it at some point.
conclusions.
1. This bug does not appear on all FTP servers. I tried two servers yesterday.
Writes to files on the first server were successful, while writes to files
on the second server were unsuccessful.
2. I don't think that downgrading to curlftpfs 0.9.1 will fix the problem.
At least, it won't do so for all servers.
I'm going to keep experimenting.
using commands like echo. I think I have a good understanding of it. See
http://members.cox.net/cmbrannon/curlftpfs-bug.txt
for a fuller description.
The other issue is the inability to save files in vim.
I can't reproduce this one on any of my servers.
that doesn't work for me, it just keeps creating new 0-byte ~xyz files.
I could downgrade to curlftpfs 0.9.1, but I think it has other problems.
When I tried it on one of my test FTP servers, version 0.9.1 would
occasionally fail to report errors when writing files. The data didn't
show up on the remote server, but the writing process never failed with
an indication of error.
I really don't think that downgrading to 0.9.1 is the best approach, even
though 0.9.2 fails for some servers.
More suggestions would be appreciated.