Re: No such revision after Filesystem-Crash

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.

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.

-- 
  Les Mikesell
   lesmikesell@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org