Bookmarks

Yahoo Gmail Google Facebook Delicious Twitter Reddit Stumpleupon Myspace Digg

Search queries

/proc/kallsyms format, sqldatasource dal, wwwxxxenden, convert raid5 to raid 10 mdadm, apache force chunked, nrao wwwxxx, xxxxxdup, procmail change subject header, wwwXxx not20, Wwwxxx.doks sas

Links

XODOX
Impressum

#1: Databasename/Tablename is marked as crashed and should be repaired

Posted on 2011-10-14 09:07:12 by James Corteciano

--20cf30780e5c0e6fa904af3ce886
Content-Type: text/plain; charset=ISO-8859-1

Hello,

I have the following error on my mysql server log and managed to repaired
the broken table. However, it keeps occurring by time to time. I am using
MyISAM storage engine to all database and having some locking table which I
know / aware about the disadvantage of MyISAM.

'./Databasename/Tablename' is marked as crashed and should be repaired

Are there any ways to solved permanently? Any advise would be appreciated.

Thank you.

James

--20cf30780e5c0e6fa904af3ce886--

Report this message

#2: Re: Databasename/Tablename is marked as crashed and should be repaired

Posted on 2011-10-14 09:30:05 by Mark Goodge

On 14/10/2011 08:07, James wrote:
> Hello,
>
> I have the following error on my mysql server log and managed to repaired
> the broken table. However, it keeps occurring by time to time. I am using
> MyISAM storage engine to all database and having some locking table which I
> know / aware about the disadvantage of MyISAM.
>
> './Databasename/Tablename' is marked as crashed and should be repaired
>
> Are there any ways to solved permanently? Any advise would be appreciated.

If it's happening repeatedly, and the MySQL server itself is running
without any problems (ie, it isn't crashing and restarting) then you may
have problems with the hardware - with the disk itself.

Mark
--
Sent from my Babbage Difference Engine
http://mark.goodge.co.uk
http://www.ratemysupermarket.com

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=gcdmg-mysql-2@m.gmane.org

Report this message

#3: Re: Databasename/Tablename is marked as crashed and should be repaired

Posted on 2011-10-14 10:22:21 by sureshkumarilu

--20cf30434f54c2398604af3df434
Content-Type: text/plain; charset=ISO-8859-1

Hi,

The permanent solution is to convert the table into Innodb engine.

Thanks
Suresh Kuna

On Fri, Oct 14, 2011 at 1:00 PM, Mark Goodge <mark@good-stuff.co.uk> wrote:

> On 14/10/2011 08:07, James wrote:
>
>> Hello,
>>
>> I have the following error on my mysql server log and managed to repaired
>> the broken table. However, it keeps occurring by time to time. I am using
>> MyISAM storage engine to all database and having some locking table which
>> I
>> know / aware about the disadvantage of MyISAM.
>>
>> './Databasename/Tablename' is marked as crashed and should be repaired
>>
>> Are there any ways to solved permanently? Any advise would be appreciated.
>>
>
> If it's happening repeatedly, and the MySQL server itself is running
> without any problems (ie, it isn't crashing and restarting) then you may
> have problems with the hardware - with the disk itself.
>
> Mark
> --
> Sent from my Babbage Difference Engine
> http://mark.goodge.co.uk
> http://www.ratemysupermarket.**com <http://www.ratemysupermarket.com>
>
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe: http://lists.mysql.com/mysql?**
> unsub=sureshkumarilu@gmail.com<http://lists.mysql.com/mysql?unsub=sureshkumarilu@gmail.com>
>
>


--
Thanks
Suresh Kuna
MySQL DBA

--20cf30434f54c2398604af3df434--

Report this message

#4: Re: Databasename/Tablename is marked as crashed and should be repaired

Posted on 2011-10-14 10:40:58 by Johan De Meersman

----- Original Message -----
> From: "Suresh Kuna" <sureshkumarilu@gmail.com>
>
> The permanent solution is to convert the table into Innodb engine.

Wonderful advice, especially without even bothering to try and find out what is actually causing the corruption. Well done, that man. You *are* aware that not all tables can be converted to InnoDB? Full text indices come to mind, for one.


One way of establishing wether or not the table is on a bad block (it probably isn't, or you'd see something in the syslog) would be to ensure it goes on a completely different set of blocks: create an identical table with a different name, copy the contents with insert as select, and then swap out the tables using alter table rename. The "old" table will remain on the blocks it is, and the new one will have all the content on "fresh" blocks.

Note that a repair table is also very likely to already have copied the entire table using roughly the same process, so that's probably not it; but it may be worth a shot anyway.



--
Bier met grenadyn
Is als mosterd by den wyn
Sy die't drinkt, is eene kwezel
Hy die't drinkt, is ras een ezel

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=gcdmg-mysql-2@m.gmane.org

Report this message