Comment 8 for bug 352742

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

With the newer than revision 39, the message
"
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!
"
is cause by "partial re-prepare". (situation of some files are already prepared)
I think the message may not appear at normal situation now.