allow uncoordinated reads concurrent with writes of a mutable file or directory locally

[davidsarah]

In the fix to #265 in Tahoe v1.1, MutableFileNodes were made to serialize writes to a given mutable file or directory by a single gateway / storage client.

As mentioned in ticket:265#comment:4, this does not apply to concurrent reads and writes -- the read may fail rather than obtaining some snapshot of the file or directory.

Clients using filesystem-like interfaces such as SFTP or FUSE may not expect such failures. At the time of writing, the SFTP documentation at wiki:SftpFrontend incorrectly claims that readers will get a snapshot of the file. (For mutable files, this problem applies directly to the file; for immutable files it applies to the parent directory when that is mutable.)

[davidsarah]

Replying to davidsarah:

At the time of writing, the SFTP documentation at wiki:SftpFrontend incorrectly claims that readers will get a snapshot of the file. (For mutable files, this problem applies directly to the file; for immutable files it applies to the parent directory when that is mutable.)

This doc is fixed by wiki:SftpFrontend?action=diff&version=47&old_version=46 .

[zooko]

Is it clear to readers of wiki:SftpFrontend that "concurrent" accesses through a single gateway will get serialized? Should it be?

[davidsarah]

Replying to zooko:

Is it clear to readers of wiki:SftpFrontend that "concurrent" accesses through a single gateway will get serialized? Should it be?

When sshfs is used, there should be a single sshfs mount: wiki:SftpFrontend?action=diff&version=50&old_version=49

I don't want to make statements about serialization in the docs that are stronger than what is actually implemented. I think wiki:SftpFrontend is now accurate, even if it doesn't quite give the full story.

[davidsarah]

This improvement would be useful for the drop-upload feature, because you can't really avoid the possibility of concurrent reads and writes on the upload directory if you want to be able to read it while it is still active.

[daira]

Add magic-folder keyword to all drop-upload tickets.

[daira]

This does not affect the intended Magic Folder design, since a client should not read its own DMD concurrently with writing it. It reads its own DMD on start-up, and other clients' DMDs on each scan, but it should not write its own DMD until after the start-up scan.

However, I'm not sure that this is this is not currently implemented correctly. Filed #2553 to track it.