List:General Discussion« Previous MessageNext Message »
From:praj Date:January 10 2006 5:12pm
Subject:Re: checking for corruption?
View as plain text  
Hi ,

Alternate solution : Do show table status on that database . In comment 
field you can find info about corrupted table .

This will be faster than check table .

----- Original Message ----- 
From: "N.J. Thomas" <njt@stripped>
To: <mysql@stripped>
Sent: Tuesday, January 10, 2006 9:00 PM
Subject: checking for corruption?

> After a power outage, we had a large table (~2GiB, 23e6 records) get
> corrupted. Only a few rows were actually affected, so nobody noticed for
> a few weeks though. A repair fixed the problem.
> We are now considering running the "check table" command regularly
> (every 15 minutes?) and plugging that into our monitoring system, i.e.
> if "check table" reports an error, our script beeps/emails someone.
> My question is this: is it okay to run "check table" frequently? What
> impact will it have on production systems? How quickly will it check
> very large tables? Is there an alternative (better) solution?
> thanks,
> Thomas
> -- 
> N.J. Thomas
> njt@stripped
> Etiamsi occiderit me, in ipso sperabo
> -- 
> MySQL General Mailing List
> For list archives:
> To unsubscribe:

checking for corruption?N.J. Thomas10 Jan
  • Re: checking for corruption?praj10 Jan