Yakari,
- Original Message -
From: "Yukari Iwatani" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.mysql
Sent: Friday, March 14, 2003 3:36 PM
Subject: Hard, unrecoverable InnoDB crash with MySQL 4.0.11
> Hi:
>
> I'm running MySQL 4.0.11 (MySQL.com binary RPMs) on Red Hat Linux 7.3, all
> errata applied (kernel 2.4.18-26.7.xsmp).
>
> This morning, our server died hard, with the following error:
>
> 030314 2:44:13 InnoDB: Assertion failure in thread 7938074 in file
> btr0btr.c line 298
0x8073e0a handle_segfault + 450
0x8285738 pthread_sighandler + 184
0x8157b39 btr_page_alloc_for_ibuf + 241
0x815edda btr_page_split_and_insert + 854
0x816e9e4 btr_cur_pessimistic_insert + 1824
0x8127e40 ibuf_insert_low + 4332
0x81288ca ibuf_insert + 726
0x816b3f1 btr_cur_search_to_nth_level + 2025
0x812f423 row_ins_index_entry_low + 179
0x812fd6a row_ins_index_entry_step + 302
0x8130050 row_ins + 696
0x813018c row_ins_step + 252
0x8131787 row_insert_for_mysql + 507
0x80cfd32 write_row__11ha_innobasePc + 1122
0x80a7bfc write_record__FP8st_tableP12st_copy_info + 528
0x80a754d
mysql_insert__FP3THDP13st_table_listRt4List1Z4ItemRt4List1Zt4List1Z4Item15en
um_duplicates + 1141
0x807fed9 mysql_execute_command__Fv + 6837
0x8082178 mysql_parse__FP3THDPcUi + 560
0x807d90d dispatch_command__F19enum_server_commandP3THDPcUi + 1545
0x80836ae do_command__FP3THD + 154
0x807cabf handle_one_connection + 631
0x8282eec pthread_start_thread + 220
0x82b65fa thread_start + 4
the algorithm should make sure there always are pages in the free list of
the insert buffer tree. In this case the list was empty (page number
0x) , whence the assertion.
> When the server then tried to restart itself, it died with:
>
> InnoDB: Error: trying to access page number 4294396415 in space 0
Hmm... that is 2^32 - 570881. Looks like corruption.
> InnoDB: which is outside the tablespace bounds.
> InnoDB: Byte offset 0, len 16384, i/o type 10
>
> 030314 2:48:11 InnoDB: Assertion failure in thread 12292 in file
> fil0fil.c
> line 1176
>
> The server would not come back up. We had to nuke the InnoDB tablespace
> and logs and restore from backup.
You could have tried in my.cnf
set-variable=innodb_force_recovery=4
to bring it up.
If the problem recurs, you could try upgrading to Linux-2.4.20. If the
corruption is a Linux kernel problem that might help.
> I've placed the resolved stack trace and full error logs online at:
>
> http://www.oxyopia.com/~yi/stack.resolved
> http://www.oxyopia.com/~yi/failure.log
>
> TIA,
> --
> Yukari Iwatani
> <[EMAIL PROTECTED]>
Heikki Tuuri
Innobase Oy
---
InnoDB - transactions, hot backup, and foreign key support for MySQL
See http://www.innodb.com, download MySQL-4.0 from http://www.mysql.com
sql query
-
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
