That usually means the table is corrupt beyond repair and nothing is really
fixing it or there is something one cannot easily comprehend ( this usually
happens with inconsistency among deleted records and some kind of mismatch
that occurs) -anyway what I would really advice in this case is to
Quoting Kishore Jalleda ([EMAIL PROTECTED]):
That usually means the table is corrupt beyond repair and nothing is really
fixing it or there is something one cannot easily comprehend ( this usually
happens with inconsistency among deleted records and some kind of mismatch
that occurs)
there are
any errors in the table.
Keith
In theory, theory and practice are the same;
in practice they are not.
On Wed, 29 Mar 2006, Sander Smeenk wrote:
To: mysql@lists.mysql.com
From: Sander Smeenk [EMAIL PROTECTED]
Subject: Re: MySQL 5.0.19-2 and repair problems...
Quoting Kishore Jalleda
Quoting [EMAIL PROTECTED] ([EMAIL PROTECTED]):
Have you tried the following myisamchk option:
--extend-check, -e
Yup. But that won't even work at ALL:
# myisamchk -e games.MYI
Checking MyISAM file: games.MYI
Data records: 10644 Deleted blocks: 0
- check file-size
- check record
what's the result of
SHOW CREATE TABLE games
??
I'd drop the indexes on the games table, and then run repair tables,
and then put the indexes back in. Worth a shot.
-Sheeri
On 3/29/06, Sander Smeenk [EMAIL PROTECTED] wrote:
Quoting [EMAIL PROTECTED] ([EMAIL PROTECTED]):
Have you tried
Quoting sheeri kritzer ([EMAIL PROTECTED]):
what's the result of
SHOW CREATE TABLE games
It gives me the create statement for that table.
All perfectly normal. MyISAM table, latin1 charset.
I'd drop the indexes on the games table, and then run repair tables,
and then put the indexes back
According to the manual, 64 to 32 bit shouldn't matter, it should work
fine as long as they're both little endian, or they're both big
endian.
I've copied MyISAM tables from 64 to 32 bit without a problem.
BTW, I suggested that because in the error it said:
myisamchk: error: Key in wrong
Quoting sheeri kritzer ([EMAIL PROTECTED]):
According to the manual, 64 to 32 bit shouldn't matter, it should work
fine as long as they're both little endian, or they're both big
endian.
This friend of mine said he also had major problems moving 32-64.
Crashing mysql's, but not corrupt
