> -----Original Message----- > From: Logan, David (SST - Adelaide) [mailto:[EMAIL PROTECTED] > Sent: Thursday, July 27, 2006 22:40 > To: Dilipkumar; Dirk Bremer; mysql@lists.mysql.com > Subject: RE: Mysqlcheck issues > > The trouble with myisamchk is that it requires the server to > be offline. > This may not be suitable. Do you have a bad area on the disk? The > easiest way would be to stop the server briefly, rename the index thus > keeping it occupying the potentially bad part of the disk and recreate > the index. > > This would at least take the disk out of the equation if the problem > re-occurs.
There are reasons that I doubt this is a disk problem. That being said, I will try your advice the next time the index goes bad. Dirk Bremer - Senior Systems Engineer - ESS/AMS - NISC Lake St. Louis MO - USA Central Time Zone 636-755-2652 fax 636-755-2503 [EMAIL PROTECTED] www.nisc.coop -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
