Device-Mapper-Multipath; Rhba-2009:0432: Bug Fix Update - Red Hat ENTERPRISE LINUX 5.4 - TECHNICAL NOTES Manual

Chapter 1. Package Updates
The device-mapper packages provide a library required by logical volume management utilities such
as LVM2 and dmraid.
This update applies the following bug fixes:
• Fixes crash when dmsetup -U, -G, and -M options are used.
• Enforces device name length and character limitations.
This update adds the following enhancements:
• Adds "all" field to "-o fields" option, expanding to all fields of report type. That is, you can add -o
<field_name> to specify which fields to print in certain commands; "-o all" expands to all possible
fields known to report.
• Library now exports dm_tree_node_size_changed function and correctly propagates table size
change up the device tree.
• Prints warning message if application releases the library and a memory pool is still in use
(indicating a possible memory leak).
• Library is now compiled from merged device-mapper LVM2 tree (device-mapper library is now part
of LVM2 source code tree).
All users of device-mapper should upgrade to these updated packages, which resolve these issues
and include these enhancements.

1.36. device-mapper-multipath

1.36.1. RHBA-2009:0432: bug fix update

Note
This update has already been released (prior to the GA of this release) as errata
RHBA-2009:0432
Updated device-mapper-multipath packages that resolve an issue are now available.
The device-mapper multipath packages provide tools to manage multipath devices by issuing
instructions to the device-mapper multipath kernel module, and by managing the creation and removal
of partitions for device-mapper devices.
These updated device-mapper-multipath packages fix the following bug:
• there was a race condition in the shutdown code for multipathd wherein a lock could be destroyed
before all threads were finished using it. This could cause the machine to become unresponsive
on multipathd shutdown. The multipathd daemon now waits for all threads to finish using the lock
before destroying it, thus removing the race and resolving the issue.
• when adding a new multipath-capable block device, a race condition existed between the multipathd
daemon and udev to multipath the new device. If udev--through multipath--updated the multipath
devices first, then the multipathd daemon would not use the device-specific configurations for the
40
237