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
