On 7/2/07, Andreas Hasenack <firstname.lastname@example.org> wrote:
> On Sat, Jun 30, 2007 at 09:24:59PM +0200, Erik Huelsmann wrote:
> > Hi Chris,
> >> No of course things happen which we have no control over. That's part of
> >> the fun/headache of IT right? ;-)
> > Yes :-)
> >> What I am saying I that I am surprised there are no tools available to
> >> be able to recover a repository into a usable state. A simple(no such
> >> thing I know) tool is all that is needed to be able to mark a revision
> >> as bad and let and svnadmin dump/verify and the other tools work as they
> >> should.
> >> Do you think this is unreasonable?
> > Absolutely not! It's a very reasonable request! The only thing is that
> > this is the default in-production behaviour already: if a damaged
> > revision is not required to construct a later revision, it's simply
> > skipped and no damage will be detected.
> Is it? Maybe I don't have the deltas inner workings correctly in my
> mind, but consider this simple test:
> [andreas@pandora x]$ svnadmin create test-repo
> [andreas_at_pandora x]$ svn mkdir file://$(pwd)/test-repo/dir1 -m "- created dir 1"
> Commit da revisão 1.
> [andreas_at_pandora x]$ svn mkdir file://$(pwd)/test-repo/dir2 -m "- created dir 2"
> Commit da revisão 2.
> [andreas@pandora x]$ echo corrupt > test-repo/db/revs/1
> [andreas@pandora x]$ svnadmin verify test-repo/
> * Verified revision 0.
> svnadmin: Can't set position pointer in file 'test-repo/db/revs/1': Invalid argument
> Does the dir2 creation depend on dir1? If yes, then this error is valid.
Ofcourse you get an error there. I said "if a damaged revision is not
required to construct a later revision, ...". What you're doing there
is subsequently checking out *all* revisions, meaning that the damaged
revision itself and all revisions based on it are checked out. And
still you expect no errors?
Received on Tue Jul 3 17:19:23 2007