Comment 20 for bug 1193350

Revision history for this message
Roel Van de Paar (roel11) wrote :

I re-ran the testcase from #14 and got a hang + crash

[...]
2015-10-24 02:09:20 31504 [Warning] InnoDB: Setting thread 32255 nice to -11 failed, current nice 19, errno 13
2015-10-24 02:09:23 31504 [Warning] InnoDB: Setting thread 32256 nice to -11 failed, current nice 19, errno 13
2015-10-24 02:09:23 31504 [Warning] InnoDB: Setting thread 32255 nice to -11 failed, current nice 19, errno 13
InnoDB: sync levels should be > 800 but a level is 175
Mutex '&log_bmp_sys->mutex'
InnoDB: Locked mutex: addr 0x7f0e90606460 thread 139701316347648 file /mnt/workspace/percona-server-5.6-binaries-debug-yassl-new/label_exp/centos6-64/percona-server-5.6.25-73.2/storage/innobase/log/log0online.cc line 1801
InnoDB: sync_thread_levels_g(array, 800) does not hold!
2015-10-24 02:09:23 7f0ebf55e700 InnoDB: Assertion failure in thread 139701316347648 in file sync0sync.cc line 1280
[...]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7f0e6dc8f010): SHOW GLOBAL STATUS LIKE 'MAX_STATEMENT_TIME_SET_FAILED'
Connection ID (thread ID): 13
Status: NOT_KILLED

Core looks corrupted. Plenty of disk space.

Reading symbols from /sda/Percona-Server-5.6.25-rel73.2-f9f2b02.Linux.x86_64-debug/bin/mysqld...done.
BFD: Warning: /sda/939551/rundir1_9/./master-data/core.31504.1000.1000.6.1445641763.mysqld is truncated: expected core file size >= 3202265088, found: 1469190144.
[New LWP 22505]
[...]
[New LWP 22619]
Cannot access memory at address 0x7f0ebf6d61e8
Cannot access memory at address 0x7f0ebf6d61e0
(gdb) bt
+bt
#0 0x00007f0ebf06f771 in ?? ()
Cannot access memory at address 0x7f0ebf559ff8

[roel@localhost rundir1_9]$ df -h | grep sda
/dev/sda 881G 205G 632G 25% /sda