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.
Created attachment 1985232[details]
xfsdump archive produced using xfsdump-3.1.4-1.el7 with a bind mount
Description of problem:
xfsdump/xfsrestore: suggest recovery for false roots may be possible using -x
Description of problem:
Some versions of xfsdump may produce archives that cannot be restored correctly
problems with bind mounts identified in Bug 1698057, a fix to restore these
archives was made in Bug 2034327.
This fix uses a new option `-x` to allow archives to be restored, unfortunately
for the case where an archive causes xfsrestore to fail with an assert there's
no direction given to the user that recovery may be possible.
Version-Release number of selected component (if applicable):
xfsdump-3.1.10-1.el9.x86_64
Steps to Reproduce:
Using the xfsdump attached to the bz
mkdir /tmp/test
xfsrestore -f bind_mount-xfsdump-3.1.4-1.el7.x86_64.dump /tmp/test
Actual results:
xfsrestore: using file dump (drive_simple) strategy
xfsrestore: version 3.1.10 (dump format 3.0) - type ^C for status and control
xfsrestore: searching media for dump
xfsrestore: examining media file 0
xfsrestore: dump description:
xfsrestore: hostname: rhel-7_2
xfsrestore: mount point: /mnt2
xfsrestore: volume: /dev/loop0
xfsrestore: session time: Sat Mar 12 11:36:41 2022
xfsrestore: level: 0
xfsrestore: session label: "bind mount"
xfsrestore: media label: "test"
xfsrestore: file system id: 9327a140-79c1-4c02-9478-7f699c562409
xfsrestore: session id: 7e3f9f99-928c-40fe-ae65-93ba72387b1e
xfsrestore: media id: d486cf35-b15c-480c-885d-20d7fe755a7d
xfsrestore: searching media for directory dump
xfsrestore: reading directories
xfsrestore: tree.c:757: tree_begindir: Assertion `ino != persp->p_rootino || hardh == persp->p_rooth' failed.
Aborted (core dumped)
Expected results:
xfsrestore: ERROR: tree.c:791: tree_begindir: Assertion `ino != persp->p_rootino || hardh == persp->p_rooth` failed.
xfsrestore: ERROR: False root detected. Recovery may be possible using the `-x` option
Aborted
Additional info:
Upstream: https://lore.kernel.org/linux-xfs/20230824020704.1893521-1-ddouwsma@redhat.com
Comment 1RHEL Program Management
2023-09-23 12:05:09 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 2RHEL Program Management
2023-09-23 12:07:05 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.