innodb does not report filename in I/O error message

[monty solomon]

InnoDB experienced an I/O error and crashed but did not report the name of the file it was trying to read

2015-01-18 19:00:57 5260 [ERROR] InnoDB: Tried to read 16384 bytes at offset 536
428544. Was only able to read 0.
2015-01-18 19:00:57 7f6190e5a700 InnoDB: Operating system error number 5 in a file operation.
InnoDB: Error number 5 means 'Input/output error'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
2015-01-18 19:00:57 5260 [ERROR] InnoDB: File (unknown): 'read' returned OS error 105. Cannot continue operation
150118 19:00:57 mysqld_safe Number of processes running now: 0
150118 19:00:57 mysqld_safe mysqld restarted

mysql Ver 14.14 Distrib 5.6.22-71.0, for Linux (x86_64) using EditLine wrapper
Server version: 5.6.22-71.0-log Percona Server (GPL), Release 71.0, Revision 726

CentOS release 6.5 (Final)
Linux 2.6.32-431.el6.x86_64 #1 SMP Fri Nov 22 03:15:09 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

[Valerii Kravchuk (valerii-kravchuk)]

This is easy to confirm by code review:

[openxs@chief percona-5.6]$ grep -rn os_file_handle_error_cond_exit *
storage/innobase/os/os0file.cc:586:os_file_handle_error_cond_exit(
storage/innobase/os/os0file.cc:684: return(os_file_handle_error_cond_exit(name, operation, TRUE, FALSE));
storage/innobase/os/os0file.cc:700: return(os_file_handle_error_cond_exit(
[openxs@chief percona-5.6]$ vi +684 storage/innobase/os/os0file.cc
[openxs@chief percona-5.6]$ grep -rn os_file_handle_error *
storage/innobase/os/os0file.cc:586:os_file_handle_error_cond_exit(
storage/innobase/os/os0file.cc:678:os_file_handle_error(
storage/innobase/os/os0file.cc:684: return(os_file_handle_error_cond_exit(name, operation, TRUE, FALSE));
storage/innobase/os/os0file.cc:692:os_file_handle_error_no_exit(
storage/innobase/os/os0file.cc:700: return(os_file_handle_error_cond_exit(
storage/innobase/os/os0file.cc:841: os_file_handle_error(dirname, "opendir");
storage/innobase/os/os0file.cc:852: os_file_handle_error(dirname, "opendir");
storage/innobase/os/os0file.cc:874: os_file_handle_error_no_exit(NULL, "closedir", FALSE);
storage/innobase/os/os0file.cc:886: os_file_handle_error_no_exit(NULL, "closedir", FALSE);
storage/innobase/os/os0file.cc:958: os_file_handle_error_no_exit(NULL, "readdir_next_file", FALSE);
storage/innobase/os/os0file.cc:1044: os_file_handle_error_no_exit(full_path, "stat", FALSE);
storage/innobase/os/os0file.cc:1094: os_file_handle_error_no_exit(
storage/innobase/os/os0file.cc:1108: os_file_handle_error_no_exit(pathname, "mkdir", FALSE);
storage/innobase/os/os0file.cc:1216: retry = os_file_handle_error(
storage/innobase/os/os0file.cc:1283: retry = os_file_handle_error(
storage/innobase/os/os0file.cc:1533: os_file_handle_error_no_exit(name, "ioctl", FALSE);
storage/innobase/os/os0file.cc:1704: retry = os_file_handle_error_no_exit(
storage/innobase/os/os0file.cc:1707: retry = os_file_handle_error(name, operation);
storage/innobase/os/os0file.cc:1789: retry = os_file_handle_error_no_exit(
storage/innobase/os/os0file.cc:1792: retry = os_file_handle_error(name, operation);
storage/innobase/os/os0file.cc:1912: os_file_handle_error_no_exit(name, "delete", FALSE);
storage/innobase/os/os0file.cc:1976: os_file_handle_error_no_exit(name, "delete", FALSE);
storage/innobase/os/os0file.cc:2020: os_file_handle_error_no_exit(oldpath, "rename", FALSE);
storage/innobase/os/os0file.cc:2029: os_file_handle_error_no_exit(oldpath, "rename", FALSE);
storage/innobase/os/os0file.cc:2060: os_file_handle_error(NULL, "close");
storage/innobase/os/os0file.cc:2069: os_file_handle_error(NULL, "close");
storage/innobase/os/os0file.cc:2170: os_file_handle_error_no_exit (name, "posix_fallocate",
storage/innobase/os/os0file.cc:2360: os_file_handle_error(NULL, "flush");
storage/innobase/os/os0file.cc:2414: os_file_handle_error(NULL, "flush");
storage/i...

[Laurynas Biveinis (laurynas-biveinis)]

Is there an upstream report?

[Valerii Kravchuk (valerii-kravchuk)]

There is now, http://bugs.mysql.com/bug.php?id=76020.

[Shahriyar Rzayev (rzayev-sehriyar)]

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