This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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.
Bug 2207726 - Unable to boot if /boot is xfs filesystem with extent hole
Summary: Unable to boot if /boot is xfs filesystem with extent hole
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: grub2
Version: 8.7
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Bootloader engineering team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-05-16 16:14 UTC by Frank Sorenson
Modified: 2023-09-16 19:10 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-16 19:10:25 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-4387 0 None Migrated None 2023-09-16 19:08:09 UTC
Red Hat Issue Tracker RHELPLAN-157402 0 None None None 2023-05-16 16:18:13 UTC

Description Frank Sorenson 2023-05-16 16:14:28 UTC 
Description of problem:

If /boot is on an xfs filesystem, and the directory contains a hole in the extent allocation, booting fails with "error: not a correct xfs inode"

Version-Release number of selected component (if applicable):

2.02-142.el8_7.3.x86_64


How reproducible:

should be very easy


Steps to Reproduce:

1) have older kernel installed
2) create several hundred files with long names in /boot:

    # for i in {001..300} ; do
        touch /boot/filler_filename____________________________________${i}
      done

3) install new kernel version rpms
4) remove the filler files:

    # rm -f /boot/filler_filename*

5) verify that /boot has a hole:

    # xfs_bmap /boot
    boot:
	0: [0..7]: 748422104..748422111
	1: [8..15]: hole
	2: [16..23]: 748422080..748422087

6) reboot


Actual results:

booting fails with "error: not a correct xfs inode"


Expected results:

booting succeeds


Additional info:

bug also affects RHEL 7, but is fixed in RHEL 9
Comment 3 Marta Lewandowska 2023-05-23 09:27:04 UTC 
Reproduced using 2.02-142.el8_7.3.x86_64. (wasn't actually that easy to get the hole; I had to try it a few times on different machines)

This patch is included in the latest RHEL-8 grub-- 2.02-148.el8-- and therefore in released 8.8. Is this alright for you / the customer or does this need to be backported into specific release(s)? Notably, 8.7.z is already EOL so that patch won't make it there.
Comment 4 Marta Lewandowska 2023-05-23 11:49:43 UTC 
Actually, the patch should be in grub2-2.02-123.el8_6.15 (most recent RHEL-8.6 grub) as well.
Comment 7 raravind 2023-07-06 10:50:08 UTC 
Marta, I think the patch mentioned in comment#1 is not included in any of the RHEL 8's.I recently checked 8.8 and 8.9 grub(grub2-2.02-148.el8 | grub2-2.02-150.el8) and couldn't find there.However it is included in RHEL 9.I couldn't reproduce the error in recent RHEL 9.3.
Comment 9 Marta Lewandowska 2023-07-19 13:41:25 UTC 
Reshmi's totally right in comment#7... not sure what I was seeing before..!

Ok, so that means we have a patch and we can do SanityOnly testing since it's difficult to reproduce.
Comment 10 Marta Lewandowska 2023-07-19 18:42:10 UTC 
Today's a rough day for me! ;)
I have to take back what's in comment#9... I downloaded the src rpm, looked for the patch (xfs: Don't attempt to iterate over empty directory) and didn't find it, but then forgot to apply patches before looking at the code itself. Seems I knew to do this correctly in the past!
Turns out (+1 to nfrayer!) that it's in release-to-master.patch
So now, also after more info from Nicolas, we think this patch is not enough to fix this issue, especially since it's not very reproducible...
Comment 12 RHEL Program Management 2023-09-16 19:05:11 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 13 RHEL Program Management 2023-09-16 19:10:25 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.
Note You need to log in before you can comment on or make changes to this bug.