-
Type:
Bug
-
Status: Done
-
Priority:
Medium
-
Resolution: Fixed
-
Affects Version/s: None
-
Component/s: None
-
Labels:
-
Launchpad URL:
-
Upstream Bug URL:
**Reported in Launchpad by monty solomon last update 24-02-2015 09:24:07
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