Have a read of this, he seems to have recovered from the same problem:
http://raphaelhahn.com/2009/08/innodb-caused-mysql-to-crash/after recovery
There are some links in the error output you pasted, have you followed and
read those?
If all else fails you could have a read of this InnoDB data recovery talk I
attended recently, there is a suite of tool you can use (link at the end):
http://www.percona.com/files/presentations/percona-live/london-2011/PLUK2011-data-recovery-for-mysql.pdf
If you're really, really stuck then Percona has per-hour billing for
consultancy (their consultants presented the slide above) and work
internationally over the phone/online. I have no affiliation with them.
Priority for you after recovery would be to get backups in place, even
quick and dirty cron daily mysqldump.
Good luck.
On 16 November 2011 08:34, umapathi b <umapathi.b@stripped> wrote:
> Hi,
>
> I am not able to even recover with the option ..innodb_force_recovery=4.
> I don't even have the backup of the data ..
>
> How can I recover ..the data ..? atleast the old data ...
>
> This is my error output ..
>
>
> ####################################################################################
>
> 111116 12:49:02 mysqld started
> nohup: ignoring input
> 111116 12:49:02 InnoDB: Database was not shut down normally!
> InnoDB: Starting crash recovery.
> InnoDB: Reading tablespace information from the .ibd files...
> InnoDB: Restoring possible half-written data pages from the doublewrite
> InnoDB: buffer...
> 111116 12:49:02 InnoDB: Starting log scan based on checkpoint at
> InnoDB: log sequence number 0 492420330.
> InnoDB: Error: tried to read 65536 bytes at offset 0 5016576.
> InnoDB: Was only able to read 1024.
> InnoDB: Fatal error: cannot read from file. OS error number 17.
> 111116 12:49:26InnoDB: Assertion failure in thread 3086489296 in file
> os0file.c line 2197
> 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.
> 111116 12:49:26 - 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=131072
> 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 =
> 217599 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=0xbf936a28, backtrace may not be correct.
> Stack range sanity check OK, backtrace follows:
> 0x81872a3
> 0x842e4e9
> 0x83f95df
> 0x83d9cc0
> 0x83e36ae
> 0x83e3bb7
> 0x8341a4b
> 0x8250100
> 0x823f8c6
> 0x81862c6
> 0x8189b1a
> 0xc67f70
> 0x80fa4a1
> 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 resolve 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.
> 111116 12:49:26 mysqld ended
>
>
>
> #############################################################################################
>
> Thanks,
> Umapathi.
>
--
GPG Key fingerprint = B323 477E F6AB 4181 9C65 F637 BC5F 7FCC 9CC9 CC7F
“Live as if you were to die tomorrow. Learn as if you were to live
forever.” - Indian political and spiritual leader Mahatma Gandhi (1869-1948)
