corruption in the InnoDB tablespace ??

[Lord Kazuky]

Buenos Dias. Esta mañana despues de haber reiniciado mi servidor (Linux Suse 10), me di cuenta y no iniciaba el servicio del Mysql.

Al ejecutar el comando manualmente para iniciar el servicio me sale algo como esto:

Código:

080812 09:27:09  mysqld started
InnoDB: Error: tried to read 1048576 bytes at offset 0 1048576.
InnoDB: Was only able to read 1024000.
InnoDB: Fatal error: cannot read from file. OS error number 17.
080812  9:27:36InnoDB: Assertion failure in thread 4157826736 in file os0file.c line 2176
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: about forcing recovery.
mysqld got signal 11;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=0
read_buffer_size=67104768
max_used_connections=0
max_connections=100
threads_connected=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 523887 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=(nil)
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
Cannot determine thread, fp=0xffffa498, backtrace may not be correct.
Bogus stack limit or frame pointer, fp=0xffffa498, stack_bottom=(nil), thread_stack=196608, aborting backtrace.
The manual page at http://www.mysql.com/doc/en/Crashing.html contains
information that should help you find out what is causing the crash.
080812 09:27:36  mysqld ended

Bueno segun lo que entiendo, algo muy malo paso en las tablas. y segun la pagina que indican ahi en el manual, la seccion de forzar una recuperacion. (http://dev.mysql.com/doc/refman/5.0/...-recovery.html)

Estableci el parametro 'innodb_force_recovery' y solo me dejo iniciar mysql con el valor 6

Código:

080812 09:38:56  mysqld started
InnoDB: The user has set SRV_FORCE_NO_LOG_REDO on
InnoDB: Skipping log redo
080812  9:38:56  InnoDB: Started; log sequence number 0 0
InnoDB: !!! innodb_force_recovery is set to 6 !!!
080812  9:38:57 [Note] /usr/sbin/mysqld-max: ready for connections.
Version: '5.0.37-max-log'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  MySQL Community Edition - Experimental

Aunque en este modo no me deja hacer practicamente nada.

La pregunta es si alguien sabe como puedo por lo menos arreglar la BD o que proceso debo seguir, igual dispongo de Backups (Afortunadamente).

Gracias ;)

[Lord Kazuky]

Bueno... lastimosamente todo lo que intente, no funciono ..

Probe la utilidad "myisamchk " la cual funciono perfectamente para las tablas MyISAM pero desafortunadamente la mayoria de mis tablas y bases de datos son InnoDB (por aquello de las transacciones) entonces esto no sirvio...

Lo unico que me dejo hacer el motor fue utilizar los comandos DROP, entonces finalmente lo unico que se pudo hacer fue Borrar las Bases de datos InnoDB. Luego quitar el "innodb_force_recovery" del my.cnf.
Reiniciar el Motor.
Y cuando ya me dejaba entrar. volver a restaurar todo del Backup.

Afortunadamente no era el servidor de produccion sino otro con datos de prueba.