Description:
Before I start, this is for a client and we have no backups.
MySQL will no longer start, here is what I see(with set-variable=innodb_force_recovery=6):
081105 19:42:48 mysqld started
InnoDB: The user has set SRV_FORCE_NO_LOG_REDO on
InnoDB: Skipping log redo
InnoDB: Error: trying to access page number 4294058879 in space 0,
InnoDB: space name ./ibdata1,
InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset 0, len 16384, i/o type 10.
InnoDB: If you get this error at mysqld startup, please check that
InnoDB: your my.cnf matches the ibdata files that you have in the
InnoDB: MySQL server.
081105 19:42:49InnoDB: Assertion failure in thread 3086883072 in file fil0fil.c line 3959
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.
081105 19:42:49 - 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=2093056
max_used_connections=0
max_connections=400
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 1227196 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=0xbf8425c8, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x8187393
0x83f96bc
0x83d76a5
0x83d7cdd
0x83cba1f
0x83bc39e
0x83bc516
0x83bd56a
0x8341ace
0x8250170
0x823f936
0x81863b6
0x8189bd5
0x45a0fdec
0x80fa4e1
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/en/using-stack-trace.html and follow instructions on how to resol
ve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do
resolve it
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.
081105 19:42:49 mysqld ended
And from a resolve stack dump:
# resolve_stack_dump -s mysqld.sym -n mysql.stack | c++filt
0x8187393 handle_segfault + 755
0x83f96bc fil_io + 716
0x83d76a5 buf_LRU_invalidate_tablespace + 1333
0x83d7cdd buf_read_page + 637
0x83cba1f buf_page_get_gen + 303
0x83bc39e trx_rseg_get_on_id + 702
0x83bc516 trx_rseg_list_and_array_init + 182
0x83bd56a trx_sys_init_at_db_start + 378
0x8341ace innobase_start_or_create_for_mysql + 5870
0x8250170 innobase_init() + 880
0x823f936 ha_init() + 582
0x81863b6 unireg_abort + 582
0x8189bd5 main + 1109
0x45a0fdec _end + 1026696560
0x80fa4e1 _start + 33
Looking online, these types of errors seem to be a result of hardware problems. And it doesn't look like I am any different:
Nov 2 09:36:30 server smartd[4809]: Device: /dev/hda, 2 Offline uncorrectable sectors
Nov 2 10:06:30 server smartd[4809]: Device: /dev/hda, 2 Currently unreadable (pending) sectors
So my question, is there ANY way I can recover any of the databases?
How to repeat:
I obviously can repeat this by trying to start mysql.
