You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Cory Grimster <cg...@mindoka.com> on 2005/03/01 16:56:10 UTC
Invalid prop-mod flag in rev-file
Hi everyone,
While going over our company's backups, I've found out that svnadmin
dump has been failing on our repository for the past two weeks. I ran
svnadmin verify on the repository and got this:
[user@host repository]# svnadmin verify .
* Verified revision 0.
...
* Verified revision 65.
svn: Invalid prop-mod flag in rev-file
Seems to be failing on revision 66, which has a time stamp of Jan. 26th.
Our last good dump is from Feb. 19th. I have no idea why it would
suddenly be causing problems. Users can still work with the repository
just fine.
The server is Mandrake 10.1 Official running subversion 1.1.1 with an
fsfs back end.
I've run svnadmin recover on the repository (not sure if it even applies
to fsfs or just bdb), but it doesn't seem to find anything:
[user@host repository]# svnadmin recover .
Repository lock acquired.
Please wait; recovering the repository may take some time...
Recovery completed.
The latest repos revision is 872.
Any advice would be greatly appreciated.
-Cory
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Invalid prop-mod flag in rev-file
Posted by Cory Grimster <cg...@mindoka.com>.
Thanks, Max. Zeroing out that md5sum let the svnlook tree command run,
but the dump still fails.
FYI, it looks like there's more corruption in the rev file than just
that one spot. In fact I've been able to find corruption in many of the
revision files.
I've restored a backup and done an incremental dump of the work that's
been done since then and combined the two. svnadmin verify says the
produce is ok, so at least I haven't lost any data.
I will need to figure out how all those rev files got corrupted, though,
but that's between me and the server ;)
Thanks again.
-Cory
Max Bowsher wrote:
> Cory Grimster wrote:
>
>> I've dug deeper and have found the offending node in the rev file:
>>
>> svnlook tree -r66 --show-ids /svnroot /sites/intranet
>>
>> ...
>> catalog/ <krq.0.r66/33550254>
>> svn: Malformed text rep offset line in node-rev
>>
>> That's referring to this section of the rev file, I think:
>>
>> id: krq.0.r66/33550254
>> type: dir
>> count: 0
>> text: 66 33548492 1749 1749 39a7b28ert.t0dfee4650f283a4c4963
>> cpath: /sites/intranet/packages/general-comments/catalog
>> copyroot: 0 /
>>
>> The last item in the text: field looks like it should be a hex value.
>> I'm pretty sure "t.t" doesn't belong there...
>>
>> Of course I have no idea where that value comes from, so I'm unsure how
>> I can correct it.
>>
>> Any takers?
>
>
> That's an md5sum. So "rt.t" certainly isn't valid.
>
> Replacing the entire md5sum with all-zeros will act as a wildcard - that
> might allow the dump to proceed a further. Obviously, make a backup
> before conducting surgery.
>
> Max.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Invalid prop-mod flag in rev-file
Posted by Max Bowsher <ma...@ukf.net>.
Cory Grimster wrote:
> I've dug deeper and have found the offending node in the rev file:
>
> svnlook tree -r66 --show-ids /svnroot /sites/intranet
>
> ...
> catalog/ <krq.0.r66/33550254>
> svn: Malformed text rep offset line in node-rev
>
> That's referring to this section of the rev file, I think:
>
> id: krq.0.r66/33550254
> type: dir
> count: 0
> text: 66 33548492 1749 1749 39a7b28ert.t0dfee4650f283a4c4963
> cpath: /sites/intranet/packages/general-comments/catalog
> copyroot: 0 /
>
> The last item in the text: field looks like it should be a hex value.
> I'm pretty sure "t.t" doesn't belong there...
>
> Of course I have no idea where that value comes from, so I'm unsure how
> I can correct it.
>
> Any takers?
That's an md5sum. So "rt.t" certainly isn't valid.
Replacing the entire md5sum with all-zeros will act as a wildcard - that
might allow the dump to proceed a further. Obviously, make a backup before
conducting surgery.
Max.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Invalid prop-mod flag in rev-file
Posted by Cory Grimster <cg...@mindoka.com>.
I've dug deeper and have found the offending node in the rev file:
svnlook tree -r66 --show-ids /svnroot /sites/intranet
...
catalog/ <krq.0.r66/33550254>
svn: Malformed text rep offset line in node-rev
That's referring to this section of the rev file, I think:
id: krq.0.r66/33550254
type: dir
count: 0
text: 66 33548492 1749 1749 39a7b28ert.t0dfee4650f283a4c4963
cpath: /sites/intranet/packages/general-comments/catalog
copyroot: 0 /
The last item in the text: field looks like it should be a hex value.
I'm pretty sure "t.t" doesn't belong there...
Of course I have no idea where that value comes from, so I'm unsure how
I can correct it.
Any takers?
Cory Grimster wrote:
> Hi everyone,
>
> While going over our company's backups, I've found out that svnadmin
> dump has been failing on our repository for the past two weeks. I ran
> svnadmin verify on the repository and got this:
>
> [user@host repository]# svnadmin verify .
> * Verified revision 0.
> ...
> * Verified revision 65.
> svn: Invalid prop-mod flag in rev-file
>
> Seems to be failing on revision 66, which has a time stamp of Jan. 26th.
> Our last good dump is from Feb. 19th. I have no idea why it would
> suddenly be causing problems. Users can still work with the repository
> just fine.
>
> The server is Mandrake 10.1 Official running subversion 1.1.1 with an
> fsfs back end.
>
> I've run svnadmin recover on the repository (not sure if it even applies
> to fsfs or just bdb), but it doesn't seem to find anything:
>
> [user@host repository]# svnadmin recover .
> Repository lock acquired.
> Please wait; recovering the repository may take some time...
>
> Recovery completed.
> The latest repos revision is 872.
>
> Any advice would be greatly appreciated.
>
> -Cory
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Invalid prop-mod flag in rev-file
Posted by Cory Grimster <cg...@mindoka.com>.
Hasn't anyone seen this error before? Some help would be really great.
I'm concerned that our repository is corrupted in some weird and
wonderful way.
Cory Grimster wrote:
> Hi everyone,
>
> While going over our company's backups, I've found out that svnadmin
> dump has been failing on our repository for the past two weeks. I ran
> svnadmin verify on the repository and got this:
>
> [user@host repository]# svnadmin verify .
> * Verified revision 0.
> ...
> * Verified revision 65.
> svn: Invalid prop-mod flag in rev-file
>
> Seems to be failing on revision 66, which has a time stamp of Jan. 26th.
> Our last good dump is from Feb. 19th. I have no idea why it would
> suddenly be causing problems. Users can still work with the repository
> just fine.
>
> The server is Mandrake 10.1 Official running subversion 1.1.1 with an
> fsfs back end.
>
> I've run svnadmin recover on the repository (not sure if it even applies
> to fsfs or just bdb), but it doesn't seem to find anything:
>
> [user@host repository]# svnadmin recover .
> Repository lock acquired.
> Please wait; recovering the repository may take some time...
>
> Recovery completed.
> The latest repos revision is 872.
>
> Any advice would be greatly appreciated.
>
> -Cory
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org