Op 27-apr.-2016 16:17 schreef "Terry Dooher" <terry.doo...@naturalmotion.com >: > > Hi all, > > > > I’m in the process of dump/loading our repositories to take advantage of FSFS format 7. Looking at the change list for 1.9.4 (out tomorrow), it shows: > > fsfs: fix a rare source of incomplete dump files and reports (r1717876) > > > > I’m having trouble finding a layman’s explanation of what this issue means, however. (I’ve read https://issues.apache.org/jira/browse/SVN-4554 but it doesn’t make much sense to me.) In practical terms, I’m running through several hundred thousand revisions across 20 repositories. Is there a chance this bug could happen silently and corrupt a dump in a way that wouldn’t be picked up during svnadmin load (or by ‘svnadmin verify’ following the load)? > > > > I’m on 1.9.2 now. Should I wait for 1.9.4 to do this? >
I would use at least 1.9.3 for the process running 'svnadmin dump', because of this fix in 1.9.3: * svnadmin dump: preserve no-op changes (r1709388 et al, issue #4598) Otherwise your new repository might be slightly different from the original regarding no-op changes (see the issue [1] for more explanation). Concerning issue #4554 I'm not sure. From the issue description it sounds like quite a rare edge case that you would only very rarely see in a real world repository (and since it talks about dump files being broken, I'm assuming you would detect it when loading the dump). But maybe stefan2 or someone else knows more about the circumstances for this issue, whether it's likely to occur in the wild, and what the visible consequences would be? -- Johan [1] https://issues.apache.org/jira/plugins/servlet/mobile#issue/SVN-4598
