Yes, I think you're right on that. Any idea what the cause might be or what
I can do to find out? I do have a core file, but I'm at a loss as to what to
do with it...
Original Message Follows
From: Sergei Golubchik <[EMAIL PROTECTED]>
Subject: Re: myisamchk Illegal Instr
Hi!
On Aug 07, Paul Mahon wrote:
>
> % bin/myisamchk -t ~/tmp -e BROKE/EventsBROKE
> Checking MyISAM file: BROKE/EventsBROKE
> Data records: 101333504 Deleted blocks: 86920613
> bin/myisamchk: warning: Table is marked as crashed and last repair failed
> - check file-size
> - check key delete-ch
Hello, I recently managed to corrupt a table pretty badly. I read the
sections in the documentation about recovering after a crash. None of the
methods worked. All give output similar to the following:
% bin/myisamchk -t ~/tmp -f -o BROKE/EventsBROKE
- recovering (with keycache) MyISAM-table 'BRO
Unfortunatly, I'm stuck using mysqld version 3.23.54 :(
Original Message Follows
From: Victoria Reznichenko <[EMAIL PROTECTED]>
Date: Fri, 08 Aug 2003 18:29:45 +0300
"Paul Mahon" <[EMAIL PROTECTED]> wrote:
> Hello, I recently managed to corrupt a table pretty badly. I read the
> sections i
"Paul Mahon" <[EMAIL PROTECTED]> wrote:
> Hello, I recently managed to corrupt a table pretty badly. I read the
> sections in the documentation about recovering after a crash. None of the
> methods worked. All give output similar to the following:
> % bin/myisamchk -t ~/tmp -f -o BROKE/EventsBROK
