ExternalVendorCode/tahoe-lafs
1
0
Fork 0
mirror of https://github.com/tahoe-lafs/tahoe-lafs.git synced 2024-12-19 13:07:56 +00:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

docs/write_coordination.rst: fix formatting and add more specific warning about access via sshfs.

Browse Source
This commit is contained in:
david-sarah 2011-08-31 16:21:48 -07:00
parent 7191b0b32e
commit 08ea3dc512
1 changed files with 13 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
docs/write_coordination.rst
View File

@ -2,12 +2,17 @@
Avoiding Write Collisions in Tahoe
==================================
Tahoe does not provide locking of the mutable files and directories.
If there is more than one simultaneous attempt to change a mutable file
or directory, then an <cite>UncoordinatedWriteError</p> will result.
This might, in rare cases, cause the file or directory contents to be
accidentally deleted. The user is expected to ensure that there is at
most one outstanding write or update request for a given file or
directory at a time. One convenient way to accomplish this is to make
a different file or directory for each person or process which wants to
Tahoe does not provide locking of mutable files and directories.
If there is more than one simultaneous attempt to change a mutable file
or directory, then an ``UncoordinatedWriteError`` may result.
This might, in rare cases, cause the file or directory contents to be
accidentally deleted. The user is expected to ensure that there is at
most one outstanding write or update request for a given file or
directory at a time. One convenient way to accomplish this is to make
a different file or directory for each person or process that wants to
write.
If mutable parts of a filesystem are accessed via sshfs, only a single
sshfs mount should be used. There may be data loss if mutable files or
directories are accessed via two sshfs mounts, or written both via sshfs
and from other clients.