[Lilug] MySQL crash and burn (corruption) and trying to recover innodb

[dotCOMmie (Ilya S.)]

On 06/16/2010 05:05 PM, Mike A. Leonetti wrote:
> The MySQL database became corrupt after an unexpected power off. The
> backups are impossible, and all I have to work with is the 39 GB
> database. MySQL is always crashing in the same spot when I tried to
> export with innodb_force_recovery with the values of 4 to 6. I then
> tried using both the google innodb-tools and the innoinfo by Steve
> Hardy. The innodb-tools doesn't really export much and the innodbinfo
> utility gives me:
>
>...

You know, I'm not appreciating this. Your luck just rubbed of on me! d:

Basically same thing server lost power and DB wouldn't start with similar output
but not exactly the same.Innodb_force_recovery only started with 6, was able to
dump the data with dumpsql --all-databases and importing now. We'll see how much
of the data is retained. Granted I only really care about a <1MB table out of
1.5GB dump so I think I'll be OK.

Lesson: 15 min to setup a backup can save you 1/2 a day if not more.

Have you made any progress with your database?

regards.

-- 
dotCOMmie

That's easy to fix, but I can't be bothered.