Re: Problem of data corruption
Hi,
I've experienced exactly same problems of corruption, with exactly same errors.
I'm running Mysql4.0.21, with a lighter config of yours. The error occurs on a innodb table about 70000 rows and 16Mb of data, that table has a PK combining 3 fields of different type (varchar(10)+char(3)+smallint(5)) , and with an index on a single varchar field.
The innodb crash + rollback occured on any DML command, even on an ALTER TABLE t type=InnoDB which normally rebuild indexes.
A rename table works fine, this to enable me to re-import table from nightly backup.
But that left me with a corrupted dead table in my innodb tablespace, impossible to drop.
The only way i get off this was to stop Mysql, add a line "innodb_force_recovery=4" in my.cnf , start , check the error server file, stop, remove that line, and restart the server to drop the table.
When reading this thread and seeing data corruption come back again... that's decide me to post... :-/
Any comments on this ??
My soft config is Mysql4.0.21-standard-log icc-glibc23, Official MySQL-standard library on a SuSE9.1, with one innodb tablespace sizing about 250Mb now, on 2.6.5-7.111 kernel. MySQL is running verrry fine until now, for three years now.
Thks
Benjamin