Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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
on s390x:
backup: dump format, 4.2 or 4.3 BSD without IDC
Version-Release number of selected component (if applicable):
file-5.04-14.el6
How reproducible:
always
execute file against the dump file created by dump command
Created attachment 616434[details]
proposed patch
This patch removes duplicated magic pattern and keeps the one which provides more detailed information about dumps.
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.
http://rhn.redhat.com/errata/RHBA-2012-1339.html