Cause: File contained more magic patterns to detect output of "dump" backup tool.
Consequence: On big-endian architectures, less detailed magic pattern was used and the File output was inconsistent.
Fix: Less detailed magic pattern has been removed and only one magic pattern to detect "dump" output is used now.
Result: File uses more detailed magic pattern every time even on big-endian architectures.
Description of problem:
On RHEL6 there are differences between platforms how the dump file is recognized.
on x86_64, i386 e.g.
backup: new-fs dump file (little endian), This dump Sat Sep 22 21:00:54 2012, Previous dump Wed Dec 31 19:00:00 1969, Volume 1, Level zero, type: tape header, Label myext3fs, Filesystem /mnt/myext3fs, Device /dev/loop0, Host any.host.org, Flags 3
backup: dump format, 4.2 or 4.3 BSD without IDC
Version-Release number of selected component (if applicable):
execute file against the dump file created by dump command
Upstream bug report: http://bugs.gw.com/view.php?id=204
Created attachment 616434 [details]
This patch removes duplicated magic pattern and keeps the one which provides more detailed information about dumps.
Can you please attach backup file (or first 4096 bytes) for which it's broken (big endian version) so upstream can verify the fix?
Created attachment 616457 [details]
dump from a big endian system
attached big endian dump sample
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.