MySQL 5.0.19-2 and repair problems...
in [MyODBC]
|
From: Sander Smeenk on 29 Mar 2006 09:52 Hello! I'm having a weird problem i'd like to hear your opinions about: | [18:44] [root(a)zwart:~] # mysqlcheck v games | v.games | error : Table './v/games' is marked as crashed and should be repaired | [18:44] [root(a)zwart:~] # mysqlcheck -r v games | v.games OK | [18:44] [root(a)zwart:~] # mysqlcheck v games | v.games | error : Key in wrong position at page 108544 | error : Corrupt | [18:45] [root(a)zwart:~] # mysqlcheck -f -r v games | v.games OK | [18:45] [root(a)zwart:~] # mysqlcheck v games | v.games | error : Key in wrong position at page 108544 | error : Corrupt | [18:45] [root(a)zwart:~] # /etc/init.d/mysql stop | Stopping MySQL database server: mysqld. | [18:45] [root(a)zwart:~] # cd /var/lib/mysql/v | [18:45] [root(a)zwart:/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] [root(a)zwart:/var/lib/mysql/v] # echo "REPAIR TABLE games" | mysql v | Table Op Msg_type Msg_text | v.games repair status OK | [18:48] [root(a)zwart:/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/mysql?unsub=myodbc(a)freebsd.csie.nctu.edu.tw
From: "Kishore Jalleda" on 29 Mar 2006 11:03 ------=_Part_7082_176413.1143648088508 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline 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 <ssm+mysql(a)freshdot.net> wrote: > > Hello! > > I'm having a weird problem i'd like to hear your opinions about: > > | [18:44] [root(a)zwart:~] # mysqlcheck v games > | v.games > | error : Table './v/games' is marked as crashed and should be repaire= d > | [18:44] [root(a)zwart:~] # mysqlcheck -r v games > | v.games OK > | [18:44] [root(a)zwart:~] # mysqlcheck v games > | v.games > | error : Key in wrong position at page 108544 > | error : Corrupt > | [18:45] [root(a)zwart:~] # mysqlcheck -f -r v games > | v.games OK > | [18:45] [root(a)zwart:~] # mysqlcheck v games > | v.games > | error : Key in wrong position at page 108544 > | error : Corrupt > | [18:45] [root(a)zwart:~] # /etc/init.d/mysql stop > | Stopping MySQL database server: mysqld. > | [18:45] [root(a)zwart:~] # cd /var/lib/mysql/v > | [18:45] [root(a)zwart:/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] [root(a)zwart:/var/lib/mysql/v] # echo "REPAIR TABLE games" | > mysql v > | Table Op Msg_type Msg_text > | v.games repair status OK > | [18:48] [root(a)zwart:/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/mysql?unsub=3Dkjalleda(a)gmail.co= m > > ------=_Part_7082_176413.1143648088508--
From: Sander Smeenk on 29 Mar 2006 12:47 Quoting Kishore Jalleda (kjalleda(a)gmail.com): > 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/mysql?unsub=myodbc(a)freebsd.csie.nctu.edu.tw
From: mysql on 29 Mar 2006 13:01 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(a)lists.mysql.com > From: Sander Smeenk <ssm+mysql(a)freshdot.net> > Subject: Re: MySQL 5.0.19-2 and repair problems... > > Quoting Kishore Jalleda (kjalleda(a)gmail.com): > > > 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/mysql?unsub=mysql(a)karsites.net > > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=myodbc(a)freebsd.csie.nctu.edu.tw
From: Sander Smeenk on 29 Mar 2006 13:18 Quoting mysql(a)karsites.net (mysql(a)karsites.net): > 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/mysql?unsub=myodbc(a)freebsd.csie.nctu.edu.tw
|
Next
|
Last
Pages: 1 2 Prev: Connector/ODBC 3.51.13 Next: MySQL 4.0.18 on Mac OS X 10.2.8 won't start |