try

REPAIR TABLE 'tablename'


Gleb Paharenko wrote:

>Hello.
>
>
>
>REPAIR TABLE ... USE_FRM helps in difficult cases. See:
>
>  http://dev.mysql.com/doc/mysql/en/repair-table.html
>
>
>
>
>
>
>
>
>
>
>
>Per Jessen <[EMAIL PROTECTED]> wrote:
>
>  
>
>>All,
>>    
>>
>
>  
>
>>I've got a table with about 25mill rows that was victim of a crash recently. 
>>(power-failure).
>>    
>>
>
>  
>
>>I've been trying to recover it, but I'm not making much progress. 
>>    
>>
>
>  
>
>
>  
>
>>>From the most recent attempts:
>>    
>>
>
>  
>
>
>  
>
>>myisamchk --safe-recover --force <table>
>>    
>>
>
>  
>
>>- recovering (with keycache) MyISAM-table '<table>'
>>    
>>
>
>  
>
>>Data records: 21622679
>>    
>>
>
>  
>
>>49800008000
>>    
>>
>
>  
>
>>7256000
>>    
>>
>
>  
>
>>10627000
>>    
>>
>
>  
>
>>myisamchk: error: 126 for record at pos 1589881104
>>    
>>
>
>  
>
>>MyISAM-table '<table>' is not fixed because of errors
>>    
>>
>
>  
>
>
>  
>
>>myisamchk -r --force --tmpdir=/data2/tmp <table>
>>    
>>
>
>  
>
>>- recovering (with sort) MyISAM-table '<table>'
>>    
>>
>
>  
>
>>Data records: 12876899
>>    
>>
>
>  
>
>>- Fixing index 1
>>    
>>
>
>  
>
>>- Fixing index 2
>>    
>>
>
>  
>
>>- Fixing index 3
>>    
>>
>
>  
>
>>Key 3 - Found wrong stored record at 0
>>    
>>
>
>  
>
>>MyISAM-table '<table>' is not fixed because of errors
>>    
>>
>
>  
>
>
>  
>
>
>  
>
>>Where do I go from here?  I've got a backup of the table, but I'm not sure 
>>what sort of state it
>>    
>>
>
>  
>
>>is in.
>>    
>>
>
>  
>
>
>  
>
>
>
>
>  
>

Reply via email to