Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I have a "kind of big" (maybe 300Mb of data) mysql isam table that is corrupted:

| mytable | check | warning  | Table is marked as crashed and last repair failed         |
| mytable | check | warning  | 3 clients are using or haven't closed the table properly  |
| mytable | check | warning  | Size of indexfile is: 436531200 Should be: 1024      |
| mytable | check | warning  | Size of datafile is: 361663548 Should be: 361662760 |
| mytable | check | error    | Record-count is not ok; is 685042 Should be: 0          |
| mytable | check | warning  | Found 685071 parts Should be: 0 parts      |
| mytable | check | error    | Corrupt

I'm trying to repair table mytable but it takes too long (repair table mytable). Please note that I don't have shell access to the server, only ftp and remote mysql connections.

Any tips to make this repair go faster?

As last resort I can ask the server admins to change some mysql parameters just to make this go faster, any tips in this case?

share|improve this question
    
How long is 'too long'? –  Stefan Lasiewski Sep 15 '10 at 0:47
    
3hours and counting... –  AlfaTeK Sep 15 '10 at 1:24

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.