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.
From the XFS list:
> Just a heads-up: GRUB currently doesn't work on a CRC enabled
> file-system. It will print the following error message:
> "not a correct XFS inode"
This format is still WIP upstream, but we should probably have the issue on the RHEL7 radar since we plan to default to XFS even for /boot.
A simple workaround would be to not enable CRCs for the root fs; this may be done by default in any case.
So this bug may be a WONTFIX or NOTABUG, but I figured we should at least log the issue.
Thanks,
-Eric
on-disk format stuff has recently been coalesced into libxfs/xfs_format.h
http://oss.sgi.com/cgi-bin/gitweb.cgi?p=xfs/xfs.git;a=blob;f=fs/xfs/libxfs/xfs_format.h
Other than that, we maybe need to do some buddy coding to do this, as I don't think either grub2 or xfs has great up-to-date documentation...
For starters I assume grub2 could just grok new formats, but skip the actual CRC verification... things haven't changed *that* much.
-Eric
*** Bug 1220844 has been marked as a duplicate of this bug. ***
Comment 11Winfrid Tschiedel
2015-09-13 11:27:24 UTC
I have tested grub2-2.02-0.23.fc23.x86_64 installed on an Fedora 21
I succeeded in booting a CentOS 7 with XFS from the fedora boot menu,
but I still cannot boot a SLED 12 with XFS from the fedora boot menu.
Using my openSUSE 13.2 I can boot CentOS 7 and SLED 12.
If you need more information, please advise me, how to create a log from grub2.
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.
https://rhn.redhat.com/errata/RHSA-2015-2401.html
From the XFS list: > Just a heads-up: GRUB currently doesn't work on a CRC enabled > file-system. It will print the following error message: > "not a correct XFS inode" This format is still WIP upstream, but we should probably have the issue on the RHEL7 radar since we plan to default to XFS even for /boot. A simple workaround would be to not enable CRCs for the root fs; this may be done by default in any case. So this bug may be a WONTFIX or NOTABUG, but I figured we should at least log the issue. Thanks, -Eric