Good call... I should have figured that out my self. The old version
was 2.6:
/usr/bin/myisamchk (v2.6)
/usr/local/mysql-standard-4.1.8-apple-darwin7.6.0-powerpc/bin/myisamchk
(v2.7)
This is likely why I lost my data in the first place.
Dan T
On Feb 16, 2005, at 10:57 AM, Michael Stassen wrote
Dan Tappin wrote:
I have MySQL 4.1.8 installed on OS X 10.3.8 Server and I was in the
process of building a PHP / MySQL website. After numerous connection
issues with the MySQL server I decided to take a look at the status of
my tables to check for corruption.
After running myisamchk I managed
#x27;" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Tuesday, November 18, 2003 2:51 PM
Subject: RE: table crash (error127) using v4.0.15 & JDBC
> Are the crashes occurring on the same machines? Or random machines? Can
you
> track the disk activity at the time the ta
Are the crashes occurring on the same machines? Or random machines? Can you
track the disk activity at the time the table is being marked as corrupt?
Are you tracking the database activity?
-Original Message-
From: fabien marsaud [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 18, 2003 5
- Original Message -
From: "Martin Mokrejs" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Friday, April 05, 2002 10:41 PM
Subject: Table crash!
> Don't do this when the table is in the cache!
>
> The correct way (open two xterms and do commands in this order):
>
