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.
Deleting the lost+found directory on a file system with inodes of size greater than 128 bytes and reusing inode 11 for a different file caused the extended attributes for inode 11 (which were set before a umount operation) to not be saved after a file system remount. As a result, the extended attributes were lost after the remount. With this update, inodes store their extended attributes under all circumstances.
Created attachment 468399[details]
patch for RHEL 6
Description of problem:
In ext3 filesystem, if following conditions 1., 2., 3. and 4. are satisfied,
we cannot find the extended attribute (EA) after remount.
Condition:
1. the inode size is over 128 bytes
2. "lost+found" whose inode number is 11 was removed
3. the #11 inode is created as a file.
4. the EA of #11 inode locates in-inode
This happens because of the following logic:
i_extra_isize (member of ext3_inode structure) is set to over 0 by ext3_new_inode()
when we create a file whose inode number is 11 after removing "lost+found".
Therefore setfattr creates the EA of #11 inode in-inode.
After remount, i_extra_isize of #11 inode is set to 0 by ext3_iget()
when we lookup the file, so getfattr tries to search the EA only out-inode.
However, the EA locates in-inode, so getfattr can't find the EA.
This problem is fixed in the upstream kernel. The patch is http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=beb37b85b0b727e68e16a39a1e5a2140f87fa201.
Patch for RHEL6.0 is attached.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
Deleting the lost+found directory on a file system with inodes of size greater than 128 bytes and reusing inode 11 for a different file caused the extended attributes for inode 11 (which were set before a umount operation) to not be saved after a file system remount. As a result, the extended attributes were lost after the remount. With this update, inodes store their extended attributes under all circumstances.
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/RHSA-2011-1530.html