Percona Data Recovery Tool for InnoDB

innochecksum is unusable and dangerous

Reported by Andrew Gaul on 2012-08-06
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Data Recovery Tool for InnoDB
High
Aleksandr Kuzminsky

Bug Description

innochecksum has three significant bugs: spuriously writing to FIL_PAGE_LSN, calculating the old- and new-style checksums in the wrong order, and smashing adjacent fields on x86-64. The program is unusable and dangerous as-is. I submitted fixes to all symptoms:

https://code.launchpad.net/~gaul/percona-data-recovery-tool-for-innodb/do-not-write-lsn
https://code.launchpad.net/~gaul/percona-data-recovery-tool-for-innodb/calculate-new-checksum-first
https://code.launchpad.net/~gaul/percona-data-recovery-tool-for-innodb/fixed-width-checksum

Changed in percona-data-recovery-tool-for-innodb:
importance: Undecided → High
assignee: nobody → Aleksandr Kuzminsky (akuzminsky)
Changed in percona-data-recovery-tool-for-innodb:
status: New → Fix Committed
milestone: none → release-0.6
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers