Bug #6137 unaccessible catalog when one of tables crashed

• Submitted: 18 Oct 2004 8:00
• Modified: 14 Aug 2006 10:54
• Reporter: Jaroslav Uher
• Status: Closed
• Category: MySQL Administrator
• Severity: S4 (Feature request)
• Version: 1.0.13
• OS: Windows (Windows NT SP6)
• Assigned to: Vladimir Kolesnikov
• CPU Architecture: Any
• Tags: Catalog

[18 Oct 2004 8:00] Jaroslav Uher

Description:
if one of tables is crashed (MYD or MYI file corupted), MA displays message:
-----
Error while fetching Schema Table Status.
MySQL Error Number 1016
Can't ope file: '....table name...MYI'. (errno: 132)
-----
Catalog is unacessible and cannot be used Maintenance functionality.

How to repeat:
Edit MYI file to be corupted
In MA go to catalogs and click on schemata with corupted table
MA shows message above.

Suggested fix:
Display warning message (short description for all problems)
Display list of tables with marked corupted tables (+ message returned from MySQL server)
Grey-out button 'Edit table' when corupted one is selected.

[14 Aug 2006 10:54] Vladimir Kolesnikov

I cannot repro this behavour with latest versions of MySQL Server/Administrator. When .MYI or .MYD is broken, table is shown and can be checked/repaired. The only issue that I have noticed is that when .MYF file is broken MA doesn't show the object (table or view) on the catalog page as the server cannot tell what it is - table or view, like this ('broken' was a table):

mysql> show table status \G
*************************** 1. row ***************************
           Name: broken
         Engine: NULL
        Version: NULL
     Row_format: NULL
           Rows: NULL
 Avg_row_length: NULL
    Data_length: NULL
Max_data_length: NULL
   Index_length: NULL
      Data_free: NULL
 Auto_increment: NULL
    Create_time: NULL
    Update_time: NULL
     Check_time: NULL
      Collation: NULL
       Checksum: NULL
 Create_options: NULL
        Comment: Incorrect information in file: '.\test\broken.frm'