You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Razvan STANESCU <pa...@signumcreative.com> on 2006/10/09 05:24:56 UTC
yet another "can't read length line"
Hi there,
I have a problem with a broken version in my SVN repository.
Since I was preparing to upgrade to subversion-1.4, I tried
to dump the repository and I got the following message:
svnadmin: Can't read length line in file '/srv/svn/db/revs/12425'
I checked the list, but no solution I've tried worked.
A. trying to dump everything but not 12425 gave me the message
above, here is my session
> # svnadmin dump /srv/svn -r 0:12424 --incremental > D-1
> ...
> # svnadmin dump /srv/svn -r 12426:HEAD --incremental > D-2
> * Dumped revision 12426.
> ...
> * Dumped revision 12434.
> svnadmin: Can't read length line in file '/srv/svn/db/revs/12425'
B. trying to fix the repository with "fsfverify" failed also, here
is my session (the full output is in the attachment)
> # ./fsfsverify/fsfsverify.py -f /srv/svn/db/revs/12425
> ...
> NodeRev Id: ja7.1bp.r12425/57145
> type: file
> pred: ja7.1bp.r12414/38823
> text: INVALID 12425 0 31 1749 b393e94d5f878cd0288f5174a2100d62
> cpath: /trunk/java/avmob/jboss-hello/sms-profile/bin/build.xml
> copyroot: 11933 /trunk/java/avmob
> Invalid rep header found at 0 (^@^@^@^@^@)!
> Found problem in NodeRev ja7.1bp.r12425/57145 (57145)
> text: INVALID 12425 0 31 1749 b393e94d5f878cd0288f5174a2100d62
> At offset 0
> Original text rep located at 0
> Traceback (most recent call last):
> File "./fsfsverify/fsfsverify.py", line 756, in ?
> copy_len = 4096 + header_len
> NameError: name 'header_len' is not defined
I'm using
- svn, version 1.3.1 (r19032)
- neon, version 0.24.7
- libapr1/libaprutil1, version 1.2.7
- FSFS format
As an additional information, one month ago I reorganized the
repository, meaning I changed the tree moving several projects
from one directory to another...
Could anybody help me to recover the repository? I'm not tied to the
version 12425, but now we are at version 13293 which represents about
one month of work.
If someone needed it, I could provide a link to the broken revision
file...
Thank you for any help!
--
pappy
Re: yet another "can't read length line"
Posted by Pappy Răzvan STĂNESCU <pa...@signumcreative.com>.
John Szakmeister wrote:
>>>...
>>> File "./fsfsverify/fsfsverify.py", line 756, in ?
>>> copy_len = 4096 + header_len
>>> NameError: name 'header_len' is not defined
>
> I've seen this before, and it was generally in the presence of a
> more severe corruption.
>
> ...
>
> If you can provide me a link to the file, I'll take a look at it.
> I suspect there is going to be some data loss though.
This is what I suspect too (due to ^@^@^@^@^@), there is a
Reiser filesystem there and I remember this fstype caused me
some trouble in the past...
I sent you the link directly... I don't care if that certain revision
is lost, I whould only like to recover the rest...
10x
--
pappy
Re: yet another "can't read length line"
Posted by John Szakmeister <jo...@szakmeister.net>.
----- Razvan STANESCU <pa...@signumcreative.com> wrote:
> Hi there,
>
> I have a problem with a broken version in my SVN repository.
>
> Since I was preparing to upgrade to subversion-1.4, I tried
> to dump the repository and I got the following message:
>
> svnadmin: Can't read length line in file '/srv/svn/db/revs/12425'
>
> I checked the list, but no solution I've tried worked.
>
> A. trying to dump everything but not 12425 gave me the message
> above, here is my session
>
> > # svnadmin dump /srv/svn -r 0:12424 --incremental > D-1
> > ...
> > # svnadmin dump /srv/svn -r 12426:HEAD --incremental > D-2
> > * Dumped revision 12426.
> > ...
> > * Dumped revision 12434.
> > svnadmin: Can't read length line in file '/srv/svn/db/revs/12425'
>
> B. trying to fix the repository with "fsfverify" failed also, here
> is my session (the full output is in the attachment)
>
> > # ./fsfsverify/fsfsverify.py -f /srv/svn/db/revs/12425
> > ...
> > NodeRev Id: ja7.1bp.r12425/57145
> > type: file
> > pred: ja7.1bp.r12414/38823
> > text: INVALID 12425 0 31 1749 b393e94d5f878cd0288f5174a2100d62
> > cpath: /trunk/java/avmob/jboss-hello/sms-profile/bin/build.xml
> > copyroot: 11933 /trunk/java/avmob
> > Invalid rep header found at 0 (^@^@^@^@^@)!
> > Found problem in NodeRev ja7.1bp.r12425/57145 (57145)
> > text: INVALID 12425 0 31 1749 b393e94d5f878cd0288f5174a2100d62
> > At offset 0
> > Original text rep located at 0
> > Traceback (most recent call last):
> > File "./fsfsverify/fsfsverify.py", line 756, in ?
> > copy_len = 4096 + header_len
> > NameError: name 'header_len' is not defined
I've seen this before, and it was generally in the presence of a more severe corruption.
> I'm using
> - svn, version 1.3.1 (r19032)
> - neon, version 0.24.7
> - libapr1/libaprutil1, version 1.2.7
> - FSFS format
>
> As an additional information, one month ago I reorganized the
> repository, meaning I changed the tree moving several projects
> from one directory to another...
>
> Could anybody help me to recover the repository? I'm not tied to the
> version 12425, but now we are at version 13293 which represents about
> one month of work.
>
> If someone needed it, I could provide a link to the broken revision
> file...
>
> Thank you for any help!
If you can provide me a link to the file, I'll take a look at it. I suspect there is going to be some data loss though.
-John
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org