Possible svnsync data loss bug?

I just ran into a rather frightening problem. We do replications via
svnsync for backup purposes. I just found two of the replicated
repositories which had these entries for *every* version:

   r20927 | (no author) | (no date) | 1 line
   Changed paths:

And svnlook tree shows there is nothing in the repositories.

We have never seen any errors while running svnsync, however, these
replicas have been around so long that most of the logs are long since
gone, though I did find a recent log entry for the very version shown
above (note: the first and last lines are output by my scripts):

   Running command: svnsync sync file:///svn/repos/blah-blah
--non-interactive
   Committed revision 20927.
   Copied properties for revision 20927.
   No errors, not sending email

It appears that svnsync is failing somehow but never indicating that in
the output or exit status and, instead, creating empty revisions.

These two repositories are the only two we are replicating from this
host, and I have yet to find any other repositories in the same state
(though I am still looking). So, I guess it could be a bug on the
remote end, which svnsync is unable to detect. My machine is running
SVN 1.6.16 (on a Linux machine running our variant of RHEL 5.8). I
can't tell you much about the remote end as it is currently down ;(

I searched through the SVN bugdb but didn't see anything reminiscent of
this. Has anyone seen this behavior?

++thanks,
trent...
Received on 2012-06-22 19:53:26 CEST