You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Kazuyoshi Furutaka <fu...@jaea.go.jp> on 2008/10/06 01:37:34 UTC
how can I recover my rep. from "Malformed svndiff data in
representatioN"?
Hi all,
I've just started using a subversion repo. which now has only 5
revisions, on a x86_64 linux machine running Fedora 9.
The version of the subversion (rpm package) is:
subversion-1.4.6-7.x86_64
subversion-1.4.6-7.i386
The repo uses FSFS and is mainly accessed via svn+ssh.
A few days ago, when I tried to checkout the latest revision,
I got the following message
svn: Decompression of svndiff data failed
and some files were missing from the checked-out copy.
So I used "fsfsverify.py" http://www.szakmeister.net/fsfsverify/.
Using the script I found that THE FIRST REVISION seems to be
corrupted. Then I run the script over the revision 1 with and
without "-f" a few dozen times, and finally got the following
message:
Traceback (most recent call last):
File "./work/fsfsverify/fsfsverify.py", line 1134, in <module>
options.dumpWindows)
File "./work/fsfsverify/fsfsverify.py", line 571, in verify
svndiff = Svndiff(f, self.length)
File "./work/fsfsverify/fsfsverify.py", line 461, in __init__
(self.startingOffset)
__main__.InvalidSvndiffHeader: Invalid svndiff header at offset 887125
After that, when I do for example `svn diff` I get the following
message:
Malformed svndiff data in representation
`svnadmin verify` ends with the same message.
* Verified revision 0.
svnadmin: Malformed svndiff data in representation
(How) is it possible to remedy this situation?
There're only 5 revisions in the repo, and the only modification
we did in the first three revisions were deletion of useless files,
so it's not difficult to build the repo/revisions again from scratch.
But it's going to have many revisions and I don't want to encounter
the same situation again...
Thanks in advance,
Yours,
Kazuyoshi
--
Kazuyoshi Furutaka
furutaka _dot_ kazuyoshi _at_ jaea _dot_ go _dot_ jp
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: how can I recover my rep. from "Malformed svndiff data in
representatioN"?
Posted by Kazuyoshi Furutaka <fu...@jaea.go.jp>.
Hi all...
Thanks John for your interest.
From: "John Szakmeister" <jo...@szakmeister.net>
Subject: Re: how can I recover my rep. from "Malformed svndiff data in representatioN"?
Date: Mon, 6 Oct 2008 21:22:08 -0400
> > I've just started using a subversion repo. which now has only 5
> > revisions, on a x86_64 linux machine running Fedora 9.
> > The version of the subversion (rpm package) is:
> > subversion-1.4.6-7.x86_64
> > subversion-1.4.6-7.i386
> > The repo uses FSFS and is mainly accessed via svn+ssh.
> >
> > A few days ago, when I tried to checkout the latest revision,
> > I got the following message
> > svn: Decompression of svndiff data failed
> > and some files were missing from the checked-out copy.
>
> Can you provide more information about your setup? Do you have a good
> link? Was it LAN access or WAN? Was it a large commit?
The server and clients are on the same LAN (a few hops)
and I think the link between the two machines is good.
The server provides its access through svn+ssh with
svnserve and sshd (provided by a Fedora package
openssh-server-5.1p1-2.fc9.x86_64).
The svnserve is configured to allow
anon-access = read
auth-access = write
(These are the only changes made to our svnserve.conf)
At present I'm the only one user of the server and
my access is mainly from a linux machine (i386, Fedora
9) with svn provided by the subversion-1.4.6-7.i386
rpm package.
There are about 430 files in the failed revision:
many of these are c/fortran source and object files.
> Can I see the corrupted revision? And get the full output of fsfsverify?
This morning I've tried to recover (fake) the failed
revision by loading a dump obtained on a different
machine by making a cloned repository (but failed though:
I still get the same "svn: Malformed svndiff data in
representation" error when checking out for example).
Later I'll send you the corrupted revision and the full
output of the script by a private email.
Thanks in advance.
Yours,
Kazuyoshi
--
Kazuyoshi Furutaka
furutaka _dot_ kazuyoshi _at_ jaea _dot_ go _dot_ jp
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: how can I recover my rep. from "Malformed svndiff data in representatioN"?
Posted by John Szakmeister <jo...@szakmeister.net>.
On Sun, Oct 5, 2008 at 9:37 PM, Kazuyoshi Furutaka
<fu...@jaea.go.jp> wrote:
> Hi all,
>
> I've just started using a subversion repo. which now has only 5
> revisions, on a x86_64 linux machine running Fedora 9.
> The version of the subversion (rpm package) is:
> subversion-1.4.6-7.x86_64
> subversion-1.4.6-7.i386
> The repo uses FSFS and is mainly accessed via svn+ssh.
>
> A few days ago, when I tried to checkout the latest revision,
> I got the following message
> svn: Decompression of svndiff data failed
> and some files were missing from the checked-out copy.
Can you provide more information about your setup? Do you have a good
link? Was it LAN access or WAN? Was it a large commit?
> So I used "fsfsverify.py" http://www.szakmeister.net/fsfsverify/.
> Using the script I found that THE FIRST REVISION seems to be
> corrupted. Then I run the script over the revision 1 with and
> without "-f" a few dozen times, and finally got the following
> message:
> Traceback (most recent call last):
> File "./work/fsfsverify/fsfsverify.py", line 1134, in <module>
> options.dumpWindows)
> File "./work/fsfsverify/fsfsverify.py", line 571, in verify
> svndiff = Svndiff(f, self.length)
> File "./work/fsfsverify/fsfsverify.py", line 461, in __init__
> (self.startingOffset)
> __main__.InvalidSvndiffHeader: Invalid svndiff header at offset 887125
>
> After that, when I do for example `svn diff` I get the following
> message:
> Malformed svndiff data in representation
>
> `svnadmin verify` ends with the same message.
> * Verified revision 0.
> svnadmin: Malformed svndiff data in representation
>
>
> (How) is it possible to remedy this situation?
>
> There're only 5 revisions in the repo, and the only modification
> we did in the first three revisions were deletion of useless files,
> so it's not difficult to build the repo/revisions again from scratch.
> But it's going to have many revisions and I don't want to encounter
> the same situation again...
Can I see the corrupted revision? And get the full output of fsfsverify?
Thanks!
-John
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org