List:General Discussion« Previous MessageNext Message »
From:Michael Widenius Date:October 5 1999 5:21pm
Subject:isamchk message!
View as plain text  
>>>>> "ycnee" == ycnee  <ycnee@stripped> writes:

ycnee> root@dbs [home/mysql]% bin/isamchk -r var/bbs/note_content.ISM
ycnee> - recovering ISAM-table 'var/bbs/note_content.ISM'
ycnee> Data records: 388920
ycnee> - Fixing index 1
ycnee> Found link that points at 2036733184 (outside data file) at 5973222
ycnee> Found link that points at 947066112 (outside data file) at 17210284
ycnee> Found block with too small length at 57579096; Skipped
ycnee> Found block with too small length at 63819945; Skipped
ycnee> Found block with too small length at 85917941; Skipped
ycnee> Found link that points at 839778304 (outside data file) at 85917949
ycnee> Found block with too small length at 106083227; Skipped
ycnee> Found block with too small length at 106727304; Skipped
ycnee> Found block with too small length at 111234235; Skipped
ycnee> Found link that points at 218103826 (outside data file) at 119702025
ycnee> Found block with too small length at 120050526; Skipped
ycnee> Found block with too small length at 120050574; Skipped
ycnee> Found block with too small length at 128235589; Skipped
ycnee> Found link that points at 2500329472 (outside data file) at 130290638
ycnee> Found link that points at 1768297472 (outside data file) at 131713010
ycnee> Found block with too small length at 131823587; Skipped
ycnee> Found block with too small length at 132809505; Skipped
ycnee> Data records: 388921

ycnee> any idea with the above message??

Hi!

The above means that someone (something?) killed MySQL in the middle
of an update.  You have also blob/text or varchar columns in your table.
While checking the table, isamchk found a row that was not ok and
started scanning the table from this to find the next complete row.
During the scan, isamchk may report a lot of warnings that can be
ignored.

The important thing is that when you started isamchk, you had 388920
rows in the table and when isamchk ended you had 388921.  This suggest 
that even if MySQL was killed in the middle of an update, isamchk was
able to get back all rows.

Regards,
Monty
Thread
isamchk message!ycnee30 Sep
  • Re: isamchk message!sinisa30 Sep
  • isamchk message!Michael Widenius5 Oct