[debian-mysql] Bug#682232: #682232

[Antti-Juhani Kaijanaho]

On Mon, Jul 23, 2012 at 02:34:45PM +0100, Nicholas Bamber wrote:
> 	Since you have managed to recover I feel fully justified in downgrading
> to important.

Agreed.  It doesn't look like this would hit upgrades regularly.

> 	Since innodb became the default storage engine in version 5.5 , one
> possible theory that occurs to me is that the following happened:
> 
> 1.) There had been in the past some temporary experiment with innodb.
> 2.) After that experiment some innodb files lay lying around.
> 3.) During the upgrade these old innodb files got in the way.
> 
> If you think that might have happened, that might give us some scenarios
> from which we could try to get a reproducible bug.

It's not impossible but I can't say whether it's so or not.

> If you still have the old innodb files, I believe there are some tools
> for reading them which might be interesting.

Yes, I have the tarball I made before recovering.  I have also set up a wheezy
VM in the broken state

> Lastly I suppose you could try the following:
> 1.) Install mysql-5.1 in a clean squeeze environment.
> 2.) import a logical dump of your database.
> 3.) upgrade to 5.5.
> If that reproduces the error then I think we'd be onto something.

By logical dump, what do you mean here?  mysqldump?

-- 
Antti-Juhani Kaijanaho, Jyväskylä, Finland
http://antti-juhani.kaijanaho.fi/newblog/
http://www.flickr.com/photos/antti-juhani/