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.

Regards


---------------------------------------------------------------
********** _/     **********  David Logan 
*******   _/         *******  ITO Delivery Specialist - Database
*****    _/            *****  Hewlett-Packard Australia Ltd
****    _/_/_/  _/_/_/  ****  E-Mail: [EMAIL PROTECTED]
****   _/  _/  _/  _/   ****  Desk:   +618 8408 4273
****  _/  _/  _/_/_/    ****  Mobile: 0417 268 665
*****        _/       ******    
******      _/      ********  Postal: 148 Frome Street,
********   _/     **********          Adelaide SA 5001
                                      Australia 
i    n    v    e    n    t                                   
---------------------------------------------------------------

-----Original Message-----
From: Dilipkumar [mailto:[EMAIL PROTECTED] 
Sent: Friday, 28 July 2006 1:07 PM
To: Dirk Bremer; mysql@lists.mysql.com
Subject: Re: Mysqlcheck issues

Hi,

Instead of mysqlcheck you can use myisamckh to recover the data's.
As myisamchk -r -o *.MY*

Thanks & Regards
Dilipkumar
----- Original Message ----- 
From: "Dirk Bremer" <[EMAIL PROTECTED]>
To: <mysql@lists.mysql.com>
Sent: Thursday, July 27, 2006 8:32 PM
Subject: Mysqlcheck issues



I am using MySQL server 4.1.10 on Windows 2003 Server with MyISAM
tables. I have an issue where occasionally an index (MYI) file becomes
corrupted. I do not know why this occurs. To combat this issue, I tried
running the following command every half-hour:

mysqlcheck -Aamov --auto-repair --use-frm

This command runs on the host. For some reason, when this command
executes, the MySQL service aborts and the MYI for the main table is
corrupted. I must then restart the service and repair the affected
table.

I am at a loss here. I would really like to use the --auto-repair
option, but don't understand what is causing the service to abort.

Your thoughts?

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]

********** DISCLAIMER **********
Information contained and transmitted by this E-MAIL is proprietary to 
Sify Limited and is intended for use only by the individual or entity to

which it is addressed, and may contain information that is privileged, 
confidential or exempt from disclosure under applicable law. If this is
a 
forwarded message, the content of this E-MAIL may not have been sent
with 
the authority of the Company. If you are not the intended recipient, an 
agent of the intended recipient or a  person responsible for delivering
the 
information to the named recipient,  you are notified that any use, 
distribution, transmission, printing, copying or dissemination of this 
information in any way or in any manner is strictly prohibited. If you
have 
received this communication in error, please delete this mail & notify
us 
immediately at [EMAIL PROTECTED]


Watch the latest updates on Mumbai, with video coverage of news, events,
Bollywood, live darshan from Siddhivinayak temple and more, only on
www.mumbailive.in

Watch the hottest videos from Bollywood, Fashion, News and more only on
www.sifymax.com


-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]

Reply via email to