Re: Heavy data lost in InnoDB after a bad-shutdown
Posted by:
Tobia Bea
Date: December 29, 2013 04:59AM
I can not find innodb_fast_shutdown in my.ini file (mind I have the default "server" type default configuration), however it can be set by default. I don't have innodb_file_per_table option, so I think it is set by default to 0.
I can confirm that in all evening dumps made with mysqldump I can find ALL lost records from 14 to 21 december, in the 22nd december dump I found the record gap ... this is why I can not belive a transaction error, mysqlsump could read only committed records.
The log deletion was done just to test how old was the last checkpoint.
Don't you think it could be a checkpoint problem of inno logs? Mysqldump read from unflushed logs for 6 days, the power failure broke the log, innodb tried to restore logs but it fails, than db data back to last, 6 day old, checkpoint.
Edited 1 time(s). Last edit at 12/29/2013 05:02AM by Tobia Bea.
Subject
Views
Written By
Posted
4721
December 23, 2013 08:20AM
1748
December 24, 2013 11:01AM
1502
December 24, 2013 02:48PM
1524
December 25, 2013 04:57PM
1406
December 27, 2013 03:06AM
1422
December 27, 2013 03:53AM
1271
December 27, 2013 04:53AM
1446
December 28, 2013 01:12PM
Re: Heavy data lost in InnoDB after a bad-shutdown
1218
December 29, 2013 04:59AM
1181
December 30, 2013 01:55AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.