[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Fixing the FSFS corruption bug

From: Philip Martin <philip_at_codematters.co.uk>
Date: 2006-09-11 22:06:13 CEST

Malcolm Rowe <malcolm-svn-dev@farside.org.uk> writes:

> On Tue, Sep 05, 2006 at 09:29:27PM +0100, Malcolm Rowe wrote:
>> + err = svn_io_file_open(file, path_txn_proto_rev_lock(fs, txn_id, pool),
>> + pool);
> So I've just noticed that this method of creating a lockfile (using
> O_CREATE|O_EXCL) appears to be broken on NFSv3 mounts on Linux pre-2.6.5
> (including all 2.4 kernels), as described in [1], and as far as I can
> tell, isn't supported on NFSv2 at all ([2] backs this up, to some extent).

I suppose you might be able to use some sort of rename system instead
of using a separate lock file: rename the file before writing it and
then rename it back when the write is complete. An incomplete write
would leave the renamed file which a subsequent write would need to

Philip Martin
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Sep 11 22:13:29 2006

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.