- Issued:
- 2010-03-30
- Updated:
- 2010-03-30
RHBA-2010:0255 - Bug Fix Advisory
Synopsis
device-mapper-multipath 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 device-mapper-multipath packages that fix several bugs and add
various enhancements are now available.
Description
The device-mapper-multipath packages provide tools to manage multipath
devices using the device-mapper multipath kernel module.
This update applies the following bug fixes:
- The kpartx utility creates device maps from partition tables.
Device-mapper devices with minor numbers greater than 255 caused kpartx to
use the UUID from the wrong device when trying to create partitions. If the
device had pre-existing partitions, kpartx would fail to create the new
partitions. With this update, kpartx is now able to handle device-mapper
devices with minor numbers greater than 255. (BZ#526550)
- The udev rules for device-mapper-multipath were causing device-mapper to
occasionally create multipath devices without using the user specified uid,
gid, or mode. They have been replaced with equivalent rules that do not
cause this issue. (BZ#518575)
- When LUNs were unmapped from LSI storage arrays, the multipath rdac path
checker was not marking the paths as failed. This caused IO to the device
to hang instead of fail. The rdac path checker now marks unmapped LUNs as
failed. (BZ#531744)
- The failover path grouping policy was not ordering the paths by priority,
causing multipath to failover to the wrong path for devices with manual
failback. The multipath paths are now correctly ordered with the failover
path grouping policy. (BZ#537977)
- On some storage devices, if a LUN is deleted from an existing multipathd
device, and a new LUN is presented to the host, it may end up with the same
LUN ID and name as the old LUN. In this case, multipath will assume that
this is the old LUN and belongs to the existing multipath device. This
cause cause corruption. A new path checker "hp_tur" has been added that
verifies the WWID of the LUN when it checks the path, to avoid this
problem. (BZ#437585)
- The "tur" path checker was marking paths in standby mode as "failed". It
now correctly marks them as "ghost". (BZ#473039)
- Multipath wasn't correctly showing device renames in dry-run mode. This
has been fixed. (BZ#501019)
- Multipath was incorrectly setting the hardware handler for HP
StorageWorks devices.This has been fixed. (BZ#475967)
- On some storage devices, multipath would display incorrect path
information the first time multipath listed the paths after recovery. This
has been fixed. (BZ#499080)
- If a path is removed while it is still part of a multipath device, it
was taking multipath minutes to mark it as failed. This should now happen
immediately at the end of the next path checking interval. (BZ#527754)
- the multipathd daemon needs constant access to /var/lib and /var/run.
However it was not allowing any devices mounted under /var to be removed.
Now it only keeps open what it needs. (BZ#532424)
- the multipath checker functions were not using the default scsi timeouts.
Instead, each checker set its own timeout. Now all checker functions with
explicit timeouts use the scsi timeout set it
/sys/block/sd<x>/device/timeout by default. This can be changed by setting
the "checker_timeout" option in /etc/multipath.conf(BZ#553042)
- Multipathd was printing extraneous error messages. This has been fixed.
(BZ#472171, BZ#502128, BZ#524178)
- The multipath man page had some mistakes and missing information. This
has been fixed. (BZ#481239, BZ#510331, BZ#554830)
- A locking error could cause multipathd to deadlock if it failed to create
a multipath device correctly. This has been fixed (BZ #537281)
This update adds the following enhancements:
- Default configurations were added for more IBM, HP, SUN, and DELL
devices. (BZ#504619i, BZ#512243, BZ#515171, BZ#517896, BZ#540882,
BZ#545882)
- The kpartx utility now supports DASDs devices with more then 65520
cylinders. (BZ#524009)
All users 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 - 472171 - Restarting multipathd daemon logs some errors in /var/log/messages
- BZ - 475967 - multipath should search for "hp-sw" hardware handler, not for "hp_sw"
- BZ - 481239 - multipath -v2 command overwrites aliases specified in multipath.conf when alias is of form mpathX
- BZ - 499080 - Using readsector0 path checker, multipath displays the incorrect path information the first time after recovery.
- BZ - 502128 - /etc/init.d/multipathd reports error for non-dm managed root disk
- BZ - 504619 - Default multipath configuration ignores some MSA1000 arrays
- BZ - 515171 - Add support for Sun 6540 storage arrays.
- BZ - 518575 - Multipath UID/GID/MODE settings not always taking effect
- BZ - 524178 - Got error output when restart multipathd service
- BZ - 527754 - I takes a very long time after a device fails for the multipathd to mark it faulty
- BZ - 531744 - [LSI 5.5 bug] RDAC path checker leads to I/O hang when volumes are unmapped from storage
- BZ - 532424 - Device Mapper multipath wont unmount sub mounts of /var/
- BZ - 537281 - dm-mp domap() fails to unlock paths if map is already present
- BZ - 537977 - dm-mp path group prio ignored, active path not reported after failover, failback issues
- BZ - 540882 - [LSI 5.5 bug] update hwtable.c for multiapth-tools with new vendor and model
- BZ - 545822 - Add hwtable entry for EMC Invista
CVEs
(none)
References
(none)
Red Hat Enterprise Linux Server 5
SRPM | |
---|---|
device-mapper-multipath-0.4.7-34.el5.src.rpm | SHA-256: 3c513f07f05286a322d758bddc7b99d3503414b12b684580fa3d813942385cdd |
x86_64 | |
device-mapper-multipath-0.4.7-34.el5.x86_64.rpm | SHA-256: f306e5bd37251f5fd7ae824e9b0eacd03828118de005bd704165e3422a7509f9 |
kpartx-0.4.7-34.el5.x86_64.rpm | SHA-256: 6d53e8879f13018870a72f00e8e950d59eaa826b591ad8e75f162db5dd115dac |
ia64 | |
device-mapper-multipath-0.4.7-34.el5.ia64.rpm | SHA-256: bd58a042fb3710601cd5789bc05ad50ac2740b9b99e01a5ac3bae28f1894962e |
kpartx-0.4.7-34.el5.ia64.rpm | SHA-256: 283403e8dae69862f3861c97251f8fa2e2875650ed877c294b9f1c8e02fe8770 |
i386 | |
device-mapper-multipath-0.4.7-34.el5.i386.rpm | SHA-256: 8023ff9433f3c7d3c91405f6b94fbffdaa393d8cb5cebe67ca43e27740cda1fc |
kpartx-0.4.7-34.el5.i386.rpm | SHA-256: 7f33eb5f365947f15bf8f80ae28ac5882590509d5215cc08a5afa769f0acbfd6 |
Red Hat Enterprise Linux Workstation 5
SRPM | |
---|---|
device-mapper-multipath-0.4.7-34.el5.src.rpm | SHA-256: 3c513f07f05286a322d758bddc7b99d3503414b12b684580fa3d813942385cdd |
x86_64 | |
device-mapper-multipath-0.4.7-34.el5.x86_64.rpm | SHA-256: f306e5bd37251f5fd7ae824e9b0eacd03828118de005bd704165e3422a7509f9 |
kpartx-0.4.7-34.el5.x86_64.rpm | SHA-256: 6d53e8879f13018870a72f00e8e950d59eaa826b591ad8e75f162db5dd115dac |
i386 | |
device-mapper-multipath-0.4.7-34.el5.i386.rpm | SHA-256: 8023ff9433f3c7d3c91405f6b94fbffdaa393d8cb5cebe67ca43e27740cda1fc |
kpartx-0.4.7-34.el5.i386.rpm | SHA-256: 7f33eb5f365947f15bf8f80ae28ac5882590509d5215cc08a5afa769f0acbfd6 |
Red Hat Enterprise Linux Desktop 5
SRPM | |
---|---|
device-mapper-multipath-0.4.7-34.el5.src.rpm | SHA-256: 3c513f07f05286a322d758bddc7b99d3503414b12b684580fa3d813942385cdd |
x86_64 | |
device-mapper-multipath-0.4.7-34.el5.x86_64.rpm | SHA-256: f306e5bd37251f5fd7ae824e9b0eacd03828118de005bd704165e3422a7509f9 |
kpartx-0.4.7-34.el5.x86_64.rpm | SHA-256: 6d53e8879f13018870a72f00e8e950d59eaa826b591ad8e75f162db5dd115dac |
i386 | |
device-mapper-multipath-0.4.7-34.el5.i386.rpm | SHA-256: 8023ff9433f3c7d3c91405f6b94fbffdaa393d8cb5cebe67ca43e27740cda1fc |
kpartx-0.4.7-34.el5.i386.rpm | SHA-256: 7f33eb5f365947f15bf8f80ae28ac5882590509d5215cc08a5afa769f0acbfd6 |
Red Hat Enterprise Linux for IBM z Systems 5
SRPM | |
---|---|
device-mapper-multipath-0.4.7-34.el5.src.rpm | SHA-256: 3c513f07f05286a322d758bddc7b99d3503414b12b684580fa3d813942385cdd |
s390x | |
device-mapper-multipath-0.4.7-34.el5.s390x.rpm | SHA-256: 59ec760d3f9de7e824412c1089e48534b7e13dea0c260f18ce61bca64dd60dda |
kpartx-0.4.7-34.el5.s390x.rpm | SHA-256: e8f10cfb9fe1e5a71f64b304ef97e7f5f3ff99aefd7c175212f4677b0d5f8449 |
Red Hat Enterprise Linux for Power, big endian 5
SRPM | |
---|---|
device-mapper-multipath-0.4.7-34.el5.src.rpm | SHA-256: 3c513f07f05286a322d758bddc7b99d3503414b12b684580fa3d813942385cdd |
ppc | |
device-mapper-multipath-0.4.7-34.el5.ppc.rpm | SHA-256: 4022360d32ba4bb35e19f0ed9a861e02ab20608bb74b03ef9ec0beb571d53968 |
kpartx-0.4.7-34.el5.ppc.rpm | SHA-256: af23cc33584bfc0c5f1a2c0a2a49f9964524242043c3ab9df49298d0c08b77d1 |
Red Hat Enterprise Linux Server from RHUI 5
SRPM | |
---|---|
device-mapper-multipath-0.4.7-34.el5.src.rpm | SHA-256: 3c513f07f05286a322d758bddc7b99d3503414b12b684580fa3d813942385cdd |
x86_64 | |
device-mapper-multipath-0.4.7-34.el5.x86_64.rpm | SHA-256: f306e5bd37251f5fd7ae824e9b0eacd03828118de005bd704165e3422a7509f9 |
kpartx-0.4.7-34.el5.x86_64.rpm | SHA-256: 6d53e8879f13018870a72f00e8e950d59eaa826b591ad8e75f162db5dd115dac |
i386 | |
device-mapper-multipath-0.4.7-34.el5.i386.rpm | SHA-256: 8023ff9433f3c7d3c91405f6b94fbffdaa393d8cb5cebe67ca43e27740cda1fc |
kpartx-0.4.7-34.el5.i386.rpm | SHA-256: 7f33eb5f365947f15bf8f80ae28ac5882590509d5215cc08a5afa769f0acbfd6 |
The Red Hat security contact is secalert@redhat.com. More contact details at https://access.redhat.com/security/team/contact/.