[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Question regarding a "malformed header" problem

From: John Szakmeister <john_at_szakmeister.net>
Date: 2006-11-29 10:35:48 CET

----- Nicolas Brisset <Nicolas.Brisset@eurocopter.com> wrote:
> Hi,
>
> We have recently started using svn and are quite happy with it. It seems
> to be rock solid and gained user confidence quickly, however we have
> just met one case of "svn: Found malformed header in revision file"
> which makes us feel sort of uncomfortable...
> We are using version 1.3.0 on a Sun Solaris 8 machine, with a local
> (file:///) repository, which happens to be on a local disk (so no NFS
> involved here). The problem is not too critical (at least for now) as
> all commands requiring the repository now fail with that error, which
> was hence discovered very quickly.
> We have made a plain copy of the repository, where we tried to remove
> the guilty revision (number 34) by simply replacing "34" with "33" in
> the "current" file, and removing the files named "34" from revs/ and
> revprops/. As this is the last revision, we hope that this won't break
> anything (but we would be glad to have that confirmed by more
> experienced people). In our quick tests it seemed to work fine...

I'm not sure about that. At a quick glance that seems fine. I probably would have dumped the first 33 revs and loaded it into a new repository though.

> Googling around on a quest for a solution we found the fsfsverify.py
> script, which throws an exception on the incriminated rev file (so not
> really helpful to us), and noticed that a recent commit included in
> 1.4.2 seems to have fixed such situations resulting from write
> errors.

If you can provide me a copy of the bad revision, I can update the script to fix the file.

> So, to sum up we have 3 questions right now:
> 1) is it safe to delete the last rev and revprops files and change the
> number in current accordingly
> 2) should we upgrade to 1.4.2 to be safe

I'd definitely upgrade to 1.4.2.

> 3) is there anything better to do ? We can't send the repository, but we
> could possibly send some rev files or analyse them if you tell us what
> to look at

Not at this point, except to send me a copy of the bad rev file so I can update fsfsverify.

-John

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Nov 29 10:36:19 2006

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.