Re: corrupt repository

On Mar 21, 2006, at 20:24, Christopher L Merrill wrote:

> We were getting low on disk space so we remapped the /opt hierarch
> (including
> /opt/subversion where all our respositories are) and rsynced all
> the files
> to the new area. This was done by our sysadmin who is pretty
> good. He assured
> us that all timestamps and permissions were preserved and I have no
> reason to
> doubt it.

Is this new area on an NFS mount? If so, BerkeleyDB won't work like
that.

> Can anybody suggest what I should try next? I am pretty darn sure
> these
> files did not get corrupted by the move process, but I'm starting
> to get
> worried that we've lost our entire repository.

Do you have up-to-date backups? Dumpfiles?

Once you get this sorted out, consider moving the repository to FSFS,
since it cannot suffer from these problems. How to do so is in the FAQ.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Mar 21 23:33:41 2006