<[EMAIL PROTECTED]> wrote:
Sorry it is */*.MYI instead of */*.MYD
> -Original Message-
> From: Gregory Machin [mailto:[EMAIL PROTECTED]
> Sent: Thursday, March 22, 2007 12:02 PM
> To: Jean-Sebastien Pilon
> Cc: mysql@lists.mysql.com
> Subject: Re: database corruption ? h
Sorry it is */*.MYI instead of */*.MYD
> -Original Message-
> From: Gregory Machin [mailto:[EMAIL PROTECTED]
> Sent: Thursday, March 22, 2007 12:02 PM
> To: Jean-Sebastien Pilon
> Cc: mysql@lists.mysql.com
> Subject: Re: database corruption ? how to fix ?
>
>
it gives
the following errors for all the databases ..
myisamchk: error: './diaendomet/users.MYD' is not a MyISAM-table
myisamchk: error: './diaendomet/users.MYD' is not a MyISAM-table
phpmyadmin reports the tables as being MyISAM..
any sugetions
On 3/22/07, Jean-Sebastien Pilon <[EMAIL PROTEC
- Stop you mysql server
- change working directory to $MYSQL_DATA_DIR
- run myisamchck with */*.MYD
This will run a check on all your table files
> -Original Message-
> From: Gregory Machin [mailto:[EMAIL PROTECTED]
> Sent: Thursday, March 22, 2007 8:41 AM
> To: mysql@lists.mysql.com
To restore specific tables (or full databases) I often use this trick (I'm
just writing this down from memory, you would want to run it through a
test environment first). It runs something like this:
1) MASTER: query> FLUSH TABLES WITH READ LOCK;
query> SHOW MASTER STATUS\G
2) SLAVE:
Yes thats very true, as the corrupt slave would pick up from where it left
and its quite posssible that the record was already updated on the healthy
slave from the master, causing the replication to fail, but having said that
may be you could do this
1) stop the healthy slave
2) put a global read
Hi Kishore,
That's an interesting idea. However, given that the healthy slave
and the corrupt slave now have different values for
Exec_Master_Log_Pos, would restoring the tables from the healthy
slave necessarily be a good move?
I would be worried that the corrupt slave's counter positio
an "rsync" with the right options from the unaffected slave to the corrupt
one might prove to be an elegant technique
Kishore Jalleda
On 3/7/06, Michael Jeung <[EMAIL PROTECTED]> wrote:
>
> Hi Folks,
>
> We've got a Single Master/Multiple Slave environment.
> Recently, we had some corruption on o
> Sent: Thursday, 25 September 2003 2:05 p.m.
> To: [EMAIL PROTECTED]
> Subject: Re: Database corruption
>
>
> We had the same problem when running on linux with the 2.4.18
> kernel. Upgraded to the 2.4.20 and no problems since.
>
> Don't know if that's your
We had the same problem when running on linux with the 2.4.18 kernel.
Upgraded to the 2.4.20 and no problems since.
Don't know if that's your problem, since you didnt mention kernel versions.
Cheers
Terence
- Original Message -
From: "Quentin Bennett" <[EMAIL PROTECTED]>
To: <[EMAIL PRO
10 matches
Mail list logo
