Issued:

2011-12-06

Updated:

2011-12-06

RHBA-2011:1735 - e2fsprogs bug fix and enhancement update

Synopsis

e2fsprogs bug fix and enhancement update

Type/Severity

Bug Fix Advisory (none)

Topic

Updated e2fsprogs packages that fix several bugs and add two enhancements are now available for Red Hat Enterprise Linux 6.

Description

The e2fsprogs packages contain a number of utilities that create, check, modify, and correct inconsistencies in ext2, ext3, and ext4 file systems. This includes e2fsck (which repairs file system inconsistencies after an unclean shutdown), mke2fs (which initializes a partition to contain an empty file system), tune2fs (which modifies file system parameters), and most of the other core file system utilities.

This update fixes the following bugs:

• Running the "e2fsck" command on certain corrupted file systems failed to correct all errors during the first run. This occurred when a file had its xattr block cloned as a duplicate, but the block was later removed from the file because the file system did not contain the xattr feature. However, the block was not cleared from the block bitmaps. During the second run, e2fsck found the cloned xattr block as in use, but not owned by any file, and had to repair the block bitmaps. With this update, the processing of duplicate xattr blocks is skipped on non-xattr file systems. All problems are now discovered during the first run. (BZ#676465)

• On certain devices with very large physical sector size, the mke2fs utility set the block size to be as large as the size of the physical sector. In some cases, the size of the physical sector was larger than the page size. As a consequence, the file system could not be mounted and, in rare cases, the utility could even fail. With this update, the default block size is not set to be larger than the system's page size, even for large physical sector devices. (BZ#679931)

• Previously, multiple manual pages contained typos. These typos have been corrected with this update. (BZ#683906)

• This update modifies parameters of the "mke2fs" command to be consistent with the "discard" and "nodiscard" mount options for all system tools (like mount, fsck, or mkfs). The user is now also informed about the ongoing discard process. (BZ#713475)

• Previously, the libcomm_err libraries were built without the read-only relocation (RELRO) flag. Programs built against these libraries could be vulnerable to various attacks based on overwriting the ELF section of a program. To enhance the security, the e2fsprogs package is now provided with partial RELRO support. (BZ#730083)

This update also adds the following enhancements:

• Previously, the tune2fs tool could not set "barrier=0" as the default option on the ext3 and ext4 file systems. With this update, users are now able to set this option when creating the file system, and do not have to maintain the option in the /etc/fstab file across all of the file systems and servers. (BZ#679892)

• Previously, raw e2image output files could be extremely large sparse files, which were difficult to copy, archive, and transport. This update adds support for exporting images in the qcow format. Images in this format are small and easy to manipulate. (BZ#713468)

Users are advised to upgrade to these updated e2fsprogs packages, which fix these bugs and add these enhancements.

Solution

Before applying this update, make sure all previously-released errata relevant to your system have been applied.

This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at This content is not included.https://access.redhat.com/kb/docs/DOC-11259

Affected Products

Updated Packages

• e2fsprogs-libs-1.41.12-11.el6.i686.rpm
• libss-1.41.12-11.el6.ppc64.rpm
• libss-1.41.12-11.el6.s390.rpm
• libcom_err-1.41.12-11.el6.s390x.rpm
• libcom_err-1.41.12-11.el6.i686.rpm
• libcom_err-devel-1.41.12-11.el6.x86_64.rpm
• e2fsprogs-libs-1.41.12-11.el6.ppc64.rpm
• e2fsprogs-debuginfo-1.41.12-11.el6.i686.rpm
• e2fsprogs-devel-1.41.12-11.el6.i686.rpm
• e2fsprogs-debuginfo-1.41.12-11.el6.x86_64.rpm
• e2fsprogs-1.41.12-11.el6.ppc64.rpm
• libss-devel-1.41.12-11.el6.ppc.rpm
• libss-devel-1.41.12-11.el6.s390x.rpm
• libss-1.41.12-11.el6.i686.rpm
• libcom_err-devel-1.41.12-11.el6.ppc.rpm
• libss-1.41.12-11.el6.ppc.rpm
• libss-devel-1.41.12-11.el6.s390.rpm
• libcom_err-1.41.12-11.el6.ppc.rpm
• e2fsprogs-libs-1.41.12-11.el6.s390.rpm
• e2fsprogs-devel-1.41.12-11.el6.x86_64.rpm
• libcom_err-1.41.12-11.el6.s390.rpm
• libss-devel-1.41.12-11.el6.i686.rpm
• e2fsprogs-devel-1.41.12-11.el6.s390.rpm
• libcom_err-devel-1.41.12-11.el6.s390x.rpm
• e2fsprogs-devel-1.41.12-11.el6.s390x.rpm
• e2fsprogs-1.41.12-11.el6.i686.rpm
• e2fsprogs-libs-1.41.12-11.el6.x86_64.rpm
• libss-devel-1.41.12-11.el6.ppc64.rpm
• e2fsprogs-debuginfo-1.41.12-11.el6.ppc.rpm
• e2fsprogs-debuginfo-1.41.12-11.el6.s390.rpm
• e2fsprogs-libs-1.41.12-11.el6.ppc.rpm
• e2fsprogs-devel-1.41.12-11.el6.ppc64.rpm
• e2fsprogs-1.41.12-11.el6.s390x.rpm
• e2fsprogs-1.41.12-11.el6.src.rpm
• e2fsprogs-debuginfo-1.41.12-11.el6.s390x.rpm
• libss-devel-1.41.12-11.el6.x86_64.rpm
• libcom_err-devel-1.41.12-11.el6.s390.rpm
• libcom_err-devel-1.41.12-11.el6.ppc64.rpm
• libcom_err-devel-1.41.12-11.el6.i686.rpm
• libcom_err-1.41.12-11.el6.x86_64.rpm
• e2fsprogs-1.41.12-11.el6.x86_64.rpm
• e2fsprogs-debuginfo-1.41.12-11.el6.ppc64.rpm
• libss-1.41.12-11.el6.s390x.rpm
• e2fsprogs-devel-1.41.12-11.el6.ppc.rpm
• e2fsprogs-libs-1.41.12-11.el6.s390x.rpm
• libss-1.41.12-11.el6.x86_64.rpm
• libcom_err-1.41.12-11.el6.ppc64.rpm

Fixes

• This content is not included.BZ - 676465
• This content is not included.BZ - 679931
• This content is not included.BZ - 683906
• This content is not included.BZ - 713468
• This content is not included.BZ - 713475
• This content is not included.BZ - 730083
• This content is not included.BZ - 732940

CVEs

(none)

References

(none)

Additional information

• The Red Hat security contact is This content is not included.secalert@redhat.com. More contact details at https://access.redhat.com/security/team/contact/.
• Offline Security Data data is available for integration with other systems. See Offline Security Data API to get started.