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.
DescriptionMonakhov Dmitriy
2014-06-23 11:55:54 UTC
Created attachment 911406[details]
Corrupted image
One of filesystems was corrupted by accident (bad raid hw, not related with current issue). As result some directory block was zeroed. And fs complains about that like follows:
[4155514.187167] EXT4-fs error (device ploop28175p1): ext4_add_entry: bad entry in directory #917395: rec_len is smaller than minimal - block=3680938offset=0(0), inode=0, rec_len=0, name_len=0
[4155514.494852] EXT4-fs error (device ploop28175p1): ext4_add_entry: bad entry in directory #917395: rec_len is smaller than minimal - block=3680938offset=0(0), inode=0, rec_len=0, name_len=0
* WHAT IS WRONG:
This is obvious corruption which should be reported and fixed by e2fsck. But e2fsck oversee that error.
* PROPOSED FIX
This is known issue which was fixed by following commmit a4fdf09414e04e9ecb995aa0af2f525d335987ae
From: Theodore Ts'o <tytso>
Date: Wed, 22 Dec 2010 13:53:02 -0500
libext2fs: Don't use the extended rec_len encoding for standard file systems
Please backport this commit to e2fsprogs package
*Original image description (orig fs size:25Gb):
**Raw e2image generated with following cmd:
e2image -r /dev/ploop22852p1 - | bzip2 > ploop22852p1.e2i.bz2
** Unpack and check how-to
# pbunzip2 -c ploop22852p1.e2i.bz2 | cp --sparse=always /dev/stdin ploop22852p1.img
# e2fsck -f ploop22852p1.img
**List of corrupted dentries:
#917395 68-69 blocks are zeroed
#928616 13'th block is corrupted
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.
http://rhn.redhat.com/errata/RHBA-2014-1566.html