InnoDB: Failing assertion: 0 in file os0file.cc line 662 | handle_fatal_signal (sig=6) in os_file_handle_error_cond_exit | File operation call: 'open' returned OS error 71. | InnoDB: Operating system error number 2 in a file operation.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS |
Fix Released
|
High
|
Sergei Glushchenko | ||
5.6 |
Fix Released
|
High
|
Sergei Glushchenko |
Bug Description
=======
2013-03-15 06:38:57 5363 [Note] /ssd/Percona-
Version: '5.6.10-
2013-03-15 06:39:19 7f7611c86700 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
2013-03-15 06:39:19 7f7611c86700 InnoDB: File name /ssd/tmp/
2013-03-15 06:39:19 7f7611c86700 InnoDB: File operation call: 'open' returned OS error 71.
2013-03-15 06:39:19 7f7611c86700 InnoDB: Cannot continue operation.
2013-03-15 06:39:19 7f7611c86700 InnoDB: Assertion failure in thread 140145081214720 in file os0file.cc line 662
InnoDB: Failing assertion: 0
InnoDB: We intentionally generate a memory trap.
=======
Thread 1 (LWP 5366):
+bt
#0 0x0000003da180c60c in pthread_kill () from /lib64/
#1 0x00000000006ab85f in handle_fatal_signal (sig=6) at /ssd/ps56-
#2 <signal handler called>
#3 0x0000003da1435935 in raise () from /lib64/libc.so.6
#4 0x0000003da14370e8 in abort () from /lib64/libc.so.6
#5 0x00000000009f625c in os_file_
#6 0x00000000009f7c0a in os_file_
#7 os_file_create_func (name=0x7f7611c
#8 0x00000000009de72e in pfs_os_
imized out>) at /ssd/ps56-
#9 log_group_archive (group=0x3b6e068) at /ssd/ps56-
#10 0x00000000009df809 in log_archive_groups () at /ssd/ps56-
#11 log_archive_
#12 log_io_
#13 log_io_complete (group=<optimized out>) at /ssd/ps56-
#14 0x0000000000b7610a in fil_aio_wait (segment=1) at /ssd/ps56-
#15 0x0000000000a9f5e8 in io_handler_thread (arg=<optimized out>) at /ssd/ps56-
#16 0x0000003da1807d14 in start_thread () from /lib64/
#17 0x0000003da14f168d in clone () from /lib64/libc.so.6
=======
[Roel@qaserver 198649]$ cat ./cmd9633
ps -ef | grep 'cmdrun_9633' | grep -v grep | awk '{print $2}' | xargs sudo kill -9
rm -Rf /ssd/198649/
mkdir /ssd/198649/
cd /ssd/randgen
bash -c "set -o pipefail; perl runall.pl --queries=100000000 --seed=10879 --duration=120 --querytimeout=60 --short_
=======
- Seen in many runs.
- Long title is for SE search purposes only
Related branches
- Alexey Kopytov (community): Approve
-
Diff: 2357 lines (+1394/-155)43 files modifiedPercona-Server/mysql-test/suite/innodb/include/percona_log_archiving_check.inc (+15/-0)
Percona-Server/mysql-test/suite/innodb/include/percona_log_archiving_cleanup.inc (+15/-0)
Percona-Server/mysql-test/suite/innodb/include/percona_log_archiving_count.inc (+9/-0)
Percona-Server/mysql-test/suite/innodb/include/percona_log_archiving_last_file.inc (+24/-0)
Percona-Server/mysql-test/suite/innodb/include/percona_log_archiving_setup.inc (+49/-0)
Percona-Server/mysql-test/suite/innodb/include/percona_log_archiving_stat.inc (+72/-0)
Percona-Server/mysql-test/suite/innodb/include/percona_log_archiving_workload.inc (+5/-0)
Percona-Server/mysql-test/suite/innodb/r/pecona_bug1155475.result (+23/-0)
Percona-Server/mysql-test/suite/innodb/r/percona_innodb_log_archive_func.result (+24/-0)
Percona-Server/mysql-test/suite/innodb/r/percona_log_arch_expire_sec.result (+27/-0)
Percona-Server/mysql-test/suite/innodb/r/percona_log_arch_func.result (+21/-0)
Percona-Server/mysql-test/suite/innodb/r/percona_purge_archived_logs_before.result (+37/-0)
Percona-Server/mysql-test/suite/innodb/r/percona_purge_archived_logs_to.result (+35/-0)
Percona-Server/mysql-test/suite/innodb/t/pecona_bug1155475.test (+30/-0)
Percona-Server/mysql-test/suite/innodb/t/percona_innodb_log_archive_func.test (+31/-0)
Percona-Server/mysql-test/suite/innodb/t/percona_log_arch_expire_sec.test (+29/-0)
Percona-Server/mysql-test/suite/innodb/t/percona_log_arch_func.test (+19/-0)
Percona-Server/mysql-test/suite/innodb/t/percona_purge_archived_logs_before.test (+43/-0)
Percona-Server/mysql-test/suite/innodb/t/percona_purge_archived_logs_to.test (+39/-0)
Percona-Server/mysql-test/suite/sys_vars/r/innodb_log_arch_dir_basic.result (+38/-0)
Percona-Server/mysql-test/suite/sys_vars/r/innodb_log_arch_expire_sec_basic.result (+38/-0)
Percona-Server/mysql-test/suite/sys_vars/r/innodb_log_archive_basic.result (+38/-0)
Percona-Server/mysql-test/suite/sys_vars/t/innodb_log_arch_dir_basic.test (+60/-0)
Percona-Server/mysql-test/suite/sys_vars/t/innodb_log_arch_expire_sec_basic.test (+60/-0)
Percona-Server/mysql-test/suite/sys_vars/t/innodb_log_archive_basic.test (+61/-0)
Percona-Server/sql/handler.cc (+42/-0)
Percona-Server/sql/handler.h (+8/-0)
Percona-Server/sql/lex.h (+1/-0)
Percona-Server/sql/mysqld.cc (+2/-0)
Percona-Server/sql/sql_cmd.h (+2/-0)
Percona-Server/sql/sql_parse.cc (+43/-0)
Percona-Server/sql/sql_yacc.yy (+19/-1)
Percona-Server/storage/innobase/fil/fil0fil.cc (+34/-33)
Percona-Server/storage/innobase/handler/ha_innodb.cc (+78/-8)
Percona-Server/storage/innobase/include/fil0fil.h (+8/-6)
Percona-Server/storage/innobase/include/log0log.h (+20/-7)
Percona-Server/storage/innobase/include/log0recv.h (+2/-2)
Percona-Server/storage/innobase/include/srv0srv.h (+14/-0)
Percona-Server/storage/innobase/include/univ.i (+3/-0)
Percona-Server/storage/innobase/log/log0log.cc (+101/-62)
Percona-Server/storage/innobase/log/log0recv.cc (+18/-16)
Percona-Server/storage/innobase/srv/srv0srv.cc (+140/-0)
Percona-Server/storage/innobase/srv/srv0start.cc (+17/-20)
This can also be seen without the crash:
2013-03-10 00:05:07 22557 [Note] /ssd/Percona- Server- 5.6.8-alpha60. 2-313-debug. Linux.x86_ 64/bin/ mysqld- debug: ready for connections. alpha60. 2-debug- log' socket: '/ssd/198649/ current1_ 1/tmp/master. sock' port: 13000 Percona Server with XtraDB (GPL), Release alpha60.2, Revision 313-debug ib_log_ archive_ 000000056616601 6 ib_log_ archive_ 000000056616601 6. Server- 5.6.8-alpha60. 2-313-debug. Linux.x86_ 64/bin/ mysqld- debug: Normal shutdown
Version: '5.6.10-
2013-03-10 00:06:14 7f2e0effd700 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
2013-03-10 00:06:14 7f2e0effd700 InnoDB: File name /ssd/tmp/
2013-03-10 00:06:14 7f2e0effd700 InnoDB: File operation call: 'delete' returned OS error 71.
InnoDB: Note: can't delete archived log file /ssd/tmp/
2013-03-10 00:10:50 22557 [Note] /ssd/Percona-
Note the 'delete' versus 'open' above!