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...
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.
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
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
Best regards, and thanks for this great tool which I find very well
designed. It is quickly gaining popularity around here :-)
Nicolas
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Nov 29 00:07:50 2006