Hello monty,

It seems like something changed in 3.23.31 and 32 in auto_repair
there.

I see on many servers after crash (i've resently got unexpected
powerdown for 10 of my machines so it worked like a good testcase) I
got tables failed to be repaired (or well selects fail on them)

28.Jan 12:26:34 : pid:13836 counter:61005 AllInOne MySqlEr
Query - #1016 [ruby.local] - Can't open file: 'g06layers_stat_providers.MYD'. (errno: 
144)
select id from layers_st45.g06layers_stat_providers where type=2 and 
begin=20010117000000 and counter=61005 and page_group=255
28.Jan 12:26:34 : pid:13836 h -- 61005/0 AllInOne rec:0 l:0 tm:5.54 
28.Jan 12:26:34 : pid:13836 h  61005/0 [17.1 18:34] - [] q:0.28 i:0.00 a:5.13

the check table for this table also reports

mysql> check table layers_st45.g06layers_stat_providers;
+--------------------------------------+-------+----------+---------------------------------------------------+
| Table                                | Op    | Msg_type | Msg_text                   
|                       |
+--------------------------------------+-------+----------+---------------------------------------------------+
| g06layers_stat_providers             | check | warning  | Table is marked as crashed 
|and last repair failed |
| g06layers_stat_providers             | check | error    | Key 1 doesn't point at all 
|records                |
| layers_st45.g06layers_stat_providers | check | error    | Corrupt                    
|                       |
+--------------------------------------+-------+----------+---------------------------------------------------+
3 rows in set (6.60 sec)

It seems like this message is similar for many tables (I've checked
about 10 tables I found in my applicatin error log file)

mysql> check table layers_st27.g07layers_stat_framepages;
+---------------------------------------+-------+----------+---------------------------------------------------+
| Table                                 | Op    | Msg_type | Msg_text                  
|                        |
+---------------------------------------+-------+----------+---------------------------------------------------+
| g07layers_stat_framepages             | check | warning  | Table is marked as 
|crashed and last repair failed |
| g07layers_stat_framepages             | check | error    | Key 1 doesn't point at 
|all records                |
| layers_st27.g07layers_stat_framepages | check | error    | Corrupt                   
|                        |
+---------------------------------------+-------+----------+---------------------------------------------------+
3 rows in set (2.94 sec)


therefore the logfiles indicates the table was checked and has no
notes about it afterwards:

010127 13:11:48  Warning: Checking table:   './layers_st27/g07layers_stat_framepages'


As far then I check and repear all the tables explictly no error
messages appears in a log files - this points to the auto repair
procedure.

Also I found that after even single crash I got the followings case,
so this is not connected to crash during repair and so on...







  


  

-- 
Best regards,
 Peter                          mailto:[EMAIL PROTECTED]



---------------------------------------------------------------------
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/           (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Reply via email to