XtraDB crashes on shutdown in "crash resistent mode"

Bug #569275 reported by Vadim Tkachenko
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Server moved to https://jira.percona.com/projects/PS
Fix Released
High
Unassigned

Bug Description

I corrupted table "district" on disk and started XtraDB
with

innodb_pass_corrupt_table=1

Now error message works fine:

mysql> show create table district\G
ERROR 1194 (HY000): Table 'district' is marked as crashed and should be repaired

===

But when I do mysqladmin shutdown, XtraDB crashes:

InnoDB: space 18 will be treated as corrupt.
100423 19:39:20 [Note] libexec/mysqld: Normal shutdown

100423 19:40:05 InnoDB: Starting shutdown...
Page 18 3 still fixed or dirty
100423 19:40:09 InnoDB: Assertion failure in thread 140235682539856 in file buf/buf0buf.c line 4340
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.
===

there is gdb trace:

(gdb) bt
#0 0x00007f8b291dafb5 in raise () from /lib/libc.so.6
#1 0x00007f8b291dcbc3 in abort () from /lib/libc.so.6
#2 0x00000000008168d6 in buf_all_freed () at buf/buf0buf.c:4340
#3 0x000000000078e2fa in logs_empty_and_mark_files_at_shutdown () at log/log0log.c:3262
#4 0x00000000007d74a8 in innobase_shutdown_for_mysql () at srv/srv0start.c:1945
#5 0x000000000076a973 in innobase_end ()
#6 0x00000000006c1e9b in ha_finalize_handlerton ()
#7 0x0000000000749326 in plugin_deinitialize ()
#8 0x000000000074a64e in reap_plugins ()
#9 0x000000000074aee5 in plugin_shutdown ()
#10 0x00000000005c9327 in clean_up ()
#11 0x00000000005cfa9e in kill_server_thread ()
#12 0x00007f8b29dfc3ba in start_thread () from /lib/libpthread.so.0
#13 0x00007f8b2928dfcd in clone () from /lib/libc.so.6
#14 0x0000000000000000 in ?? ()

Related branches

Changed in percona-server:
status: New → Triaged
importance: Undecided → High
assignee: nobody → Yasufumi Kinoshita (yasufumi-kinoshita)
milestone: none → 5.1.46-rel10.1
Changed in percona-server:
milestone: 5.1.46-rel11 → 11.0
Changed in percona-server:
milestone: 11.0-old → 11.0
Changed in percona-server:
milestone: 11.0 → 5.1-11.1
Changed in percona-server:
milestone: 5.1-11.1 → 5.1-12.0
Changed in percona-server:
milestone: 5.1.47-12.0 → 5.1-12.0
Changed in percona-server:
status: Triaged → Fix Committed
Changed in percona-server:
status: Fix Committed → Fix Released
Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-405

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.