Re: Lock non-existent to allow reserving a path

On 2/24/14, 11:10 AM, Philip Martin wrote:
> It's hard to fix. Commit and unlock are separate filesystem operations
> and the server can always die, or fail the unlock, after the commit. I
> suppose a new filesystem might have a commit-and-unlock operation but
> how could FSFS solve it? We might be able to make FSFS ignore the lock
> if the file has been deleted, but that just postpones the problem until
> another commit recreates the file.

So remove the locks as part of creating a new file. Even if the commit fails
for whatever reason and you remove locks that's not a problem. You were
ignoring those locks anyway.
Received on 2014-02-24 20:48:50 CET