Missing revision file in server directory
From: Kate Ebneter <kate_at_ning.com>
Date: Mon, 03 Nov 2008 11:47:47 -0700
Hi,
I'm running a 1.5.3/FSFS subversion server (on Solaris/ZFS), and we recently
My repository is obviously damaged. I cannot dump revisions past the missing
Does anyone know how to specify a minimal revision (and revprops) file that
---- Some details which may or may not be useful to someone: The revision in question was checked in successfully. There was a backup (using hot-backup.py) running at the time of commit which completed successfully but which, obviously, did not include the affected revision. The committed revision was present on the disk at that point as our FishEye+Crucible instance slurped it correctly. The next backup was scheduled to run four hours later. The developer made some further changes to the files involved in this commit and those changes were also successfully committed (and they are still there). About two hours after the commit, the FishEye logs show an error when FishEye tried to access that revision. When the next scheduled backup ran, the backup failed because the revision had disappeared. There is nothing in any logs to indicate what happened; no developer checking in ever received an error of any kind. In short, the revision was there, was there for a couple of hours, and then ... disappeared. I have no idea what caused this. Thanks, Kate Ebneter Build Engineer Ning, Inc. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org For additional commands, e-mail: users-help_at_subversion.tigris.orgReceived on 2008-11-03 20:47:15 CET |
This is an archived mail posted to the Subversion Users mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.