Date: Tue, 11 Nov 2003 16:05:47 +0100
From: Andrea Arcangeli <andrea@suse.de>
To: Andrew Walrond <andrew@walrond.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel.bkbits.net off the air
Message-ID: <20031111150547.GG1649@x30.random>
References: <fa.eto0cvm.1v20528@ifi.uio.no> <fa.onl48uv.1tmeb21@ifi.uio.no> <3FB0EEB5.5010804@myrealbox.com> <200311111438.47868.andrew@walrond.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200311111438.47868.andrew@walrond.org>
User-Agent: Mutt/1.4i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 819
Lines: 24

On Tue, Nov 11, 2003 at 02:38:47PM +0000, Andrew Walrond wrote:
> So you check the lock, do rsync, and check the lock again. But the lock could 
> have flipped several times during the rsync and you wouldn't know about it.
> 
> My preferred solution is a single sequence file as described by Adreas:
> 
> Assuming sequence starts at 0,
> 
> To modify the repository, +1 to sequence file contents, modify repo, +1 to 
> sequence
> 
> To get a coherent copy,
> do
> 	seq1 = read(sequence file)
> 	rsync repo
> 	seq2 = read(sequence file)
> until seq1==seq2 and !(seq1&1)

yep.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/