RHBA-2007:0287 - Bug Fix Advisory
lvm2 bug fix and enhancement update
Bug Fix Advisory
Updated lvm2 packages that include various bug fixes and enhancements are
The lvm2 package contains support for logical volume management.
These updated lvm2 packages now include the following enhancements and bug
- Installs a script 'lvmdump' to create a tarball of information about lvm2
and device-mapper. You might be asked for this if you need support.
- Adds manual pages for 'lvconvert' and 'lvmdump' and updates several others.
- Adds the command line option '--config' to allow the overriding of most
settings in the configuration files.
- Changes 'dumpconfig' to use '--file' to redirect output and accepts a
space-separated list of configuration variables or sections to display.
E.g. 'lvm dumpconfig log/level backup'.
- Warns if certain duplicate entries are encountered in a configuration
file and avoids crashing if a section is empty.
- Fixes 'vgs' to treat its arguments as Volume Groups even when Physical
Volume fields are to be output.
- Shows a list of available fields if a reporting tool encounters an
unknown field. E.g. 'lvs -o help'.
- Adds %VG, %LV and %FREE suffices to the '--extents' arguments in
'lvcreate' and 'lvresize'.
- Fixes the detection of 'md' devices on big endian architectures.
- Adds a Logical Volume field to the reporting tools to list the required
- Fixes the loading of the kernel snapshot module when activating a snapshot.
- Reinstates a missing filesystem sync on creation of the first snapshot of
a Logical Volume.
- Adds the missing '--maxphysicalvolumes' command line option to 'vgchange'.
- Fixes the '--autobackup' argument to work as documented.
- Adds an error message to 'pvremove' when the device doesn't exist.
- Fixes the 'lvcreate' error message when no extents were requested.
- Adds support for Petabyte and Exabyte suffices and adds some bounds checks.
- Fixes 'pvremove' to handle the situation where the Physical Volume is
still in use.
- Fixes 'vgreduce --removemissing' to return success if Volume Group is
- Fixes 'vgchange' and 'lvchange' to handle persistent minor numbers correctly.
- Fixes the return code if a Volume Group specified on the command line is
- Retains the existing activation state after changing the Logical volume
minor number with --force.
- Includes further internal sanity checks before writing out updated metadata.
- Fixes command line Physical Extent range processing if a Physical Volume
is listed twice.
- Avoids attempting automatic metadata recovery if the correct lock is not
- Protects manipulation of the .cache file with fcntl locking.
- Stores the size of physical devices in text metadata.
- No longer attempts to load shared libraries from 'lvm.static'.
- Performs a high-level free space check before each allocation attempt.
- Adds the 'cling' allocation policy that allocates new extents on the same
Physical Volumes as existing extents.
- Uses the updated libdevmapper and libdevmapper-event library interfaces.
- Adds an initialisation script for monitoring Logical Volumes for failures
using 'dmeventd'. This is required only by lvm2 mirrors in this release.
- Disables 'lvm.static' interaction with 'dmeventd' by default.
- Adds a configuration option 'devices/ignore_suspended_devices' so
'dmeventd' can avoid scanning mirrors.
- Makes numerous corrections and improvements to the manipulation of lvm2
- Reports whether mirrors are being monitored for errors and copes if a
monitored device disappears.
- Adds a '--resync' command line option to 'lvchange' for use with mirrors.
- Makes further changes to benefit clustered installations. These are
described against 'lvm2-cluster'.
All users of lvm2 should upgrade to these updated packages, which include
these bug fixes and enhancements.
Before applying this update, make sure that all previously-released
errata relevant to your system have been applied. Use Red Hat
Network to download and update your packages. To launch the Red Hat
Update Agent, use the following command:
For information on how to install packages manually, refer to the
following Web page for the System Administration or Customization
guide specific to your system:
- Red Hat Enterprise Linux Server 4 x86_64
- Red Hat Enterprise Linux Server 4 ia64
- Red Hat Enterprise Linux Server 4 i386
- Red Hat Enterprise Linux Workstation 4 x86_64
- Red Hat Enterprise Linux Workstation 4 ia64
- Red Hat Enterprise Linux Workstation 4 i386
- Red Hat Enterprise Linux Desktop 4 x86_64
- Red Hat Enterprise Linux Desktop 4 i386
- Red Hat Enterprise Linux for IBM z Systems 4 s390x
- Red Hat Enterprise Linux for IBM z Systems 4 s390
- Red Hat Enterprise Linux for Power, big endian 4 ppc
- BZ - 162607 - pvmove could use a better error message when it's unable to activate an lv for exclusive locking
- BZ - 162704 - Long-running LVM2 processes fail to handle VG deletion followed by new VG creation with same name as old one
- BZ - 162809 - vgchange -ae error could be much better if vg is already in use
- BZ - 165787 - Not mount local lvm2 partition with lvm2-cluster
- BZ - 186304 - [RHEL4 U3] LVM2 mirror: lvextend spoils redundancy by allocating extents for mirror images from same PV.
- BZ - 193543 - 'vgs' with options from 'pvs' treats arguments as PVs not VGs
- BZ - 198821 - logical volume corruption during mirror creation/deletion loop
- BZ - 202232 - vgchange -p isn't implemented
- BZ - 202759 - mirror option (-m1) undocumented in lvcreate man/info page
- BZ - 202826 - vgsplit is broken with mirrors
- BZ - 202864 - Error message for failed vgsplit seems to imply that it actually worked
- BZ - 204128 - lvconvert from linear to mirror fails if original LV spans to PVs
- BZ - 204509 - lvm.static segfaults when trying to do initial vgscan in rc.sysinit with clustered LV's
- BZ - 206091 - changing lvm device minor numbers doesn't work
- BZ - 209320 - attempt to lock already locked VG hangs with gulm
- BZ - 210302 - LVM-Volumes with active Snapshots are not readable after Reboot
- BZ - 213552 - regression: lvextend no longer works out to the size of available space in the VG
- BZ - 213759 - regression: mirror sync log not being properly zero'ed out
- BZ - 213894 - lvextend fails even though there is plenty of space left to extend with
- BZ - 215977 - a forced pvremove of pvs with pvmoves inprogress will hang
- BZ - 218351 - creating ro lvm volumes cause "failed write" errors
- BZ - 220563 - _raw_read_mda_header does not free struct mda_header *mdah in error paths
- BZ - 221322 - Unable to create mirror with name longer than 22 chars
- BZ - 221921 - vgreduce gives wrong return code after successful removal of failed mirror log device
- BZ - 224078 - lvm(8) can leave a truncated /etc/lvm/.cache file
- BZ - 229471 - Tagging causes problems when doing mirror operations
- BZ - 231979 - clvmd does not recover locks when restarting
- BZ - 232397 - LVM2 unable to use LVM1 striped logical volumes
Red Hat Enterprise Linux for Power, big endian 4