> From: ad...@asarian-host.net
> Subject: SOLVED! (was: RE: Error : Incorrect key file for table 'X')
> Date: Sun, 26 Apr 2009 21:15:15 +
> To: mysql@lists.mysql.com
>
> Okay, I finally got it fixed. I was on the right track going the mysqldump
> route, but tur
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,
st 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
-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.
>
n-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 belo
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 --ex
