recovering crashed large (139M+ row) MyISAM table
Posted by:
Tim Park
Date: April 15, 2009 09:50PM
A server I am using MySql on had a power outage and a very large MyISAM table that I have was marked crashed by MySQL.
I am currently using myiasmchk -r -q on the table but it has literally been running now for 36 hours nonstop without finishing.
Is there a faster process to do this? Is there a way to make a copy of the table, mark it uncrashed, and see if it is ok? Are there any plans to add spatial extensions to InnoDB (or any of the other transactional FS) so we can avoid this totally crazy recovery time?
Or more generally, how does anyone run in production with MyISAM with big tables and avoid this?
Thanks,
Tim
Subject
Views
Written By
Posted
recovering crashed large (139M+ row) MyISAM table
4468
April 15, 2009 09:50PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.