From 08ea3dc512be2e331aa486f818ba9d5f2fe2c4cb Mon Sep 17 00:00:00 2001 From: david-sarah <david-sarah@jacaranda.org> Date: Wed, 31 Aug 2011 16:21:48 -0700 Subject: [PATCH] docs/write_coordination.rst: fix formatting and add more specific warning about access via sshfs. --- docs/write_coordination.rst | 21 +++++++++++++-------- 1 file changed, 13 insertions(+), 8 deletions(-) diff --git a/docs/write_coordination.rst b/docs/write_coordination.rst index eebb0dd9..e855aec4 100644 --- a/docs/write_coordination.rst +++ b/docs/write_coordination.rst @@ -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. -- 2.45.2