Okay, I finally got it fixed. I was on the right track going the mysqldump route, but turns out I had to physically do a 'rm -rf' on the mysql dir (sans the mysql database itself; and after mysqld was shut down, of course), even though I had mysqldump add command to DROP existing databases first. After that, the import succeeds, and all errors are gone.
Odd. It's been quite quiet on this list of late. I expected at least someone to know the answer. If this is indicative of people's interest in MySQL these days, then maybe it really IS a good idea to start using PostgreSQL. - Mark -----Original Message----- From: Mark [mailto:ad...@asarian-host.net] Sent: zondag 26 april 2009 17:04 To: mysql@lists.mysql.com Subject: RE: Error : Incorrect key file for table 'X' I found out it's actually a documented bug, for folks upgrading from 5.0.x to 5.1.x, http://bugs.mysql.com/bug.php?id=37631 And occurs with tables originally created with 4.0.x. There's currently no fix, it seems. There's a patch, but dev-comments to that patch suggest it can cause crashes. - Mark From: zhu dingze [mailto:mysql.li...@gmail.com] Sent: zondag 26 april 2009 16:40 To: Mark Cc: mysql@lists.mysql.com Subject: Re: Error : Incorrect key file for table 'X' Hey Dude, So many errors imply that there are some issues with your meta_data other than the tables and files itself. Please note, MySQL has upgrade some information in Information_schema Database. May I ask which kind of data have you been backup? including information_schema. Bests, Dingze 2009/4/25 Mark <ad...@asarian-host.net> C'mon, guys, there's gotta be someone who knows something about this. :) Anyone? Anyone? Bueller? Bueller? I even did a complete mysqldump (from the 5.0.77 mysqld) and imported it that way. To no luck, alas. Thanks, - Mark -----Original Message----- From: Mark [mailto:ad...@asarian-host.net] Sent: zaterdag 25 april 2009 2:34 To: mysql@lists.mysql.com Subject: Error : Incorrect key file for table 'X' Odd. I just painstakingly upgraded to MySQL 5.1.34, coming from 5.0.77. So, I run: "/usr/local/bin/mysql_upgrade", and get these all over the place (see below; just a few lines: the error list is too long to post in whole). So, accomodating MySQL, I run: /usr/local/bin/myisamchk --force --extend-check --update-state -O key_buffer=128M -O sort_buffer=128M -O read_buffer=2M -O write_buffer=2M /var/db/mysql/*/*.MYI Makes no difference, though. All the tables are unusable now (thank God for Vmware!). But obviously, I can't take it to the producton server like this (FreeBSD). Anyone any idea what's happening? Thanks, - Mark Repairing tables albatross.banned Error : Incorrect key file for table 'banned'; try to repair it error : Corrupt albatross.bridge Error : Incorrect key file for table 'bridge'; try to repair it error : Corrupt albatross.categories Error : Incorrect key file for table 'categories'; try to repair it error : Corrupt albatross.comments Error : Incorrect key file for table 'comments'; try to repair it error : Corrupt albatross.config Error : Incorrect key file for table 'config'; try to repair it error : Corrupt albatross.dict Error : Incorrect key file for table 'dict'; try to repair it error : Corrupt albatross.ecards Error : Incorrect key file for table 'ecards'; try to repair it error : Corrupt albatross.exif Error : Incorrect key file for table 'exif'; try to repair it error : Corrupt albatross.favpics Error : Incorrect key file for table 'favpics'; try to repair it error : Corrupt albatross.filetypes Error : Incorrect key file for table 'filetypes'; try to repair it error : Corrupt albatross.hit_stats Error : Incorrect key file for table 'hit_stats'; try to repair it error : Corrupt albatross.plugins Error : Incorrect key file for table 'plugins'; try to repair it error : Corrupt Etc, etc. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=mysql.li...@gmail.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=arch...@jab.org
