GET 24/7 LIVE HELP NOW

Announcement

Announcement Module
Collapse
No announcement yet.

mysql crashed

Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • mysql crashed

    MySQL-client-community-5.1.34-0.rhel5
    Storage Engine : innodb
    Database Size : 300 GB

    mysql crashed with following error.

    100607 10:48:05 InnoDB: Page checksum 2409679152, prior-to-4.0.14-form checksum 2116520512
    InnoDB: stored checksum 3419910460, prior-to-4.0.14-form stored checksum 555
    InnoDB: Page lsn 555 3228275704, low 4 bytes of lsn at page end 3228275704
    InnoDB: Page number (if stored to page already) 93232,
    InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 549
    InnoDB: Page may be an index page where index id is 0 1654
    100607 10:48:05 InnoDB: Assertion failure in thread 1106942272 in file page/page0page.c line 133
    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.1/en/forcing-recovery.html
    InnoDB: about forcing recovery.
    100607 10:48:05 - mysqld got signal 6 ;
    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=8388608
    read_buffer_size=4194304
    max_used_connections=0
    max_threads=500
    threads_connected=0
    It is possible that mysqld could use up to
    key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 10253281 K
    bytes of memory
    Hope that's ok; if not, decrease some variables in the equation.

    thd: 0x0
    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...
    stack_bottom = (nil) thread_stack 0x30000
    /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x8453de]
    /usr/sbin/mysqld(handle_segfault+0x322)[0x5bca02]
    /lib64/libpthread.so.0[0x339100e7c0]
    /lib64/libc.so.6(gsignal+0x35)[0x3390830265]
    /lib64/libc.so.6(abort+0x110)[0x3390831d10]
    /usr/sbin/mysqld(page_dir_find_owner_slot+0x1d9)[0x796a59]
    /usr/sbin/mysqld(page_cur_insert_rec_low+0x5b4)[0x794bc4]
    /usr/sbin/mysqld(page_cur_parse_insert_rec+0x2ed)[0x79541d]
    /usr/sbin/mysqld[0x783c18]
    /usr/sbin/mysqld(recv_recover_page+0x36b)[0x78588b]
    /usr/sbin/mysqld(buf_page_io_complete+0x548)[0x743b98]
    /usr/sbin/mysqld(fil_aio_wait+0x139)[0x75e389]
    /usr/sbin/mysqld[0x7c038c]
    /lib64/libpthread.so.0[0x33910064a7]
    /lib64/libc.so.6(clone+0x6d)[0x33908d3c2d]
    The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
    information that should help you find out what is causing the crash.
    100607 10:48:06 mysqld_safe mysqld from pid file /var/lib/mysql/onetdb01.pid ended


    i tried starting mysql with
    innodb_force_recovery = 4 then 3,2,1
    everytime mysql crashed with same error

    Please suggest.

  • #2
    Looks like you have some data corruption.

    Here is the #1 mistake people do when they get InnoDB corruption: they try to repair the table, filesystem, etc and they don't check their hardware. InnoDB DOES NOT RANDOMLY CORRUPT DATA -- most of the time it is BAD HARDWARE. You MUST check your hardware. I have seen people spend huge amounts of money recovering data, only to get more corruption again.

    Comment

    Working...
    X