RE: Corrupt Repository

Thanks Max,

I followed your instructions with apparent success.
I can now do a complete fresh checkout and the file in question
seems to be ok.

I've done a dump of the repository and "svnadmin verify" indicates
no errors.

thanks
Russell Thamm

PS I had supplied details as requested by kfogel but unfortunately
I failed to check the To field in outlook and I sent the response
to kfogel rather than the list.

Following are the details:

I'm running Subversion 1.1.1 with apache 2.0.52 (ssl 0.9.7e).

At the beginning of November, I upgraded from subversion 0.30.0. The dump that I took then
was 61 MBytes long (1 Nov).

Nothing untoward has happened (no full disk etc). I only noticed the problem when I tried to
checkout a complete fresh copy.

I'm not sure when the corruption occurred. Normal commit/refresh operations don't
exhibit the error, so the error may have been around for a while.

I can't do a dump now (Checksum mismatch error).

The file in question is a bitmap file trunk/msvc/apps/manager/Recorder/help/images/recorder.bmp.

-----Original Message-----
From: Max Bowsher [mailto:maxb@ukf.net]
Sent: Wednesday, 15 December 2004 1:33 AM
To: Thamm, Russell
Cc: users@subversion.tigris.org
Subject: Re: Corrupt Repository

kfogel@collab.net wrote:
> "Thamm, Russell" <russell.thamm@dsto.defence.gov.au> writes:
>> This morning, I tried to check-out a fresh copy of my repository and
>> I got the error:
>>
>> REPORT request failed on '/svn/ssc/!svn/vcc/default blah blah blah
>>
>> In the apache error log, I found the following error:
>>
>> Checksum mismatch on rep 'kn':\n blah blah blah
>>
>> Can I repair my repository?
>>
>> I have an up-to-date working directory. I could use this to recreate
>> my repository but I would then lose my history.
>>
>> The really annoying thing is that the corrupt file hasn't be
>> modified since day 1, it is still version 1.
>
> We'd love a lot more detail about your setup: version of Subversion,
> type of repository, the exact file, etc. Has your disk filled up
> recently or anything? Is the repository large, can you save it before
> you do anything further?

Reiterating that the above would be very interesting.

Regarding repair:

FIRST, MAKE A BACKUP OF THE REPOSITORY

I'm going to assume you have the Berkeley DB db_dump and db_load programs
available.

cd repository/db
db_dump -p representations > reps.txt
your-favourite-editor reps.txt

Find the line which is exactly the string " kn".
On the line below, look for the substring that is like:

(md5 16 some-mess-here))

Change the some-mess-here to 16 repetitions of the 3-character string "\00".

Save and exit.

db_load representations < reps.txt

Now, try "svnadmin dump" on the repository.

If there are further errors, the best course of action would probably be for
you to give me a tarball of the repository for repair.

Max.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Dec 15 04:58:52 2004