List:General Discussion« Previous MessageNext Message »
From:Michael Widenius Date:June 29 1999 4:39pm
Subject:ERROR 2000: Got error 134 from table handler
View as plain text  
>>>>> "Boaz" == Boaz Yahav <berber@stripped> writes:

Boaz> I get the following error :
Boaz> ERROR 2000: Got error 134 from table handler
 
Boaz> I tried running isamchk -r *.ISM and got lots of :
 
Boaz> Found block with too small length at 7235454; Skipped
Boaz> Found link that points at 4216144885 (outside data file) at 7235575
Boaz> Found link that points at 3638450802 (outside data file) at 7235616
Boaz> Found link that points at 1814349834 (outside data file) at 7236445
Boaz> Found link that points at 3346084560 (outside data file) at 7236631
Boaz> Found link that points at 2720532029 (outside data file) at 7236714
Boaz> Found link that points at 552992837 (outside data file) at 7236821
Boaz> Found link that points at 348484468 (outside data file) at 7236844
Boaz> Found block with too small length at 7237151; Skipped
Boaz> Found block with too small length at 7237153; Skipped
Boaz> Found link that points at 2171674663 (outside data file) at 7237182
Boaz> Found block with too small length at 7237297; Skipped
 
Boaz> Any idea what can be done?
 
Hi!

Did you run isamchk while mysqld was running?

Isn't the table ok now?

You will get warnings as above if isamchk found something wrong;  A
single error in the data file can give many warnings.

isamchk ends by reporting how many rows isamchk found and how many it
should have found.  This should give you an indication if you have
anything to worry about!

Regards,
Monty
Thread
ERROR 2000: Got error 134 from table handlerBoaz Yahav28 Jun
  • ERROR 2000: Got error 134 from table handlerMichael Widenius29 Jun