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 220.127.116.11 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,