Comment 5 for bug 776914

I see multiple errors in the attached log that look like the following:
"
110503 19:37:44 InnoDB: Error: page 4 log sequence number 8299215792744
InnoDB: is in the future! Current system log sequence number 8298149359628.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
"

Which indicates there's an inconsistency between the log files and the data files. The actual assertion failure resulting in a crash may have the similar nature.

Is this problem still repeatable? If so, how the backup is restored? Is there any chance that the data directory on the server contains both new files (i.e. restored from the backup) and old ones (i.e. left from the previously running server instance)?