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

Re: backing up fsfs repo

From: Mathias Weinert <mathias.weinert_at_gfa-net.de>
Date: 2006-07-06 08:43:35 CEST

Daniel Berlin wrote:
> Nico Kadel-Garcia wrote:
> > ----- Original Message -----
> > From: "Daniel Berlin" <dberlin@dberlin.org>
> > To: "Nico Kadel-Garcia" <nkadel@comcast.net>
> > Cc: <users@subversion.tigris.org>
> > Sent: Wednesday, July 05, 2006 11:35 AM
> > Subject: Re: backing up fsfs repo
> >
> >> This is wrong.
> >> The only way you can get screwed up is if you do not copy the current
> >> file first.
> >> As long as you do that, it does not matter what writes occur afterwards,
> >> the repo will still be fine (this is because old revisions are immutable
> >> in FSFS).
> >
> > How are you going to force tar to do the current files last?
> No, it needs to copy them *first*.
> (As i said, you get screwed up if you don't copy it first).
> And the answer, of course, is simple: give tar a list of file names
> ("-T" option) to archive, and specify it first in the list.
> tar will preserve that order.

I think Daniel didn't mean to say "do the current files last". What he
said is "copy the current file first". Please note that he said "file"
not "files". He probably meant the file named "current" which resides
in the db directory of the repository.

In the current file you can see, beside other information, the current
revision number of the repository. If you copy this file first you may
later copy revs and revprops files for newer revisions but that doesn't
hurt, Subversion will ignore them.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jul 6 08:45:07 2006

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.