Re: truncated db/current file

Peter N. Lundblad wrote:
> On Thu, 12 May 2005, Jeffrey Chang wrote:
>
>> Investigating the error message, it appears that the db/current file
>> got truncated somewhere, and now has 0 file length.
>>
>> Is there any way to recover this file or regenerate it? This kind of
>> error doesn't seem to be something that svnadmin can handle.

> I haven't tested, but I *think* a dump/reload should resolve it.

No, that's not going to work. dump will just error too.
So, it will be necessary to create a current file.

Create a current file with the contents "<youngest revision> zzzzz zzzzz".
This should be sufficient to make read-only operations work, but it would be
*extremely* inadvisable to try committing anything. Now you should be able
to go ahead with the dump/reload as Peter suggested...

> Run svnadmin dump on the repo and redirect to a file. Run svnadmin lod on
> a new repo with input from the dump file. Save the old repo (IMPORTANT!)
> and move the new repo into place.
>
> Hmmm... I wonder how this file got truncated. It is written and moved into
> place atomically.

Ditto, this is very odd.

Max.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri May 13 18:07:31 2005