Issued:

2012-10-23

Updated:

2012-10-23

RHBA-2012:1399 - lvm2 bug fix update

Synopsis

lvm2 bug fix update

Type/Severity

Bug Fix Advisory

Topic

Updated lvm2 packages that fix several bugs are now available for Red Hat Enterprise Linux 6.

Description

The lvm2 packages provide support for Logical Volume Management (LVM).

This update fixes the following bugs:

• When using a physical volume (PV) that contained ignored metadata areas, an LVM command, such as pvs, could incorrectly display the PV as being orphan despite it belonged to a volume group (VG). This incorrect behavior was also dependent on the order of processing each PV in the VG. With this update, the processing of PVs in a VG has been fixed to properly account for PVs with ignored metadata areas so that the order of processing is no longer important, and LVM commands now always give the same correct result, regardless of PVs with ignored metadata areas. (BZ#843808)

• Previously, if the "issue_discards=1" configuration option was used with an LVM command, moving physical volumes using the pvmove command resulted in data loss. This update fixes the bug in pvmove and the data loss no longer occurs in the described scenario. (BZ#852438)

• When the "--alloc anywhere" command-line option was specified for the lvcreate command, an attempt to create a logical volume failed if "raid4", "raid5", or "raid6" was specified for the "--type" command-line option as well. A patch has been provided to address this bug and lvcreate now succeeds in the described scenario. (BZ#852440)

• An error in the way RAID 4/5/6 space was calculated, was preventing users from being able to increase the size of these logical volumes. This update provides a patch to fix this bug but it comes with two limitations. Firstly, a RAID 4/5/6 logical volume cannot be reduced in size yet. Secondly, users cannot extend a RAID 4/5/6 logical volume with a different stripe count than the original. (BZ#852441)

• If the "issue_discards=1" configuration option was set in the /etc/lvm/lvm.conf file, it was possible to issue a discard request to a PV that was missing in a VG. Consequently, the dmeventd, lvremove, or vgreduce utilities could terminate unexpectedly with a segmentation fault. This bug has been fixed and discard requests are no longer issued on missing devices. As the discard operation is irreversible, in addition to this fix, a confirmation prompt has been added to the lvremove utility to ask the user before discarding a LV, thus increasing robustness of the discard logic. (BZ#867009)

Users of lvm2 are advised to upgrade to these updated packages, which fix these bugs.

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 https://access.redhat.com/knowledge/articles/11258

Affected Products

Updated Packages

• device-mapper-event-devel-1.02.74-10.el6_3.2.x86_64.rpm
• lvm2-debuginfo-2.02.95-10.el6_3.2.s390x.rpm
• device-mapper-libs-1.02.74-10.el6_3.2.s390x.rpm
• lvm2-devel-2.02.95-10.el6_3.2.s390.rpm
• device-mapper-1.02.74-10.el6_3.2.ppc64.rpm
• lvm2-debuginfo-2.02.95-10.el6_3.2.ppc.rpm
• device-mapper-event-libs-1.02.74-10.el6_3.2.s390x.rpm
• lvm2-debuginfo-2.02.95-10.el6_3.2.i686.rpm
• lvm2-libs-2.02.95-10.el6_3.2.ppc64.rpm
• device-mapper-libs-1.02.74-10.el6_3.2.s390.rpm
• lvm2-libs-2.02.95-10.el6_3.2.s390x.rpm
• lvm2-2.02.95-10.el6_3.2.i686.rpm
• device-mapper-event-devel-1.02.74-10.el6_3.2.ppc64.rpm
• lvm2-devel-2.02.95-10.el6_3.2.ppc64.rpm
• device-mapper-event-1.02.74-10.el6_3.2.ppc64.rpm
• device-mapper-event-devel-1.02.74-10.el6_3.2.s390.rpm
• device-mapper-event-libs-1.02.74-10.el6_3.2.x86_64.rpm
• lvm2-devel-2.02.95-10.el6_3.2.ppc.rpm
• device-mapper-devel-1.02.74-10.el6_3.2.ppc.rpm
• device-mapper-event-devel-1.02.74-10.el6_3.2.s390x.rpm
• device-mapper-event-1.02.74-10.el6_3.2.i686.rpm
• lvm2-devel-2.02.95-10.el6_3.2.x86_64.rpm
• lvm2-2.02.95-10.el6_3.2.x86_64.rpm
• lvm2-2.02.95-10.el6_3.2.src.rpm
• device-mapper-event-1.02.74-10.el6_3.2.s390x.rpm
• device-mapper-event-devel-1.02.74-10.el6_3.2.ppc.rpm
• device-mapper-devel-1.02.74-10.el6_3.2.s390x.rpm
• device-mapper-event-libs-1.02.74-10.el6_3.2.s390.rpm
• cmirror-2.02.95-10.el6_3.2.x86_64.rpm
• device-mapper-1.02.74-10.el6_3.2.i686.rpm
• lvm2-libs-2.02.95-10.el6_3.2.i686.rpm
• lvm2-cluster-2.02.95-10.el6_3.2.i686.rpm
• lvm2-libs-2.02.95-10.el6_3.2.s390.rpm
• cmirror-2.02.95-10.el6_3.2.i686.rpm
• device-mapper-event-libs-1.02.74-10.el6_3.2.ppc.rpm
• device-mapper-libs-1.02.74-10.el6_3.2.ppc.rpm
• device-mapper-1.02.74-10.el6_3.2.x86_64.rpm
• lvm2-libs-2.02.95-10.el6_3.2.ppc.rpm
• lvm2-devel-2.02.95-10.el6_3.2.s390x.rpm
• lvm2-debuginfo-2.02.95-10.el6_3.2.x86_64.rpm
• lvm2-cluster-2.02.95-10.el6_3.2.x86_64.rpm
• device-mapper-event-devel-1.02.74-10.el6_3.2.i686.rpm
• device-mapper-event-1.02.74-10.el6_3.2.x86_64.rpm
• lvm2-2.02.95-10.el6_3.2.ppc64.rpm
• device-mapper-devel-1.02.74-10.el6_3.2.i686.rpm
• device-mapper-devel-1.02.74-10.el6_3.2.s390.rpm
• device-mapper-libs-1.02.74-10.el6_3.2.i686.rpm
• device-mapper-devel-1.02.74-10.el6_3.2.ppc64.rpm
• device-mapper-libs-1.02.74-10.el6_3.2.ppc64.rpm
• lvm2-libs-2.02.95-10.el6_3.2.x86_64.rpm
• lvm2-2.02.95-10.el6_3.2.s390x.rpm
• device-mapper-devel-1.02.74-10.el6_3.2.x86_64.rpm
• device-mapper-1.02.74-10.el6_3.2.s390x.rpm
• lvm2-debuginfo-2.02.95-10.el6_3.2.ppc64.rpm
• device-mapper-event-libs-1.02.74-10.el6_3.2.i686.rpm
• lvm2-devel-2.02.95-10.el6_3.2.i686.rpm
• device-mapper-event-libs-1.02.74-10.el6_3.2.ppc64.rpm
• device-mapper-libs-1.02.74-10.el6_3.2.x86_64.rpm
• lvm2-debuginfo-2.02.95-10.el6_3.2.s390.rpm

Fixes

• This content is not included.BZ - 843808
• This content is not included.BZ - 852438
• This content is not included.BZ - 852440
• This content is not included.BZ - 852441
• This content is not included.BZ - 867009

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.