Hello, mysql was such a reliable and unbreakable database until innodb showed up. All the time I had problems with mysql it was related to innodb. Today again:
InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... 070206 09:29:19 mysqld ended Is there any use of innodb_file_per_table? As it doesn't remove the requirement of central innodb-transaction logs and data isn't stored in there, it was speedup the start where mysql seems to look for .ibd files. And mysql fails for same reason at the start, but doesn't tell much. When I'm setting innodb_force_recovery, then I get logs like 070206 9:31:42 InnoDB: Error: page 63 log sequence number 0 4317619 InnoDB: is in the future! Current system log sequence number 0 8204. InnoDB: Your database may be corrupt. 070206 9:31:42 InnoDB: Error: page 192 log sequence number 0 14323525 InnoDB: is in the future! Current system log sequence number 0 8204. InnoDB: Your database may be corrupt. 070206 9:31:42 InnoDB: Started; log sequence number 0 8204 /libexec/mysqld: ready for connections. But it doesn't actually fix the innodb-files. Once I run mysql with forced recovery, I can start it again normally. But mostly the server crashes some hours later because one big mysql process using 100% of the cpu shows up at some point and keeps running all the time. Is there any "repair innodb" command like there is a "repair table <...>" for MyIsam tables? Otherwise I think I have to recreated all. How can I check which tables are using innodb with sql? How can walk through the tables with "show databases" and "show tables". Thanks. Regards Marten -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
