[debian-mysql] Bug#682232: #682232

Nicholas Bamber nicholas at periapt.co.uk
Mon Jul 23 13:34:45 UTC 2012


severity 682232 important
thanks

Antti-Juhani,
	Thanks for your cooperation.

	Since you have managed to recover I feel fully justified in downgrading
to important. The information you have sent from the logs is very good,
but so far no different from any other innodb corruption.

	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.

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

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.

Sorry but I've run out of ideas for now.



More information about the pkg-mysql-maint mailing list