List:Bugs« Previous MessageNext Message »
From:Michael Widenius Date:October 20 2000 2:28pm
Subject:Further info from previous email bug
View as plain text  
Hi!

>>>>> "Martin" == Martin Moss <martinm@stripped> writes:

Martin> Ok,
Martin> After a little more experimentation It looks like the following problems
Martin> occur.
Martin> When I start mysqld cleanly with --myisam-recover
Martin> And then start my webspider I get the 'user hasn't closed the table'.
Martin> However no further errors seem to occur.

Do you have a copy of the table before you started MySQL ?

Martin> However if I then stop the Webspider. issue a myisamchk -r *.MYI on my
Martin> Database tables. Then restart mysqld and start the webspier again, as soon
Martin> as it tries to INSERT anything into the database I get the error 127
Martin> problem. It does however perform several deletes successfully, but fails at
Martin> the first INSERT.

When you stopped WebSpider, did you also stop mysqld?
If not the problem is that you didn't do 'flush tables' before running
repair.

Martin> The errors I now get are:-

Martin> Checking MyISAM file: Pages.MYI
Martin> Data records:     875   Deleted blocks:       0
Martin> - check file-size
Martin> myisamchk: error: Size of datafile is: 15836            Should be: 77056
Martin> - check key delete-chain
Martin> - check record delete-chain
Martin> - check index reference
Martin> - check data record references index: 1
Martin> myisamchk: error: Found key at page 2048 that points to record outside
Martin> datafile
Martin> - check record links
Martin> myisamchk: error: Record-count is not ok; is 175          Should be: 875
Martin> myisamchk: warning: Found        175 parts                Should be: 875
Martin> parts
Martin> MyISAM-table 'Pages.MYI' is corrupted
Martin> Fix it using switch "-r" or "-o"

Can you try stopping webspider and mysqld, and run:

myisamchk -r Pages
myisamchk Pages

If you don't get any errors for the second run, then the file should
be ok and you inserts should work.  If not, please ftp a copy of the
file to ftp://support.mysql.com/pub/mysql/Incoming and we will look at
this right away!

Regards,
Monty
Thread
Further info from previous email bugMartin Moss20 Oct
  • Further info from previous email bugMichael Widenius20 Oct