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

Re: No such revision after Filesystem-Crash

From: Ryan Schmidt <subversion-2006c_at_ryandesign.com>
Date: 2006-08-23 16:46:49 CEST

On Aug 23, 2006, at 15:16, Les Mikesell wrote:

> On Wed, 2006-08-23 at 04:11, Popp, Marc wrote:
>> We are using svn, version 1.2.3 (r15833) - compiled Sep 23 2005,
>> 14:50:26 on an SLES 9 Server. We are using fsfs to store the data.
>> After
>> an filesystem crash some files in the .../db/revs directory were
>> missing, but we got a backup of them.
>> I've restored the three missing files back to the directory and the
>> error message changed from
>> [error] Reference to non-existent node '19p.4.r1830/1202' in
>> filesystem
>> '/subversion/s2ds/db' [500, #160014]
>> To
>> [error] No such revision 1830 [500, #160006]
>> As mentioned above the file /subversion/s2ds/db/revs/1830 is
>> there. How
>> can I tell this to svn?
> I think you have to check out the head from what you restored,
> then copy in any newer files you happen to have in working
> copies, and commit them back.

Les, he shouldn't need to do this, because as he said, he was able to
restore all data from backup. The cases in which what you suggest is
necessary is when you've lost the latest revisions from the
repository because the backup was out-of-date, but he said this did
not occur.

Marc, if all the files of the repository that should be there are
there, then Subversion will just see them and just work. So either
all the files are not there, or perhaps they don't have the right
permissions? Check the permissions on the files that were still
there. Do they match the ones you put back?

> Can this be a feature request for some future version:
> allow a configuration option to specify an alternate location
> (on a different drive or network mount) to log updates
> between backups in a form that could be re-applied after
> a restore? The backup utility would clear the logs up to
> the backup point after completion.

You don't need to request such a feature since you can implement it
yourself today. Simply write a post-commit hook which runs "svnadmin
dump" on the just-committed revision and writes it in a special
place. Then nightly, or whenever you do your usual backups, you do a
full "svnadmin dump" on all revisions up to the current head, then
delete any incrementals up to that revision.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Aug 23 16:53:52 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.