Changes between Version 71 and Version 72 of SftpFrontend

Timestamp:

2011-08-31T23:09:15Z (13 years ago)

Author:

davidsarah

Comment:

fix write coordination link

SftpFrontend

@@ -55 +55 @@
 Tahoe's SFTP frontend includes several workarounds and extensions to make it function correctly with sshfs.
 
-Mutable parts of a filesystem should only be accessed via a single sshfs mount (this is a stronger restriction than the [http://tahoe-lafs.org/source/tahoe-lafs/trunk/docs/write_coordination.html write coordination directive] against writing mutable parts of a filesystem via more than one gateway). Data loss may result for concurrently accessed files if this restriction is not followed.
+Mutable parts of a filesystem should only be accessed via a single sshfs mount (this is a stronger restriction than the [http://tahoe-lafs.org/trac/tahoe-lafs/browser/trunk/docs/write_coordination.rst write coordination directive] against writing mutable parts of a filesystem via more than one gateway). Data loss may result for concurrently accessed files if this restriction is not followed.
 
 When writing a file to the Tahoe filesystem, sshfs does not wait for the 'close' request to complete before reporting to the application that the file has been successfully closed (#1059). 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. This also implies that during the upload, a file could be visible via SFTP but not via the Tahoe WUI, CLI, or FTP frontends.