Re: MySQL 5.0.19-2 and repair problems...
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 rebuild the table from a working/clean backup and start-over, if this is a slave then thats very easy to do, if not it depends on your latest clean backup available .. Just my 2c Kishore Jalleda On 3/29/06, Sander Smeenk [EMAIL PROTECTED] wrote: Hello! I'm having a weird problem i'd like to hear your opinions about: | [18:44] [EMAIL PROTECTED]:~] # mysqlcheck v games | v.games | error: Table './v/games' is marked as crashed and should be repaired | [18:44] [EMAIL PROTECTED]:~] # mysqlcheck -r v games | v.gamesOK | [18:44] [EMAIL PROTECTED]:~] # mysqlcheck v games | v.games | error: Key in wrong position at page 108544 | error: Corrupt | [18:45] [EMAIL PROTECTED]:~] # mysqlcheck -f -r v games | v.gamesOK | [18:45] [EMAIL PROTECTED]:~] # mysqlcheck v games | v.games | error: Key in wrong position at page 108544 | error: Corrupt | [18:45] [EMAIL PROTECTED]:~] # /etc/init.d/mysql stop | Stopping MySQL database server: mysqld. | [18:45] [EMAIL PROTECTED]:~] # cd /var/lib/mysql/v | [18:45] [EMAIL PROTECTED]:/var/lib/mysql/v] # myisamchk -r games.MYI | - recovering (with sort) MyISAM-table 'games.MYI' | Data records: 10644 | - Fixing index 1 | - Fixing index 2 | [18:48] [EMAIL PROTECTED]:/var/lib/mysql/v] # echo REPAIR TABLE games | mysql v | Table Op Msg_typeMsg_text | v.games repair status OK | [18:48] [EMAIL PROTECTED]:/var/lib/mysql/v] # myisamchk games.MYI | Checking MyISAM file: games.MYI | Data records: 10644 Deleted blocks: 0 | - check file-size | - check record delete-chain | - check key delete-chain | - check index reference | - check data record references index: 1 | - check data record references index: 2 | myisamchk: error: Key in wrong position at page 108544 | - check record links | myisamchk: error: Keypointers and record positions doesn't match | MyISAM-table 'games.MYI' is corrupted | Fix it using switch -r or -o | [1]17564 exit 255 myisamchk games.MYI No matter WHAT i try, fixing with 'repair table' using mysqlcheck, myisamchk, -o, -r, -f, it seems like i can't repair this table. So what's going on? Does anyone have any clue? Regards, Sander. -- | Honk if you love peace and quiet. | 1024D/08CEC94D - 34B3 3314 B146 E13C 70C8 9BDB D463 7E41 08CE C94D -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: MySQL 5.0.19-2 and repair problems...
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) -anyway what I would really advice in this case is to rebuild the table from a working/clean backup and start-over, if this is a slave then thats very easy to do, if not it depends on your latest clean backup available .. Amazing. Amazing that even the tools can't tell me it's unfixable. I mean, i tried everything. :) I'll restore the databases from the master (this isn't a slave, but it's a machine i want to switch to when it finally becomes stable...) and see where we get from that... The machine didn't crash. Nor did mysql. Any clue what might cause this to happen? Disk looks fine too, no read or write errors whatsoever... Thanks, Sander. -- | Just remember -- if the world didn't suck, we would all fall off. | 1024D/08CEC94D - 34B3 3314 B146 E13C 70C8 9BDB D463 7E41 08CE C94D -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: MySQL 5.0.19-2 and repair problems...
Have you tried the following myisamchk option: --extend-check, -e Check the table very thoroughly. This is quite slow if the table has many indexes. This option should only be used in extreme cases. Normally, myisamchk or myisamchk --medium-check should be able to determine whether 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 ([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) -anyway what I would really advice in this case is to rebuild the table from a working/clean backup and start-over, if this is a slave then thats very easy to do, if not it depends on your latest clean backup available .. Amazing. Amazing that even the tools can't tell me it's unfixable. I mean, i tried everything. :) I'll restore the databases from the master (this isn't a slave, but it's a machine i want to switch to when it finally becomes stable...) and see where we get from that... The machine didn't crash. Nor did mysql. Any clue what might cause this to happen? Disk looks fine too, no read or write errors whatsoever... Thanks, Sander. -- | Just remember -- if the world didn't suck, we would all fall off. | 1024D/08CEC94D - 34B3 3314 B146 E13C 70C8 9BDB D463 7E41 08CE C94D -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: MySQL 5.0.19-2 and repair problems...
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 delete-chain - check key delete-chain - check index reference - check data record references index: 1 - check data record references index: 2 myisamchk: error: Key in wrong position at page 715776 - check records and index references myisamchk: error: Keypointers and record positions doesn't match MyISAM-table 'games.MYI' is corrupted Fix it using switch -r or -o Strange, huh! -- | Don't hate yourself in the morning -- sleep till noon. | 1024D/08CEC94D - 34B3 3314 B146 E13C 70C8 9BDB D463 7E41 08CE C94D -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: MySQL 5.0.19-2 and repair problems...
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 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 delete-chain - check key delete-chain - check index reference - check data record references index: 1 - check data record references index: 2 myisamchk: error: Key in wrong position at page 715776 - check records and index references myisamchk: error: Keypointers and record positions doesn't match MyISAM-table 'games.MYI' is corrupted Fix it using switch -r or -o Strange, huh! -- | Don't hate yourself in the morning -- sleep till noon. | 1024D/08CEC94D - 34B3 3314 B146 E13C 70C8 9BDB D463 7E41 08CE C94D -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: MySQL 5.0.19-2 and repair problems...
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 in. Worth a shot. Funny, i haven't tried that yet, and lo-and-behold, after rebuilding the index (that's all i did): | [22:27] [EMAIL PROTECTED]:/var/lib/mysql/v] # myisamchk games.MYI | Checking MyISAM file: games.MYI | Data records: 10644 Deleted blocks: 0 | - check file-size | - check record delete-chain | - check key delete-chain | - check index reference | - check data record references index: 1 | - check data record references index: 2 | - check record links Aparently, what i heard from a friend, it's not done to binary copy tables from 32bit systems over to 64bit systems. Is it as bad to binary copy tables from 64bit to 32bit systems? It's vital in our current setup that binary copy of tables works. Or we need to set up replication right now ;) Lemmeknow and Thanks!! Sander. -- | Lead me not into temptation... I can find it myself. | 1024D/08CEC94D - 34B3 3314 B146 E13C 70C8 9BDB D463 7E41 08CE C94D -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: MySQL 5.0.19-2 and repair problems...
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 position at page 715776 - check records and index references Did you by any chance symlink or move files, or not move the key files? My guess is that might cause that problem, otherwise, I have no idea what would cause it. -Sheeri On 3/29/06, Sander Smeenk [EMAIL PROTECTED] wrote: 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 in. Worth a shot. Funny, i haven't tried that yet, and lo-and-behold, after rebuilding the index (that's all i did): | [22:27] [EMAIL PROTECTED]:/var/lib/mysql/v] # myisamchk games.MYI | Checking MyISAM file: games.MYI | Data records: 10644 Deleted blocks: 0 | - check file-size | - check record delete-chain | - check key delete-chain | - check index reference | - check data record references index: 1 | - check data record references index: 2 | - check record links Aparently, what i heard from a friend, it's not done to binary copy tables from 32bit systems over to 64bit systems. Is it as bad to binary copy tables from 64bit to 32bit systems? It's vital in our current setup that binary copy of tables works. Or we need to set up replication right now ;) Lemmeknow and Thanks!! Sander. -- | Lead me not into temptation... I can find it myself. | 1024D/08CEC94D - 34B3 3314 B146 E13C 70C8 9BDB D463 7E41 08CE C94D -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: MySQL 5.0.19-2 and repair problems...
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 tables. Well, i had crashing mysql's earlier (see my other post on this list about MySQL on AMD64) but that seems over now. Now i have corrupt tables. Or, better stated, all tables with indexes on them are corrupt. I've copied MyISAM tables from 64 to 32 bit without a problem. Great to hear. Have to try it out myself to be sure though, but it's good to hear you have no problems doing that. BTW, I suggested that because in the error it said: myisamchk: error: Key in wrong position at page 715776 - check records and index references Did you by any chance symlink or move files, or not move the key files? My guess is that might cause that problem, otherwise, I have no idea what would cause it. Nope. What i did is, in psuedocode: for database in datadir/* for table in datadir/database/* lock table flush table binary copy table* to tempdir unlock table } } What seems like a normal binary copy to me. All three files were copied, the .frm, the .MYI and the .MYD. Regards, Sander. -- | 't Gaat om 't spel, niet om de knikkers! | 1024D/08CEC94D - 34B3 3314 B146 E13C 70C8 9BDB D463 7E41 08CE C94D -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
