This problem is reproducible. Tried this on two occasions since I reported
the original problem and hit the same error.
Reversed the steps in these tests. i.e. started the backup first and then the
commits.
This seems like a serious problem.
Can the hot-backup.py script be executed while other svn operations are in
progress?
Thanks,
Mal
On Friday 17 October 2003 15:06, Malcolm Fernandes wrote:
> Was testing the hot-backup.py script on a test repository and it hung on
> one occassion.
>
> We are using:
> svn, version 0.30.0 on Suse Linux
>
> The hot-backup script ran successfully on several earlier attempts.
>
> Scenario:
> Was committing several hundred files and was simultaneously checking out a
> project from another xterm (http access).
> While the two subversion operations were running, I fired up the hot-backup
> script. It ran for a while and then hung after re-copying the logfiles.
>
> Re-copying logfile 'log.0000000228'...
> Re-copying logfile 'log.0000000229'...
> Backup completed.
>
>
> An strace of the process revealed:
> /usr/bin/strace -p27646
> write(2, "Log sequence error: page LSN 227"..., 64) = ? ERESTARTSYS (To be
> restarted)
>
> Interrupted the script after about half-hour and got this traceback
> message: Traceback (most recent call last):
> File "./hot-backup.py", line 160, in ?
> stdout_lines = outfile.readlines()
> KeyboardInterrupt
>
> Attempted to run db_recover manually and got this error:
> # /usr/bin/db_recover -h
> /home2/mfernandes/subversion/BACKUPS/test_2-73-2/db db_recover: Log
> sequence error: page LSN 217:649059; previous LSN 227 947360 db_recover:
> Log sequence error: page LSN 227:741713; previous LSN 227 986004
> db_recover: Log sequence error: page LSN 227:741713; previous LSN 227
> 992643 ...
> ... --snip--
> db_recover: Log sequence error: page LSN 227:759209; previous LSN 229
> 354875 db_recover: Log sequence error: page LSN 227:741713; previous LSN
> 229 480106 db_recover: strings: close: 427 blocks left pinned
> db_recover: nodes: close: 21 blocks left pinned
> db_recover: DB_ENV->open: DB_INCOMPLETE: Cache flush was unable to complete
>
> Tried this several times and got the same error.
>
> A subsequent run of hot-backup worked fine.
>
> Could the bulk commit be the cause for this failure, whereby transactions
> were still getting logged, even while the logfile was getting re-copied to
> the backup area?
>
> Thanks,
>
> Mal
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Oct 22 19:11:19 2003