[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 18:21:03 CEST

On Aug 23, 2006, at 17:40, 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?

>> 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?

> Thank you very much for your answer. It cost me almost a
> heardattack, because I really did forget to check the permissions.
> But they were and are fine. Read-Write for wwwrun (apache-user
> which serves svn).

I didn't think Subversion maintained any kind of index. I thought
just having the files in the right directories would be enough.

Did you also check the other directories for missing or corrupted or
zero-length files? Not just in db/revs but also in db/revprops?

What does "svnadmin verify /path/to/repo" say?

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