device-mapper-multipath bug fix update
| Advisory: | RHBA-2008:0050-4 |
|---|---|
| Type: | Bug Fix Advisory |
| Severity: | N/A |
| Issued on: | 2008-01-30 |
| Last updated on: | 2008-01-30 |
| Affected Products: | Red Hat Enterprise Linux (v. 5 server) Red Hat Enterprise Linux Desktop (v. 5 client) Red Hat Enterprise Linux EUS (v. 5.1.z server) |
Details
Updated device-mapper-multipath packages that fix two bugs are now
available.
The device-mapper-multipath packages provide tools to manage multipath
devices by giving the device-mapper multipath kernel module instructions on
what to do, as well as by managing the creation and removal of partitions
for device-mapper devices.
These updated device-mapper-multipath packages fix the following bugs:
* a problem with the way that the device-mapper-multipath program looked
for the user_friendly_names bindings file at /var/lib/multipath/bindings.
If /var was on a seperate file system from /, this could cause problems at
boot time, when multipath devices were not created with user-friendly
names. These updated packages provide a "bindings_file" option for the
multipath config file, /etc/multipath.conf. This can be used to set where
the device-mapper-multipath programs will look for the bindings file. The
suggested location is /etc/multipath_bindings.
* a problem with running multipath on the device containing the root
filesystem. The multipath daemon needed access to the root file system in
order to run path group priority callout programs whenever a path was added
or removed. If all the paths to the root filesystem failed, multipathd
would hang trying to access the callout program. It would then not be able
to restore access to the device after a path became active again. These
updated packages fix this problem by creating a ramfs cache for multipathd,
and loading all of the callout programs into it. This way, multipathd
always has access to those programs, even if the device they are stored on
is unreachable.
Users are advised to upgrade to these updated device-mapper-multipath
packages, which resolve this issue.
Solution
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/FAQ_58_10188
Updated packages
| Red Hat Enterprise Linux (v. 5 server) | |
| SRPMS: | |
| device-mapper-multipath-0.4.7-12.el5_1.2.src.rpm File outdated by: RHBA-2008:0219 |
MD5: 51fe3eda10fa75e17af3a5f4dbe171d8 |
| IA-32: | |
| device-mapper-multipath-0.4.7-12.el5_1.2.i386.rpm File outdated by: RHBA-2013:0779 |
MD5: 1431d646b9ff400192813c4152b1b7dd |
| kpartx-0.4.7-12.el5_1.2.i386.rpm File outdated by: RHBA-2013:0779 |
MD5: 0ffb24b1b96770b7a18f06770a142e39 |
| IA-64: | |
| device-mapper-multipath-0.4.7-12.el5_1.2.ia64.rpm File outdated by: RHBA-2013:0779 |
MD5: f95967c56ca0169453e90485a5405167 |
| kpartx-0.4.7-12.el5_1.2.ia64.rpm File outdated by: RHBA-2013:0779 |
MD5: c1f7add82b412a05f95dfe61639c528b |
| PPC: | |
| device-mapper-multipath-0.4.7-12.el5_1.2.ppc.rpm File outdated by: RHBA-2013:0779 |
MD5: 36a9e46bd9041d204f1eeb56e14a306d |
| kpartx-0.4.7-12.el5_1.2.ppc.rpm File outdated by: RHBA-2013:0779 |
MD5: f52d5739d3d9d5a3df3669d17cde8b59 |
| s390x: | |
| device-mapper-multipath-0.4.7-12.el5_1.2.s390x.rpm File outdated by: RHBA-2013:0779 |
MD5: e1b6507d2dcacc069c80bff6606f6585 |
| kpartx-0.4.7-12.el5_1.2.s390x.rpm File outdated by: RHBA-2013:0779 |
MD5: 1d152666787b8ee04b42d3e50f999888 |
| x86_64: | |
| device-mapper-multipath-0.4.7-12.el5_1.2.x86_64.rpm File outdated by: RHBA-2013:0779 |
MD5: 4d2fe1305a718baa281bcf2041a299be |
| kpartx-0.4.7-12.el5_1.2.x86_64.rpm File outdated by: RHBA-2013:0779 |
MD5: 42b4b48586fc2eb4c2300580b539c566 |
| Red Hat Enterprise Linux Desktop (v. 5 client) | |
| SRPMS: | |
| device-mapper-multipath-0.4.7-12.el5_1.2.src.rpm File outdated by: RHBA-2008:0219 |
MD5: 51fe3eda10fa75e17af3a5f4dbe171d8 |
| IA-32: | |
| device-mapper-multipath-0.4.7-12.el5_1.2.i386.rpm File outdated by: RHBA-2013:0779 |
MD5: 1431d646b9ff400192813c4152b1b7dd |
| kpartx-0.4.7-12.el5_1.2.i386.rpm File outdated by: RHBA-2013:0779 |
MD5: 0ffb24b1b96770b7a18f06770a142e39 |
| x86_64: | |
| device-mapper-multipath-0.4.7-12.el5_1.2.x86_64.rpm File outdated by: RHBA-2013:0779 |
MD5: 4d2fe1305a718baa281bcf2041a299be |
| kpartx-0.4.7-12.el5_1.2.x86_64.rpm File outdated by: RHBA-2013:0779 |
MD5: 42b4b48586fc2eb4c2300580b539c566 |
| Red Hat Enterprise Linux EUS (v. 5.1.z server) | |
| SRPMS: | |
| device-mapper-multipath-0.4.7-12.el5_1.2.src.rpm File outdated by: RHBA-2008:0219 |
MD5: 51fe3eda10fa75e17af3a5f4dbe171d8 |
| IA-32: | |
| device-mapper-multipath-0.4.7-12.el5_1.2.i386.rpm File outdated by: RHBA-2008:0219 |
MD5: 1431d646b9ff400192813c4152b1b7dd |
| kpartx-0.4.7-12.el5_1.2.i386.rpm File outdated by: RHBA-2008:0219 |
MD5: 0ffb24b1b96770b7a18f06770a142e39 |
| IA-64: | |
| device-mapper-multipath-0.4.7-12.el5_1.2.ia64.rpm File outdated by: RHBA-2008:0219 |
MD5: f95967c56ca0169453e90485a5405167 |
| kpartx-0.4.7-12.el5_1.2.ia64.rpm File outdated by: RHBA-2008:0219 |
MD5: c1f7add82b412a05f95dfe61639c528b |
| PPC: | |
| device-mapper-multipath-0.4.7-12.el5_1.2.ppc.rpm File outdated by: RHBA-2008:0219 |
MD5: 36a9e46bd9041d204f1eeb56e14a306d |
| kpartx-0.4.7-12.el5_1.2.ppc.rpm File outdated by: RHBA-2008:0219 |
MD5: f52d5739d3d9d5a3df3669d17cde8b59 |
| s390x: | |
| device-mapper-multipath-0.4.7-12.el5_1.2.s390x.rpm File outdated by: RHBA-2008:0219 |
MD5: e1b6507d2dcacc069c80bff6606f6585 |
| kpartx-0.4.7-12.el5_1.2.s390x.rpm File outdated by: RHBA-2008:0219 |
MD5: 1d152666787b8ee04b42d3e50f999888 |
| x86_64: | |
| device-mapper-multipath-0.4.7-12.el5_1.2.x86_64.rpm File outdated by: RHBA-2008:0219 |
MD5: 4d2fe1305a718baa281bcf2041a299be |
| kpartx-0.4.7-12.el5_1.2.x86_64.rpm File outdated by: RHBA-2008:0219 |
MD5: 42b4b48586fc2eb4c2300580b539c566 |
| (The unlinked packages above are only available from the Red Hat Network) | |
Bugs fixed (see bugzilla for more information)
426287 - bindings file location is problematic for certain configurations
428338 - [NetApp-S 5.2 bug] RHEL 5.1 root device multipathed host freezes during FCP path faults
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/