Hello All,
Under Centos 6 v. Mysql 5.1.61, I have detected the following strange behavior and have no idea how to solve it.
The server had large log, and it cause overloading the HardDrive up to 99%. At this moment the mysql, without previous advice, neither any alert just droped the innodb engine and it's not reading any DB build under the innob engine.
When i do:
<Quote>
mysql> SHOW ENGINES;
+------------+---------+-----------------------------------------------------------+--------------+------+------------+
| Engine | Support | Comment | Transactions | XA | Savepoints |
+------------+---------+-----------------------------------------------------------+--------------+------+------------+
| MRG_MYISAM | YES | Collection of identical MyISAM tables | NO | NO | NO |
| CSV | YES | CSV storage engine | NO | NO | NO |
| MyISAM | DEFAULT | Default engine as of MySQL 3.23 with great performance | NO | NO | NO |
| MEMORY | YES | Hash based, stored in memory, useful for temporary tables | NO | NO | NO |
+------------+---------+-----------------------------------------------------------+--------------+------+------------+
mysql> SHOW VARIABLES LIKE 'have_innodb';
+---------------+-------+
| Variable_name | Value |
+---------------+-------+
| have_innodb | NO |
+---------------+-------+
</Quote>
Innob engine is not recognised any more, and there's no way to dump existing DB to recover the server, when i try to dump existing DB, i get:
<quote>
mysqldump: Error: 'Can't create/write to file '/tmp/#sql_420c_2.MYI' (Errcode: 13)' when trying to dump tablespaces
mysqldump: Got error: 1286: Unknown table engine 'InnoDB' when using LOCK TABLES
</quote>
I'm trying to re-verify the my.cnf file, but all see to be ok, as the innob engine was already running in the server, no any configuration was changed, unless the HD overload, which now was corrected, we have deleted the unnecessary log, try to run yum update, reboot the server several times, no way, innob engine is not loading.
I need to dump the DB at least to recover the server, or now idea, what can I do, please, advice!!
Regards,
Under Centos 6 v. Mysql 5.1.61, I have detected the following strange behavior and have no idea how to solve it.
The server had large log, and it cause overloading the HardDrive up to 99%. At this moment the mysql, without previous advice, neither any alert just droped the innodb engine and it's not reading any DB build under the innob engine.
When i do:
<Quote>
mysql> SHOW ENGINES;
+------------+---------+-----------------------------------------------------------+--------------+------+------------+
| Engine | Support | Comment | Transactions | XA | Savepoints |
+------------+---------+-----------------------------------------------------------+--------------+------+------------+
| MRG_MYISAM | YES | Collection of identical MyISAM tables | NO | NO | NO |
| CSV | YES | CSV storage engine | NO | NO | NO |
| MyISAM | DEFAULT | Default engine as of MySQL 3.23 with great performance | NO | NO | NO |
| MEMORY | YES | Hash based, stored in memory, useful for temporary tables | NO | NO | NO |
+------------+---------+-----------------------------------------------------------+--------------+------+------------+
mysql> SHOW VARIABLES LIKE 'have_innodb';
+---------------+-------+
| Variable_name | Value |
+---------------+-------+
| have_innodb | NO |
+---------------+-------+
</Quote>
Innob engine is not recognised any more, and there's no way to dump existing DB to recover the server, when i try to dump existing DB, i get:
<quote>
mysqldump: Error: 'Can't create/write to file '/tmp/#sql_420c_2.MYI' (Errcode: 13)' when trying to dump tablespaces
mysqldump: Got error: 1286: Unknown table engine 'InnoDB' when using LOCK TABLES
</quote>
I'm trying to re-verify the my.cnf file, but all see to be ok, as the innob engine was already running in the server, no any configuration was changed, unless the HD overload, which now was corrected, we have deleted the unnecessary log, try to run yum update, reboot the server several times, no way, innob engine is not loading.
I need to dump the DB at least to recover the server, or now idea, what can I do, please, advice!!
Regards,