If svnrdump loses the network connection, the last commit that it dumps can be incomplete.
If one directly pipes the output of svnrdump into svnadmin load, this will result in a target
repository that doesn't have the complete record of the commit from the source repository.
(Recovery of correct data, at this point, means dumping the local repository, except for the
last commit, then reloading it, then resuming the svnrdump (with --incremental) from the
partial commit).
There are work-arounds to this problem, but they're all painful.
Likely the dump file needs to be enhanced to indicate "end-of-commit" or some such thing,
and svnadmin (and svnrdump) need to be enhanced so that they abort the last commit from a
dump if the "end-of-commit" marker isn't found before the input stream is closed.
https://mail-archives.apache.org/mod_mbox/subversion-users/201509.mbox/%3CCANu9%3DNeNevwU9fLEmen3EZBvLk9n6NgiCi6YqJBPmck0k7izsQ%40mail.gmail.com%3E
Critical