malformed file problem -- version 1.5.7

["James D. Parra" <ja...@musicreports.com>]

Hello,

One of my users committed a file to svn and now some users are getting a
'malformed file' error. These users can no longer check out or commit.
'Svnadmin verify /svnrepos' doesn't show any problems, however 'malformed
file' appears when I do a nightly dump export; 

svnadmin dump /svnrepos > /backup/svnrepos.svn_dump
<snip>
* Dumped revision 11529.
svnadmin: Malformed file
<end>

I believe the problem lies within revision numbers 11530 and 11532.  Other
users who are working on other projects are not having problems. We are
currently at revision 11784.  Is there a way that I can repair this?

Many thanks in advance,

James

RE: malformed file problem -- version 1.5.7

["James D. Parra" <ja...@musicreports.com>]

 
> Is there a way that I can repair this?
No idea, sorry.  But:

> Is there a way to roll back to revision 11529 and start there? 

Try svnadmin dump with the -r parameter to dump just the revisions you
want to keep, then svnadmin load to load them into a new repository.
Any checkouts of r11529 or earlier should be OK; if you have a later
checkout then you'll need to delete it and re-checkout.

> Should I remove all the revision number files greater that 11529

Hand-editing the repository sounds like a bad idea*... you might get rid
of this corruption but introduce a different corruption.
Using dump/load should give you a valid repository.

Kind regards,

Jon

[*] It's number zero on the "Subversion Worst Practices" guide:
http://www.red-bean.com/fitz/presentations/2007-07-27-OSCON-svn-worst-pr
actices.pdf
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Thank you, Jon, for the info. 

Before I do such a major rollback, is there a way to rollback a particular
project within the repos without affecting other projects or, to be more
concise, maintain revision numbers for the other projects that are not
affected by the mal-formed file error?

Thanks again for your help.

James 

RE: malformed file problem -- version 1.5.7

[Jon Foster <Jo...@cabot.co.uk>]

Hi,

James D. Parra [mailto:jamesp@musicreports.com] wrote:
> Is there a way that I can repair this?
No idea, sorry.  But:

> Is there a way to roll back to revision 11529 and start there? 

Try svnadmin dump with the -r parameter to dump just the revisions
you want to keep, then svnadmin load to load them into a new repository.
Any checkouts of r11529 or earlier should be OK; if you have a later
checkout then you'll need to delete it and re-checkout.

> Should I remove all the revision number files greater that 11529

Hand-editing the repository sounds like a bad idea*... you might get
rid of this corruption but introduce a different corruption.
Using dump/load should give you a valid repository.

Kind regards,

Jon

[*] It's number zero on the "Subversion Worst Practices" guide:
http://www.red-bean.com/fitz/presentations/2007-07-27-OSCON-svn-worst-pr
actices.pdf


**********************************************************************
This email and its attachments may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Cabot Communications Ltd.

If you are not the intended recipient of this email and its attachments, you must take no action based upon them, nor must you copy or show them to anyone.

Cabot Communications Limited
Verona House, Filwood Road, Bristol BS16 3RY, UK
+44 (0) 1179584232

Co. Registered in England number 02817269

Please contact the sender if you believe you have received this email in error.

**********************************************************************


______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________

RE: malformed file problem -- version 1.5.7

["James D. Parra" <ja...@musicreports.com>]

 
One of my users committed a file to svn and now some users are getting a
'malformed file' error. These users can no longer check out or commit.
'Svnadmin verify /svnrepos' doesn't show any problems, however 'malformed
file' appears when I do a nightly dump export; 

svnadmin dump /svnrepos > /backup/svnrepos.svn_dump <snip>
* Dumped revision 11529.
svnadmin: Malformed file
<end>

I believe the problem lies within revision numbers 11530 and 11532.  Other
users who are working on other projects are not having problems. We are
currently at revision 11784.  Is there a way that I can repair this?
~~~~~~~~~~~~~~~~~~~~~~~


Is there a way to roll back to revision 11529 and start there?  Should I
remove all the revision number files greater that 11529 and have my users
check out again?  Trying to figure out the best way to fix this.

Many thanks,

James