Changes between Version 2 and Version 3 of SftpFrontend

Timestamp:

2010-05-28T22:26:40Z (14 years ago)

Author:

davidsarah

Comment:

Link to sshfs patch

SftpFrontend

@@ -15 +15 @@
 Tahoe's SFTP frontend includes several workarounds and extensions to make it function correctly with sshfs.
 
-sshfs does not wait for 'close' requests to complete before reporting to the application that a file has been successfully closed. Therefore, you should not shut down your gateway node immediately after writing files via sshfs, otherwise those files may be lost. It is possible that an upload could fail (due to a network error, lack of storage space, etc.); such failures will not be reported to applications using sshfs. [TODO: include patch that makes sshfs wait for close requests to complete.]
+sshfs does not wait for 'close' requests to complete before reporting to the application that a file has been successfully closed. Therefore, you should not shut down your gateway node immediately after writing files via sshfs, otherwise those files may be lost. It is possible that an upload could fail (due to a network error, lack of storage space, etc.); such failures will not be reported to applications using sshfs. ([http://allmydata.org/trac/tahoe-lafs/raw-attachment/wiki/SftpFrontend/sshfs.c.patch This patch] makes sshfs wait for close requests to complete, but may cause its own compatibility problems; the patch is provided only for testing purposes.)
 
 Some applications may make assumptions that are incompatible with Tahoe. For example, 'flushing' a file does not guarantee that written data is reflected in the Tahoe filesystem, so opening the same file via another handle and attempting to read that data will not work.