Bug #77578 Please indicate filename of files which can't be written to or read from
Submitted: 1 Jul 2015 11:04 Modified: 2 Jul 2015 6:46
Reporter: Simon Mudd (OCA) Email Updates:
Status: Duplicate Impact on me:
Category:MySQL Server: InnoDB storage engine Severity:S3 (Non-critical)
Version:5.6.25 OS:Any
Assigned to: CPU Architecture:Any
Tags: corruption, crash, innnodb

[1 Jul 2015 11:04] Simon Mudd
A recent crash probably triggered by a failed disk shows this:

2015-07-01 12:56:13 17955 [ERROR] InnoDB: Tried to read 16384 bytes at offset 213925888. Was only able to read 8192.
2015-07-01 12:56:13 7fc17a3bf700  InnoDB: Operating system error number 2 in a file operation.

Unfortunately the information is not very helpful as the filename is not provided.
If I have a lot of tables it would be time-consuming to try to identify the broken table and then figure out if anything can be done to recovery the data. As it is I'd have to check all .ibd files and this wastes a lot of time.

How to repeat:
See above:

Suggested fix:
Make InnoDB indicate the filename of the file affected by this problem so that further diagnosis is not needed.

No this doesn't happen often but if it does having this useful information would be very good.
[1 Jul 2015 13:30] MySQL Verification Team
perhaps a duplicate of https://bugs.mysql.com/bug.php?id=76020 ?
[2 Jul 2015 6:46] MySQL Verification Team
Hello Simon,

Thank you for the report.
As Shane observed, this is surely duplicate of Bug #76020.

[2 Jul 2015 6:48] MySQL Verification Team
related but for win builds - Bug #76670