When a page is corrupted scan stops at supremum record

Bug #518600 reported by Aleksandr Kuzminsky
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Data Recovery Tool for InnoDB
Fix Released
Critical
Aleksandr Kuzminsky

Bug Description

When scanning a corrupted pages initial offset is 100 + record_extra_bytes (5 or 6).
Eventualy the scan stops when ORIGIN points to supremum record.

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.