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.
Description of problem:
e2fsck fails to check an ext4 file system with 64bit feature enabled.
$ sudo e2fsck /home/fs.img
e2fsck 1.41.12 (17-May-2010)
/home/fs.img has unsupported feature(s): 64bit
e2fsck: Get a newer version of e2fsck!
This happened to me when I tried to mount an ext4 file system during boot on RHEL6. The file system has been created on RHEL7 (which enables the 64bit feature by default). The booting process failed due to e2fsck being unable to check the file system.
Version-Release number of selected component (if applicable):
e2fsprogs-1.41.12-18.el6.x86_64
How reproducible:
Always
Steps to Reproduce:
1. create an ext4 file system with 64bit feature enabled (using newer version of e2fsprogs - e.g. from RHEL7)
2. run e2fsck on the created file system
Actual results:
e2fsck prints out an error message of unsupported feature and quits
Expected results:
e2fsck checks the file system for errors
Additional info:
Mounting the file system works fine. The only problem is with e2fsprogs which are probably too old to handle the 64bit feature. This is particularly inconvenient when the whole booting process fails due to e2fsck being unable to check the file system.
> Steps to Reproduce:
> 1. create an ext4 file system with 64bit feature enabled (using newer version of e2fsprogs - e.g. from RHEL7)
That's not a supported thing to do.
We cannot make all old releases support all new features; you broke it and you get to keep both pieces.
(However, mounting w/ an unsupported feature is odd, let me look into that)
Allowing a mount w/ that feature seems like some ext4-derp; I wouldn't recommend continuing with that filesystem under RHEL6, it's not something that is tested. At all.
-Eric