今晚InnoDB: File operation call: 'flush' 数据库自启动

nttctq

情景：下面的a、b今晚出现问题如下。以前也出现过一样的错，除了日期别的都一样。
出现在这样的错误时，数据库会自动重启。
但今天重启后到十点时，数据库又重启了。但这次只出现a中的报错，没有出现b的报错。难道不是硬盘的问题

a、数据库中出现的问题：
111118 19:15:54  InnoDB: Error: the OS said file flush did not succeed
111118 19:15:54  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/ ... em-error-codes.html
InnoDB: File operation call: 'flush'.
InnoDB: Cannot continue operation.


b、系统中出现的提示：
kernel: sd 0:0:0:1: [sda] Unhandled sense code
kernel: sd 0:0:0:1: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
kernel: sd 0:0:0:1: [sda] Sense Key : Medium Error [current]
kernel: sd 0:0:0:1: [sda] Add. Sense: Unrecovered read error
kernel: sd 0:0:0:1: [sda] CDB: Write(10): 2a 00 08 55 f6 80 00 00 20 00
kernel: end_request: I/O error, dev sda, sector 139851392
kernel: Buffer I/O error on device dm-2, logical block 4245712
kernel: lost page write due to I/O error on dm-2
kernel: Buffer I/O error on device dm-2, logical block 4245713
kernel: lost page write due to I/O error on dm-2
kernel: Buffer I/O error on device dm-2, logical block 4245714
kernel: lost page write due to I/O error on dm-2
kernel: Buffer I/O error on device dm-2, logical block 4245715
kernel: lost page write due to I/O error on dm-2

Coolriver

看起来象是你的磁盘出问题了：　kernel: end_request: I/O error, dev sda, sector 139851392
而且你应该还是用的LVM环境吧。