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

Re: Disk failure and lost of revision.

From: Brad Rhoads <bdrhoa_at_gmail.com>
Date: Wed, 9 Jan 2008 10:12:11 -0600

Perhaps a bit OT, but you might try http://www.grc.com/sr/spinrite.htm to
recover your disk. Note that I have no affiliation with GRC. In fact, I'm
personally 0/3 with the product, but they have a lot of positive
testimonials. Good luck.

On Jan 9, 2008 8:57 AM, Diego Hernan Borghetti <bdiego_at_gmail.com> wrote:

> Hello all:
> First a little of information:
> I have two repositories, 1 with 23456 revison and other with just 14
> revision, both repo are store in the same disk (a hd of 500 GB).
> Both repo are fsfs and all the information are binary files.
> My problem is the following, my primary disk (500GB) fail (some class of
> buffer error), i run fsck and fix the disk problem, after that i move both
> svn repo to a new disk, when i finish the migration run svnadmin verify in
> both repo and that is when i found the problem.
> The small repo are ok, verify all the revision and work fine, but the big
> repo (and most importan) finish with a:
> "svnadmin: no such revision 22397"
> So i check the db/revs directory and found that the file 22397 don't
> exist (probably this "go out" when fsck fix the inode lost).
> I try to run svnadmin recover but it finish ok, show the last revision ok
> but don't print any error about the revision 22397.
> My question is: it's possible recover a lost revision ?
> If the answer is "No": it's possible make another db skiping the lost
> revision ?
> Please CC my because i am not subscribe to this list.
> --
> Diego
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
> For additional commands, e-mail: users-help_at_subversion.tigris.org

Received on 2008-01-09 17:13:01 CET

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.