Bug#682232: #682232

2012-07-23 Thread Nicholas Bamber
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.

Bug#682232: #682232

2012-07-23 Thread 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 ,

Bug#682232: #682232

2012-07-23 Thread Nicholas Bamber
On 23/07/12 14:47, Antti-Juhani Kaijanaho wrote: 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 I was thinking of this: