Filesystem corrupt issue in repo
Hi, I have a repo that returns no errors with 'svnadmin recover' or 'svnadmin verify', but dumping and loading into a new repo gives me: svnadmin: E160004: Filesystem is corrupt svnadmin: E200014: Checksum mismatch while reading representation: expected: aa2f4b4990d8a287d104dd30ddf50ab0 actual: 9ba98374833678825028dcadcd521ece This is a simple svnadmin dump svnrepo > repo-backup and svnadmin load svnrepocopy < repo-backup. I tried filtering out the offending branch but it gives me a: svndumpfilter: E23: Invalid copy source path '/branches/bugfix-1_2/some-file-in-my-repo.txt' System info: svnadmin --version svnadmin, version 1.9.7 (r1800392) cat /proc/version Linux version 4.15.0-38-generic (buildd@lcy01-amd64-023) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #41-Ubuntu SMP Wed Oct 10 10:59:38 UTC 2018 Hope i have a shot at fixing it, right now my dumps are not a viable backup solution :( regards, Dennis
Error: Could not access revision times
Anyone seen this error before? This is in the Apache error logs and not sure what it means: [dav:error] Could not access revision times. [500, #175002] Searching at svn.haxx.se only finds the commit where the message was added. I think it is happening for a user doing a checkout but I am trying to get the client side of this. -- Thanks Mark Phippard http://markphip.blogspot.com/
Re: Error: Could not access revision times
Hello, On Wed, Nov 7, 2018 at 4:10 PM, Mark Phippard wrote: > > Anyone seen this error before? This is in the Apache error logs and not sure > what it means: > > [dav:error] Could not access revision times. [500, #175002] > > Searching at svn.haxx.se only finds the commit where the message was added. > I think it is happening for a user doing a checkout but I am trying to get > the client side of this. Do you use something non-standard like SVNKit to access the repositories via Apache? -- With best regards, Pavel Lyalyakin VisualSVN Team
Re: Error: Could not access revision times
On Wed, Nov 7, 2018 at 8:16 AM Pavel Lyalyakin < pavel.lyalya...@visualsvn.com> wrote: > Hello, > > On Wed, Nov 7, 2018 at 4:10 PM, Mark Phippard wrote: > > > > Anyone seen this error before? This is in the Apache error logs and not > sure what it means: > > > > [dav:error] Could not access revision times. [500, #175002] > > > > Searching at svn.haxx.se only finds the commit where the message was > added. I think it is happening for a user doing a checkout but I am trying > to get the client side of this. > > Do you use something non-standard like SVNKit to access the > repositories via Apache? > > Yes, the user that got this error was using SVNKit. I do not know if it was via Jenkins, Eclipse or something else and that is why I am not sure what the command was. I asked to recreate using SVN command line so we could better understand what triggered it. -- Thanks Mark Phippard http://markphip.blogspot.com/
Re: Filesystem corrupt issue in repo
On Wed, Nov 7, 2018 at 2:05 PM Dennis Jakobsen wrote: > > Hi, > > I have a repo that returns no errors with 'svnadmin recover' or > 'svnadmin verify', but dumping and loading into a new repo gives me: > svnadmin: E160004: Filesystem is corrupt > svnadmin: E200014: Checksum mismatch while reading representation: > expected: aa2f4b4990d8a287d104dd30ddf50ab0 > actual: 9ba98374833678825028dcadcd521ece > > This is a simple svnadmin dump svnrepo > repo-backup and svnadmin load > svnrepocopy < repo-backup. > > I tried filtering out the offending branch but it gives me a: > svndumpfilter: E23: Invalid copy source path > '/branches/bugfix-1_2/some-file-in-my-repo.txt' > > System info: > svnadmin --version > svnadmin, version 1.9.7 (r1800392) > cat /proc/version > Linux version 4.15.0-38-generic (buildd@lcy01-amd64-023) (gcc version > 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #41-Ubuntu SMP Wed Oct 10 10:59:38 UTC 2018 > > Hope i have a shot at fixing it, right now my dumps are not a viable > backup solution :( This might be due to this bug in the checksum verification: https://issues.apache.org/jira/browse/SVN-4722 (checksum fail during commit when delta is 16K) The fix was released in 1.9.9. Also note that 1.10.3 and 1.11.0 have been released already. Those should not be affected by this bug, so it might also be a good opportunity to upgrade to these more recent releases ... -- Johan
