Did not get this reply, as I wasn't subscribed to the 'dev' mailing list
(subscribed now). Had a colleague forward this to me.
Philip Martin wrote:
> I see hot-backup.py is currently using db_archive and db_recover
> directly, I think using svnadmin would be better. The script also has
> /usr/local/BerkeleyDB.4.0/bin hardcoded, did you modify it to use
> /usr/bin?
Yes, the script was modified to point to the installed binaries.
>
> Looking at hot-backup.py itself I think there is a race choosing the
> name of the backup dir. The script gets a listing of the backup
> directory, then chooses a subdir name based on that listing and then
> copies into that subdir. If two scripts run simultaneously (say the
> one you start manually and the one started by the commit) they could
> get the same directory listing, choose the same name, and then backup
> into the same subdir. That would probably cause the hang you see.
I think there is some confusion here. Two scripts were **NOT** run
simultaneously.
The sequence of events were:
1. Committed several files.
2. Started the hot-backup script while step 1 was in progress.
3. Commits are completed, but hot-backup has stalled mid-way through the
execution.
4. Waited for about half-hour, then killed the hot-backup script.
5. Ran db_recover manually, which fails.
In subsequent tests, I interchanged the order of steps 1 & 2 and had the same
problem.
Regards,
Mal
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Oct 24 01:49:18 2003