5.5.20 - dropping/altering table causes crash if corrupt undo page exists

[Shane Boone]

Percona 5.5.20-rel24.1.217, RHEL5 64
file-per-table

Server crashes when dropping or altering any table after upgrading to 5.5. Does not crash in 5.1.

error.log:
---
InnoDB: Page directory corruption: infimum not pointed to
120516 14:09:06 InnoDB: Page dump in ascii and hex (16384 bytes):
...
InnoDB: Page may be an update undo log page
InnoDB: Page directory corruption: supremum not pointed to
120516 14:09:06 InnoDB: Page dump in ascii and hex (16384 bytes):
---

Reference Percona Issue #23346

[yinfeng (yinfeng-zwx)]

We encounter this bug recently while adding a column to a small table with only 486 rows.
but this bug is hard to repeat
Can you provide some test case?

thank you! :)

[yinfeng (yinfeng-zwx)]

we had done same operation on master and slave, and both were crashed...

[Laurynas Biveinis (laurynas-biveinis)]

There is bug 978036 with the same symptoms. It was fixed in Percona Server 5.5.23 release. Please test with that or newer version and let us know if you still experience the issue or not. Thanks!

[yinfeng (yinfeng-zwx)]

thank you!
 we had a backup restored from mysql5.1.48. while using Percona Server 5.5.18 and altering the same table always crash the server. while using Percona Server 5.5.23 or straightforwardly backport the patch to Percona Server 5.5.18, everthing works well.

while it's very hard for us to ungrade from 5.5.18 to 5.5.23, another question is : can we backport the patch straightforwardly to Percona Server5.5.18?

[Laurynas Biveinis (laurynas-biveinis)]

Yes, the patch backport should be more or less straightforward. If you wish to add bug 978036 fix to Percona Server 5.5.18, the easiest way is to download Percona Server 5.5.18 source tarball and apply a patch at https://bazaar.launchpad.net/~laurynas-biveinis/percona-server/bug978036-5.5/revision/237