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.
Thank you for the report, I will have a look at the problem (not promising any ETA or release though because we have other reports that are more serious).
Comment 4RHEL Program Management
2023-09-21 23:35:38 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 5RHEL Program Management
2023-09-21 23:39:37 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.
Description of problem: Workflows 'mkrescue' and 'savelayout' fail when the XFS mount point contains space. Version-Release number of selected component (if applicable): rear-2.4-12.el8.x86_64 How reproducible: always Steps to Reproduce: [root@host1 ~]# lvcreate -l 256 -n lvol1 dg02 WARNING: xfs signature detected on /dev/dg02/lvol1 at offset 0. Wipe it? [y/n]: y Wiping xfs signature on /dev/dg02/lvol1. Logical volume "lvol1" created. [root@host1 ~]# mkfs.xfs /dev/dg02/lvol1 meta-data=/dev/dg02/lvol1 isize=512 agcount=4, agsize=65536 blks = sectsz=512 attr=2, projid32bit=1 = crc=1 finobt=1, sparse=1, rmapbt=0 = reflink=1 data = bsize=4096 blocks=262144, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0, ftype=1 log =internal log bsize=4096 blocks=2560, version=2 = sectsz=512 sunit=0 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 Discarding blocks...Done. [root@host1 ~]# mkdir /appl/foo\ bar [root@host1 ~]# mount /dev/dg02/lvol1 /appl/foo\ bar/ [root@host1 ~]# rear savelayout ERROR: Failed to save XFS options of /dev/mapper/dg02-lvol1 Aborting due to an error, check /var/log/rear/rear-host1.log for details Terminated Actual results: rear savelayout fails Expected results: rear savelayout succeeds Additional info: excerpt from the log file: Relax-and-Recover 2.4 / Git Command line options: /usr/sbin/rear savelayout ... Including layout/save/GNU/Linux/230_filesystem_layout.sh Begin saving filesystem layout Saving filesystem layout (using the findmnt command). Processing filesystem 'xfs' on '/dev/mapper/dg02-lvol1' mounted at '/appl/foox20bar' /appl/foox20bar: No such file or directory fatal error -- couldn't initialize XFS library ERROR: Failed to save XFS options of /dev/mapper/dg02-lvol1 ==== Stack trace ==== Trace 0: /usr/sbin/rear:547 main Trace 1: /usr/share/rear/lib/savelayout-workflow.sh:14 WORKFLOW_savelayout Trace 2: /usr/share/rear/lib/framework-functions.sh:101 SourceStage Trace 3: /usr/share/rear/lib/framework-functions.sh:49 Source Trace 4: /usr/share/rear/layout/save/GNU/Linux/230_filesystem_layout.sh:224 source Trace 5: /usr/share/rear/lib/_input-output-functions.sh:372 StopIfError Message: Failed to save XFS options of /dev/mapper/dg02-lvol1 == End stack trace ==