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

RE: Support for filesystem snapshots (?)

From: Vallon, Justin <Justin.Vallon_at_deshaw.com>
Date: Mon, 2 Aug 2010 14:41:29 -0400

From: Les Mikesell [mailto:lesmikesell_at_gmail.com]
> On 8/2/2010 11:42 AM, Vallon, Justin wrote:
> > So, my follow up is: If I unplug the network cable between svn-commiter and filesystem, will the repository be corrupt?
> >
> > If yes, then the underlying database is not atomic and therefore not transactional.
> >
> > If no, then the server can take a snapshot at any point in time, and the snapshot is guaranteed to be consistent.
> A better match for comparison would be what happens if the server
> crashes mid-transaction. A backup taken with the server active might
> catch the same state. So the more relevant question would be if the
> repository will always be consistent after a server crash.

That is the situation I raised. If the network connection between the host that is modifying the repository and the filesystem that houses the repository is lost, will be repository be (a) corrupt, (b) require cleanup (locks, etc), (c) pristine?

(c) is great
(b) is ok
(a) means the operations are not transactional


(c) snapshots work
(b) snapshots work, but need a cleanup after restore
(a) snapshots don't work; repository is not transactional, either

Received on 2010-08-02 20:44:18 CEST

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

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