Hello,
as some of you might have noticed s7 is badly corrupted.
Before I go into the details I can say we will most likely have to resetup s7
due to a innodb failure and I need to find a workaround until we have the data
in place which can take days or even weeks.
Now the details - probably some of you with database knowledge might have an
idea or say something to my idea of a workaround.
The replication failed several times in the past days and I did not know why.
I simply skipped the slave query when it failed and then replication ran again.
Today the database process restarted without a slave query failing repeatedly.
I had a close look and came to the idea that a broken transaction in the
transaction log made it break.
So I stopped the transaction from being played into the mysql db when the
database restarts by setting innodb_force_recovery = 3.
Ok, fine. MySQL then starts. Cool. But the slave process wont run in this mode
so we dont have the new data. Hm.
So I tried to throw away the broken transaction.
I moved the iblog-files and started mysql again.
MySQL failed to come up then telling me:
121116 11:40:28 InnoDB: Error: page 7 log sequence number 270 492619208
InnoDB: is in the future! Current system log sequence number 268 2967383564.
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-innodb-recovery.html
Ok. MySQL does not come up then and repeatedly restarts. No luck. Copied the
log files back. Fine. Works again.
Now I tried several thing to check which table might be corrupted.
Innodbchecksum reported everything fine.
Mysqlcheck crashed the mysql daemon when accessing centralauth.localnames.
Oh? Why? Checking the table again crashes mysql. Hm.
Tried a repair table - "storage engine does not support this"...hm.
The log says
InnoDB: Page lsn 268 3672100478, low 4 bytes of lsn at page end 3672100478
InnoDB: Page number (if stored to page already) 192520,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 428
InnoDB: Page may be an index page where index id is 0 1174
InnoDB: (index "PRIMARY" of table "centralauth"."localnames")
InnoDB: Error in page 192520 of index "PRIMARY" of table
"centralauth"."localnames"
121116 13:02:46 - mysqld got signal 11 ;
I tried to remove the index to rebuild it but this does not work due to
innodb_force_recovery = 3.
Mysqldump fails - crashes the mysql daemon too.
So I dont have any more idea how to fix this error.
Now I thought if we have to resetup I could drop the table completely and start
mysql normal mode so replication works again.
This would only mean s7 would lack this table until it is resetup.
What do you think about this?
Any more ideas?
Cheers
Marlen/nosy
_______________________________________________
Toolserver-l mailing list ([email protected])
https://lists.wikimedia.org/mailman/listinfo/toolserver-l
Posting guidelines for this list:
https://wiki.toolserver.org/view/Mailing_list_etiquette
