Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

So I had a very large corrupt innodb table. mysqld would crash whenever I did a check table on it. I did a innodb-force-recovery=1 and did a dump of the table. No errors showed up.

I dropped the table and attempted to restore.. 20% into it mysqld crashes;

InnoDB: Wrong owned count 15, 2, rec 4010
120203 22:01:07  InnoDB: Page dump in ascii and hex (16384 bytes):
len 16384; hex       737f2bb.....

... ..

120203 22:01:07  InnoDB: Page checksum 1937714109, prior-to-4.0.14-form checksum 2715118693
InnoDB: stored checksum 1937714109, prior-to-4.0.14-form stored checksum 2715118693
InnoDB: Page lsn 229 2169122954, low 4 bytes of lsn at page end 2169122954
InnoDB: Page number (if stored to page already) 283815,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 994
InnoDB: Page may be an index page where index id is 0 4660
InnoDB: (index "fact_fiscalYearLabel" of table "mycompany_staging"."Fact")
120203 22:01:07  InnoDB: Apparent corruption of an index page n:o 283815 in space 994

I thought dumping a table successfully then restoring from it should clear the corruption? why is it still corrupted and I cannot restore it?

tia!

share|improve this question
add comment

1 Answer

Try to do a memory check first. If that passes, upgrade mysql.. there are several innodb bugs that can cause that.

share|improve this answer
    
this is on a cloud host cannot do a memory check. also it is the latest version of mysql available in the Ubuntu 10.04 release. –  John Ingles Feb 4 '12 at 4:20
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.