Hide Forgot
Description of problem: dump -0 -f - srcdir | restore -oax -f - drops leading blocks of zero-bytes and reports "Missing blocks at end of <path>, assuming hole". Version-Release number of selected component (if applicable): dump-0.4-0.5.b42.el6 How reproducible: always Steps to Reproduce: 1. dump -0 -f - srcdir | restore -oax -f - 2. 3. Actual results: It reports "Missing blocks at end of <path>, assuming hole" Expected results: No error Additional info: The bug is fixed in upstream: http://sourceforge.net/tracker/index.php?func=detail&aid=3133762&group_id=1306&atid=101306
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. If you would like it considered as an exception in the current release, please ask your support representative.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Under certain circumstances, the dump utility could have failed to detect holes in files correctly. When a user attempted to restore an erroneous backup using the "restore" command, an error message "Missing blocks at end of [path], assuming hole" could have been displayed. In such case, the backup could have not been restored properly. This bug has been fixed in this update so that dump now handles holes in files as expected.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2011-1095.html