Re: Re: Help! Recovering corrupt table
Rolf, Tuesday, September 03, 2002, 1:57:49 AM, you wrote: RH I'm using MySQL 3.23.51. I have a table which started giving 127 errors. [skip] RH It recovers my table but I end up with only 1030 out of 27497 rows, RH so that's not a log of help! RH Running myisamchk -r -e gives a similar result (only 1030 rows are RH recovered), as does truncating the table first then restored the MYD RH file and running myiasmchk. RH Any other suggestions as to what to try? Could you repair table with REPAIR TABLE .. USE_FRM ? RH Thanks for the the suggestion. What does USE_FRM mean? That gives a RH syntax error. If I do a plain REPAIR TABLE then it has the same RH effect as myisamchk, just giving me 1030 out of 27000+ rows! Oh! My fault :( It's supported only since 4.0.2 Could you use 4.0.2 temporarily? Does it also deletes records? RH Not sure what you mean? If you would use REPAIR TABLE .. USE_FRM it also deletes 26 thousand rows? -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.net http://www.ensita.net/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Victoria Reznichenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.net ___/ www.mysql.com - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Help! Recovering corrupt table
Rolf, Monday, September 02, 2002, 3:38:06 PM, you wrote: RH I'm using MySQL 3.23.51. I have a table which started giving 127 errors. [skip] RH It recovers my table but I end up with only 1030 out of 27497 rows, RH so that's not a log of help! RH Running myisamchk -r -e gives a similar result (only 1030 rows are RH recovered), as does truncating the table first then restored the MYD RH file and running myiasmchk. RH Any other suggestions as to what to try? RH I'm happy to try to write some code of my own to walk through the MYD RH file and extract anything that looks like valid data. Is the MYD file RH format documented anywhere? Could you repair table with REPAIR TABLE .. USE_FRM ? Does it also deletes records? -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.net http://www.ensita.net/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Victoria Reznichenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.net ___/ www.mysql.com - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Help! Recovering corrupt table
RH I'm using MySQL 3.23.51. I have a table which started giving 127 errors. [skip] RH It recovers my table but I end up with only 1030 out of 27497 rows, RH so that's not a log of help! RH Running myisamchk -r -e gives a similar result (only 1030 rows are RH recovered), as does truncating the table first then restored the MYD RH file and running myiasmchk. RH Any other suggestions as to what to try? Could you repair table with REPAIR TABLE .. USE_FRM ? Thanks for the the suggestion. What does USE_FRM mean? That gives a syntax error. If I do a plain REPAIR TABLE then it has the same effect as myisamchk, just giving me 1030 out of 27000+ rows! Does it also deletes records? Not sure what you mean? Regards, -Rolf -- Rolf Howarth, Square Box Systems Ltd, Stratford-upon-Avon UK. - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Help! Recovering corrupt table
At 23:57 +0100 9/2/02, Rolf Howarth wrote: RH I'm using MySQL 3.23.51. I have a table which started giving 127 errors. [skip] RH It recovers my table but I end up with only 1030 out of 27497 rows, RH so that's not a log of help! RH Running myisamchk -r -e gives a similar result (only 1030 rows are RH recovered), as does truncating the table first then restored the MYD RH file and running myiasmchk. RH Any other suggestions as to what to try? Could you repair table with REPAIR TABLE .. USE_FRM ? Thanks for the the suggestion. What does USE_FRM mean? That gives a syntax error. That's because USE_FRM isn't supported until MySQL 4.0.2. It means that the repair operation uses the table's .frm (description) file in order to determine what the structure of the indexes should be. It can be useful if the index file has been corrupted beyond recognition. If I do a plain REPAIR TABLE then it has the same effect as myisamchk, just giving me 1030 out of 27000+ rows! Does it also deletes records? Not sure what you mean? Regards, -Rolf -- Rolf Howarth, Square Box Systems Ltd, Stratford-upon-Avon UK. - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
