David Hopkins wrote on Thu, Sep 15, 2011 at 10:30:46 +0800: > Greetings, > > I have an SVN repo that is failing svnadmin verify on revision 192. > > For some reason the verify output says: > > [...various successful revisions...] > * Verified revision 191. > svnadmin: Can't read file 'E:\Repositories\Client_Name\db\revs\0\16 > 2': End of file found > > I'm not sure why the verification command for revision 192 would throw > an error description for revision 162. Revision 192 affected a > completely different part of the repository to revision 162, so there is > > no obvious relationship between them. >
Possibly due to rep-sharing? Does db/revs/0/192 contain the number "162" in ASCII decimal delimited by whitespace? You can check that with the following command: grep -a "^text:" db/revs/0/192 Does 'svnadmin dump -r 162 >NUL' work ? To answer your question: yes, most definitely a copy of the r192 (and/or r162) rev file would allow to pinpoint the problem, however you might not want to share those files on a public list as they may contain sensitive data (versioned file contents). > All the revisions from 193 to 332 (HEAD) are ok. It might be a one-off. > > This looks like a FSFS-backed repository (I am very new to SVN and > inherited the server from someone else!). The server is VisualSVN 2.1.4, > > which is based on SVN 1.6.13. > > The clients are mostly TortoiseSVN 1.6.16, which uses SVN 1.6.17. > > What steps should I take to fix the corrupted revision? Is there more > information that I should provide? (eg a copy of the rev 192 file?) This > > problem is causing checkouts and updates to fail for files that were > last modified in that revision. > > Regards, > > David Hopkins > Serck Controls > > > ===== PRIVACY AND CONFIDENTIALITY NOTICE ===== > The information contained in this message is intended for the named recipient > only. It may contain privileged and confidential information. If you are > not the intended recipient, you must not copy, distribute, take any action in > reliance on it, or disclose any details of the message to any person, firm or > corporation. If you have received this message in error, please notify the > sender immediately by reply e-mail and delete all copies of this transmission > together with any attachments. > The views or opinions expressed in this e-mail or any attachment are not > necessarily those of Serck Controls Pty Ltd. > NOTE - You should carry out your own virus checks before opening any > attachment. >
