Bug #11676 A corruption of an underling .MYD table is reported as corruption of the .MRG
Submitted: 30 Jun 2005 20:08 Modified: 3 Aug 2005 15:40
Reporter: Raymond DeRoo Email Updates:
Status: Won't fix Impact on me:
None 
Category:MySQL Server Severity:S2 (Serious)
Version:4.1.13-bk OS:Linux (Linux)
Assigned to: Ingo Strüwing CPU Architecture:Any

[30 Jun 2005 20:08] Raymond DeRoo
Description:
A corruption in one of the underlining .MYD files of a merge table report the error being corruption in the .MRG file, not the specific .MYD file.

How to repeat:
FLUSH TABLES;
DROP TABLE IF EXISTS m1, m2;
CREATE TABLE m1 ( a INT PRIMARY KEY ) ENGINE=MyISAM;
CREATE TABLE m2 ( a INT PRIMARY KEY ) ENGINE=MERGE UNION (m1);
INSERT INTO m1 VALUES ( 1 );
FLUSH TABLES;

edit m1.MYD, replace contents with ABC

FLUSH TABLES;
CHECK TABLE m1;
SELECT * FROM m1;
FLUSH TABLES;
SELECT * FROM m2;
[3 Aug 2005 15:40] Ingo Strüwing
The whole MERGE error reporting is weird. Fixing it would be a major act. This particular case is consistent with similar cases and should not be fixed separately.