Last change
on this file was
4723af6,
checked in by Brian Warner <warner@…>, at 2017-06-06T10:20:49Z
|
LAFS now stands for "Least-Authority File Store" rather than "Least-Authority File System". refs #2345
Signed-off-by: Daira Hopwood <daira@…>
|
-
Property mode set to
100644
|
File size:
944 bytes
|
Line | |
---|
1 | .. -*- coding: utf-8-with-signature -*- |
---|
2 | |
---|
3 | ================================== |
---|
4 | Avoiding Write Collisions in Tahoe |
---|
5 | ================================== |
---|
6 | |
---|
7 | Tahoe does not provide locking of mutable files and directories. |
---|
8 | If there is more than one simultaneous attempt to change a mutable file |
---|
9 | or directory, then an ``UncoordinatedWriteError`` may result. |
---|
10 | This might, in rare cases, cause the file or directory contents to be |
---|
11 | accidentally deleted. The user is expected to ensure that there is at |
---|
12 | most one outstanding write or update request for a given file or |
---|
13 | directory at a time. One convenient way to accomplish this is to make |
---|
14 | a different file or directory for each person or process that wants to |
---|
15 | write. |
---|
16 | |
---|
17 | If mutable parts of a file store are accessed via sshfs, only a single |
---|
18 | sshfs mount should be used. There may be data loss if mutable files or |
---|
19 | directories are accessed via two sshfs mounts, or written both via sshfs |
---|
20 | and from other clients. |
---|
Note: See
TracBrowser
for help on using the repository browser.