Percona XtraBackup moved to https://jira.percona.com/projects/PXB

  1. Bug #352742
  2. Comment #6

Comment 6 for bug 352742

Revision history for this message
Yasufumi Kinoshita (yasufumi-kinoshita) wrote :

http://bazaar.launchpad.net/~percona-dev/percona-xtrabackup/trunk/revision/35

I have fixed except for,
"
InnoDB: Doing recovery: scanned up to log sequence number 1319 813701532 (99 %)
090405 4:29:47 InnoDB: ERROR: We were only able to scan the log up to 1319 813701532
InnoDB: but a database page a had an lsn 1319 814039859. It is possible that the
InnoDB: database is now corrupt!
"

It may need to investigate more.

The progress of log is come from process of insert-buffer.
And the precessed page's LSN becomes newer.
And the page may be "re-read" during the recovery...
(I don't know why "re-read" the same page yet....)