Context Navigation

Changes between Version 49 and Version 50 of SftpFrontend

v49	v50
48	48	Tahoe's SFTP frontend includes several workarounds and extensions to make it function correctly with sshfs.
49	49
	50	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.
	51
50	52	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.
51	53