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.

Created attachment 523092 [details]
testcase for the bug

This is mainstream bug.
it happens during migration inode from ind-layout to extent one
chattr +e ./a_file and result in massive data corruption.
Patch already available: http://patchwork.ozlabs.org/patch/93790/
and it is applicable to 2.6.32.131 as is.
Test case attached.

Since RHEL 6.2 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.

Just a note - we do not support ext3->ext4 migration in RHEL (as is probably obvious by the fact that this stuff is so broken).

Migration paths are rarely run or tested, and never run or tested by our internal QE.  Migration gets you half-an-ext4, without all of the improved metadata layout you gain at mkfs time.  Our only supported usecase for ext4 is a fresh mkfs.

Since this is simple & obvious, we could consider fixing it to avoid corruption for people who try it anyway, but I don't want to leave the impression that this is a supported/maintained use case.

Since migration isn't supported in RHEL, I'm just going to WONTFIX this one.

Thanks for the report,
-Eric