- Issued:
- 2010-03-30
- Updated:
- 2010-03-30
RHBA-2010:0298 - Bug Fix Advisory
Synopsis
lvm2 bug fix and enhancement update
Type/Severity
Bug Fix Advisory
Red Hat Insights patch analysis
Identify and remediate systems affected by this advisory.
Topic
Updated lvm2 packages that fix several bugs and add enhancements are
now available.
Description
The lvm2 packages contain support for Logical Volume Management (LVM).
This update applies the following bug fixes:
- Fixes crash in dmevnetd if both snapshot and mirror monitoring is used.
- Fixes several memory locking problems which could lead to deadlocks.
- Uses read-only instead or write lock for lvchange --refresh.
- Fixes bug where non-blocking file locks could be granted in error.
- Uses fixed buffer to prevent stack overflow in persistent filter dump.
- Fixes default device mode permissions when using static lvm.
- Fixes return code of info call for query by uuid.
- Allows vgremove of a VG with PVs missing.
- Drops metadata cache after device was autorepaired and removed from VG.
- Removes missing flag in metadata if PV reappeared and is empty.
- Fixes unlocking of Volume Group in pvresize and toollib error paths.
- Removes log volume from metadata if initial deactivation fails.
- Fixes several memory leaks in pvs and pvdisplay commands.
- Dumps persistent device filter after every full scan.
- Refreshes device filters before full device rescan.
- Returns error status if vgchange fails to activate some volume.
- Restricts vgchange to activate only visible LVs.
- Fixes pvmove region_size overflow for very large PVs.
- Fixes lvcreate and lvresize %PVS argument always to use sensible total
size.
- Delays announcing mirror monitoring to syslog until initialisation
succeeded.
- Doesn't attempt to deactivate an LV if any of its snapshots are in use.
- Fixes pvcreate string termination in duplicate uuid warning message.
- Makes lvchange --refresh only take a read lock on volume group.
- Makes lvconvert honour log mirror options combined with downconversion.
- Makes all tools use consistent lock ordering obtaining VG_ORPHAN lock
second.
- Fixes memory leak in vgsplit when re-reading the vg.
- Fixes crash in vg_release.
- Explicitly requests fallback to default major number in device mapper.
- Rounds up requested readahead to at least one page and print warning.
- Fixes mirror convert polling to ignore LV with different UUID.
As well, this update adds the following enhancements:
- Uses lvconvert --repair instead of vgreduce in mirror dmeventd and
introduces to use mirror image and log policies. In the event of a failure,
the policy specified in lvm.conf will be used to determine what happens
(for exact description see using mirror_log_fault_policy and
mirror_image_fault_policy comments in lvm.conf).
- Updates man pages, including lvcreate,lvconvert to explain PhysicalVolume
parameter, document --all option, clarify use of PE ranges, mention
- -repair in lvconvert and document size units uniformly.
- Adds new option prioritise_write_locks in lvm.conf. This option only
affects locking_type 1 (local file-based locking).
- Introduces new read-only locking as locking type 4.
- Adds wait_for_locks option to lvm.conf so blocking for locks can be
disabled.
- Adds an API version number, LVM_LIBAPI, to the VERSION string for liblvm.
- Handles metadata with unknown segment types more gracefully.
- Adds --pvmetadatacopies for pvcreate, vgcreate, vgextend, vgconvert.
- Adds implict pvcreate support to vgcreate and vgextend.
- Recognises DRBD devices and handle them like MD mirror devices.
- Checks MD devices for a partition table during device scan.
- Adds extended device (blkext) and md partition (mdp) types to filters.
- Distinguishes between powers of 1000 and powers of 1024 in unit suffixes
(si_unit_consistency lvm.conf option).
- Introduces automatic data_alignment detection and adds
devices/data_alignment_detection to lvm.conf.
- Adds --dataalignmentoffset to pvcreate to shift start of aligned data
area.
- Updates 'md_chunk_alignment' to use stripe-width to align PV data area.
Users of lvm2 are advised to upgrade to these updated packages, which
resolve these issues and add these enhancements.
Solution
Before applying this update, make sure that all previously-released
errata relevant to your system have been applied.
This update is available via Red Hat Network. Details on how to use
the Red Hat Network to apply this update are available at
http://kbase.redhat.com/faq/docs/DOC-11259
Affected Products
- Red Hat Enterprise Linux Server 5 x86_64
- Red Hat Enterprise Linux Server 5 ia64
- Red Hat Enterprise Linux Server 5 i386
- Red Hat Enterprise Linux Workstation 5 x86_64
- Red Hat Enterprise Linux Workstation 5 i386
- Red Hat Enterprise Linux Desktop 5 x86_64
- Red Hat Enterprise Linux Desktop 5 i386
- Red Hat Enterprise Linux for IBM z Systems 5 s390x
- Red Hat Enterprise Linux for Power, big endian 5 ppc
- Red Hat Enterprise Linux Server from RHUI 5 x86_64
- Red Hat Enterprise Linux Server from RHUI 5 i386
Fixes
- BZ - 463272 - disk log mirror convert option is lost if down covert option is also given
- BZ - 481793 - Attempting to vgsplit a base PV into a VG stacked on top causes a seg fault
- BZ - 500177 - lvconvert is not atomic
- BZ - 500899 - RFE: give better message when pvmove is already in progress on requested VG
- BZ - 510526 - RHEL5 cmirror tracker: core log mirrors appear to unnecessarily resync twice after upconvert following leg failure
- BZ - 515232 - LVM commands take a VERY long time (>40 min) to finish
- BZ - 516773 - vgextend does not take blocking lock and fails if run concurrently with lvextend
- BZ - 529668 - vg* tools exit with 'success' even though supplied VG name format invalid
- BZ - 536817 - Upgrade lvm2 to 2.02.56 version
- BZ - 537942 - deadlock after multiple primary device failures
- BZ - 537947 - what happened to the 'use vgreduce --removemissing' hint?
- BZ - 537954 - vgreduce issues while attempting to clean up VG after failure
- BZ - 538620 - mirror fault policies in lvm.conf should be consistent
- BZ - 543225 - multiple leg failure leaves mirror with only an "unknown device"
- BZ - 543658 - disk log failure of two synced mirrors caused deadlock
- BZ - 547891 - unable to recreate pv on re-enabled failed device due to 'inconsistent vg'
- BZ - 548223 - new mirror changes at risk of being pulled out before rhel5.5
- BZ - 552723 - repair of failed mirror is failing, causing many other issues
- BZ - 557104 - dmeventd crash if both snapshot and mirror monitoring DSO are used
- BZ - 564009 - Need to disable snapshots of mirrors in rhel5.5
CVEs
(none)
References
(none)
Red Hat Enterprise Linux Server 5
SRPM | |
---|---|
lvm2-2.02.56-8.el5.src.rpm | SHA-256: 18cf86ac34ad835a2677445f1b39a7860fee8470401a6ea2813b6002fa3981a3 |
x86_64 | |
lvm2-2.02.56-8.el5.x86_64.rpm | SHA-256: 0fdd0f5514f31b78723568d063f97b03366debb2d8309d6a5949fbb74d06add7 |
ia64 | |
lvm2-2.02.56-8.el5.ia64.rpm | SHA-256: 790a95678f0a3714f075ff426102c072a8fff4e0704ff00bd8b7b2c1c6ed9499 |
i386 | |
lvm2-2.02.56-8.el5.i386.rpm | SHA-256: 5e4a5f60ec790762ba8c8ba4119bfb0aa5c2ce0eaefeb1161b88122dee046d56 |
Red Hat Enterprise Linux Workstation 5
SRPM | |
---|---|
lvm2-2.02.56-8.el5.src.rpm | SHA-256: 18cf86ac34ad835a2677445f1b39a7860fee8470401a6ea2813b6002fa3981a3 |
x86_64 | |
lvm2-2.02.56-8.el5.x86_64.rpm | SHA-256: 0fdd0f5514f31b78723568d063f97b03366debb2d8309d6a5949fbb74d06add7 |
i386 | |
lvm2-2.02.56-8.el5.i386.rpm | SHA-256: 5e4a5f60ec790762ba8c8ba4119bfb0aa5c2ce0eaefeb1161b88122dee046d56 |
Red Hat Enterprise Linux Desktop 5
SRPM | |
---|---|
lvm2-2.02.56-8.el5.src.rpm | SHA-256: 18cf86ac34ad835a2677445f1b39a7860fee8470401a6ea2813b6002fa3981a3 |
x86_64 | |
lvm2-2.02.56-8.el5.x86_64.rpm | SHA-256: 0fdd0f5514f31b78723568d063f97b03366debb2d8309d6a5949fbb74d06add7 |
i386 | |
lvm2-2.02.56-8.el5.i386.rpm | SHA-256: 5e4a5f60ec790762ba8c8ba4119bfb0aa5c2ce0eaefeb1161b88122dee046d56 |
Red Hat Enterprise Linux for IBM z Systems 5
SRPM | |
---|---|
lvm2-2.02.56-8.el5.src.rpm | SHA-256: 18cf86ac34ad835a2677445f1b39a7860fee8470401a6ea2813b6002fa3981a3 |
s390x | |
lvm2-2.02.56-8.el5.s390x.rpm | SHA-256: 708219478ede7060441f780bc776b60d74cfce65bfacba795b47d8687da1ab50 |
Red Hat Enterprise Linux for Power, big endian 5
SRPM | |
---|---|
lvm2-2.02.56-8.el5.src.rpm | SHA-256: 18cf86ac34ad835a2677445f1b39a7860fee8470401a6ea2813b6002fa3981a3 |
ppc | |
lvm2-2.02.56-8.el5.ppc.rpm | SHA-256: 72dd04d68e1a8886c0142d8bdfc5a75a2a06de715f88d246e887182ba85e9d95 |
Red Hat Enterprise Linux Server from RHUI 5
SRPM | |
---|---|
lvm2-2.02.56-8.el5.src.rpm | SHA-256: 18cf86ac34ad835a2677445f1b39a7860fee8470401a6ea2813b6002fa3981a3 |
x86_64 | |
lvm2-2.02.56-8.el5.x86_64.rpm | SHA-256: 0fdd0f5514f31b78723568d063f97b03366debb2d8309d6a5949fbb74d06add7 |
i386 | |
lvm2-2.02.56-8.el5.i386.rpm | SHA-256: 5e4a5f60ec790762ba8c8ba4119bfb0aa5c2ce0eaefeb1161b88122dee046d56 |
The Red Hat security contact is secalert@redhat.com. More contact details at https://access.redhat.com/security/team/contact/.