malformed file problem -- version 1.5.7
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 * Dumped revision 11529. svnadmin: Malformed file 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
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 * Dumped revision 11529. svnadmin: Malformed file 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
RE: malformed file problem -- version 1.5.7
> 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
