Bug #48373 InnoDB error message is ambiguous
Submitted: 28 Oct 2009 11:34
Reporter: Oli Sennhauser Email Updates:
Status: Verified Impact on me:
Category:MySQL Server: InnoDB storage engine Severity:S4 (Feature request)
Version:5.0, (5.1) OS:Any
Assigned to: CPU Architecture:Any
Tags: innodb error message ambiguous

[28 Oct 2009 11:34] Oli Sennhauser
Customer gets the following error message:

> InnoDB: Database page corruption on disk or a failed
> InnoDB: file read of page 619774.

Now he would like to know if this is caused by a page corruption (what he suspects) OR from a failed file read (what could also be the case because he is testing disk systems).

How to repeat:

1893 buf_page_io_complete(
1930   if (buf_page_is_corrupted(block->frame)) {
1931   fprintf(stderr,
1932     "InnoDB: Database page corruption on disk or a failed\n"
1933     "InnoDB: file read of page %lu.\n", (ulong) block->offset);
1934   ...

Suggested fix:
Either fix the error message if one of the above is not the case or specify two different error exits.