Skip to navigation

Bug Fix Advisory lvm2 bug fix update

Advisory: RHBA-2013:0023-1
Type: Bug Fix Advisory
Severity: N/A
Issued on: 2013-01-07
Last updated on: 2013-01-07
Affected Products: Red Hat Enterprise Linux (v. 5 server)
Red Hat Enterprise Linux Desktop (v. 5 client)

Details

Updated lvm2 packages that fix four bugs are now available for Red Hat
Enterprise Linux 5.

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

This update fixes the following bugs:

* Prior to this update, the --alloc option in the lvm2 man pages was
insufficiently documented. A more detailed specification of allocation policies
was needed. With this update, the description has been enhanced and provides a
more comprehensive insight into the allocation process. (BZ#770970)

* Previously, when the pv_min_size setting in the lvm.conf configuration file
(/etc/lvm/lvm.conf) was set to value smaller than the default value of 2048 KB,
the system ignored this configuration later on. Consequently, the lvm commands
returned the following warning when processing smaller physical volumes:

Ignoring too small pv_min_size 512KB, using default 2048KB.

This bug has been fixed, and user-set pv_min_size is no longer ignored in the
aforementioned case. (BZ#786009)

* Previously, when a physical volume (PV) with no physical extents (PE) was in a
volume group (VG), the vgcfgrestore command executed on the VG failed with the
following message:

Floating point exception

This behavior was caused by a division by zero error. With this update, a fix
has been introduced to avoid the aforementioned exception. As a result,
vgcfgrestore no longer fails in the described scenario. (BZ#820237)

* Previously, it was possible to use the lvcreate command with the --alloc cling
option to create a linear device that exceeded any single physical volume (PV)
within the volume group (VG). The lvcreate command placed the data across
multiple PVs, which was in conflict with the cling allocation policy. This bug
has been fixed and lvcreate now works in accordance with the selected allocation
policy. (BZ#821013)

All 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

Updated packages

Red Hat Enterprise Linux (v. 5 server)

SRPMS:
lvm2-2.02.88-10.el5.src.rpm
File outdated by:  RHBA-2013:1352
    MD5: 1d063d1f8fe067d62fdb95dd8e281f84
SHA-256: 1703d8efd3b49b826ecf3eae14748a1a17f0068040e56c1ecb47512844437bde
 
IA-32:
lvm2-2.02.88-10.el5.i386.rpm
File outdated by:  RHBA-2013:1352
    MD5: 85f748846f3706143afe12603158c09a
SHA-256: 5127b337f8733f3e6fd43092ddf90a616997366b2b2ded5226dbf284d3c45771
lvm2-debuginfo-2.02.88-10.el5.i386.rpm
File outdated by:  RHBA-2013:1352
    MD5: 5cd2d0495f894006dc1edbc735bb4e23
SHA-256: ddb186b144bf054b5cc20f26c1631b8685ea51fbc086fa42b7731603ffc90b56
 
IA-64:
lvm2-2.02.88-10.el5.ia64.rpm
File outdated by:  RHBA-2013:1352
    MD5: 0a1f1854f23d15e547fe1620ecc9439e
SHA-256: fef0ad0f6e54719b4918045a5aa458b98ca6e3cb8491f7b6f4abbed53de332ae
lvm2-debuginfo-2.02.88-10.el5.ia64.rpm
File outdated by:  RHBA-2013:1352
    MD5: 23dfe36dd72d1f2342c22fab5a9d0974
SHA-256: 54ee10990efdb4743d7170ee3d4a65b5879383556807a943ac71e20251283dcd
 
PPC:
lvm2-2.02.88-10.el5.ppc.rpm
File outdated by:  RHBA-2013:1352
    MD5: c71cf111014393e8721e2f7f40442966
SHA-256: dbae2c1ddd8e2539c2fdc7579fe8082ee1d17ce11e38bab029df7840227e89a5
lvm2-debuginfo-2.02.88-10.el5.ppc.rpm
File outdated by:  RHBA-2013:1352
    MD5: f44f27e19491475c19d8093efde15331
SHA-256: b61a2443239e245871cd899ce1e9a51f0f383477af145a11f87fad527b98ca67
 
s390x:
lvm2-2.02.88-10.el5.s390x.rpm
File outdated by:  RHBA-2013:1352
    MD5: 58932a6909dfde2088f7740a2793fd36
SHA-256: d0d87f396d1a1b2528dd08488da00d8720877b150b69bce523d549d266ce4f2d
lvm2-debuginfo-2.02.88-10.el5.s390x.rpm
File outdated by:  RHBA-2013:1352
    MD5: bd58f6e00ec780d57d01ea4f13d63587
SHA-256: 727f615aa1bc820ef38600ccceeb58a0b8a4fa5a94e54dadfb1b11d210acf298
 
x86_64:
lvm2-2.02.88-10.el5.x86_64.rpm
File outdated by:  RHBA-2013:1352
    MD5: 6f195754b6c20bec7aeb55aff874b8a4
SHA-256: 092fa8027c8465dca5a70e7b6dc7f45001cc548b64cbf8748ee2af5a16966451
lvm2-debuginfo-2.02.88-10.el5.x86_64.rpm
File outdated by:  RHBA-2013:1352
    MD5: ea99bc179339ed2b17fd2caa9728c401
SHA-256: a6fb4c1634bb18e060811a4d9107683df46dba118c7a142fd9b6ba11a21d5678
 
Red Hat Enterprise Linux Desktop (v. 5 client)

SRPMS:
lvm2-2.02.88-10.el5.src.rpm
File outdated by:  RHBA-2013:1352
    MD5: 1d063d1f8fe067d62fdb95dd8e281f84
SHA-256: 1703d8efd3b49b826ecf3eae14748a1a17f0068040e56c1ecb47512844437bde
 
IA-32:
lvm2-2.02.88-10.el5.i386.rpm
File outdated by:  RHBA-2013:1352
    MD5: 85f748846f3706143afe12603158c09a
SHA-256: 5127b337f8733f3e6fd43092ddf90a616997366b2b2ded5226dbf284d3c45771
lvm2-debuginfo-2.02.88-10.el5.i386.rpm
File outdated by:  RHBA-2013:1352
    MD5: 5cd2d0495f894006dc1edbc735bb4e23
SHA-256: ddb186b144bf054b5cc20f26c1631b8685ea51fbc086fa42b7731603ffc90b56
 
x86_64:
lvm2-2.02.88-10.el5.x86_64.rpm
File outdated by:  RHBA-2013:1352
    MD5: 6f195754b6c20bec7aeb55aff874b8a4
SHA-256: 092fa8027c8465dca5a70e7b6dc7f45001cc548b64cbf8748ee2af5a16966451
lvm2-debuginfo-2.02.88-10.el5.x86_64.rpm
File outdated by:  RHBA-2013:1352
    MD5: ea99bc179339ed2b17fd2caa9728c401
SHA-256: a6fb4c1634bb18e060811a4d9107683df46dba118c7a142fd9b6ba11a21d5678
 
(The unlinked packages above are only available from the Red Hat Network)

Bugs fixed (see bugzilla for more information)

770970 - lvm2 man page and documentation for "normal" Allocation Policy needs to be improved
786009 - Ignoring too small pv_min_size 512KB
820237 - vgcfgrestore fails with division by zero if metadata-only PV with no physical extents present in VG
821013 - cling allocation policy should never split data across PVs



These packages are GPG signed by Red Hat for security. Our key and details on how to verify the signature are available from:
https://www.redhat.com/security/team/key/#package

The Red Hat security contact is secalert@redhat.com. More contact details at http://www.redhat.com/security/team/contact/