page_parser emits filenames that can't be sorted correctly

Bug #1068794 reported by James King
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Percona Data Recovery Tool for InnoDB
Fix Committed
Low
Unassigned

Bug Description

For non-FIL_PAGE_TYPE_BLOB pages, page_parser emits filenames in the format internalID-pageID.page. It zero pads the page ID to 8 places, but does not pad the internal ID.

The page concatenation step in the documentation (http://www.percona.com/docs/wiki/innodb-data-recovery-tool:mysql-data-recovery:extracting_the_data) recommends using the following command:

find pages-1246363747/0-286/ -type f -name '*.page' | sort -n \
   | xargs cat > pages-1246363747/0-286/customer_pages_concatenated

However, because the prefixed ID is not padded, the sort command used can result in an output file containing out or order pages.

Revision history for this message
James King (t-james-king) wrote :

The attached patch resolves the sort order issue by zero padding the prefix ID.

Changed in percona-data-recovery-tool-for-innodb:
status: New → Confirmed
importance: Undecided → Low
Changed in percona-data-recovery-tool-for-innodb:
status: Confirmed → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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