Bug 674238 - Dracut should start multipathd with the new -B option in multipathd.sh
Summary: Dracut should start multipathd with the new -B option in multipathd.sh
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: dracut
Version: 6.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Harald Hoyer
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On: 644111
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-01 06:15 UTC by Ben Marzinski
Modified: 2011-05-19 11:54 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Currently when multipath runs in the initramfs with user_friendly_names set, if it doesn't find existing mappings in /etc/multipath/bindings, it creates new ones, just like it does once the node is in normal operation. Unfortunately, these can conflict with the user_friendly_names set in the normal filesystem's /etc/multipath/bindings. dracut now starts the multipathd daemon with the new -B option, which causes multipath to treat the bindings file as read-only.
Clone Of:
Environment:
Last Closed: 2011-05-19 11:54:13 UTC
Target Upstream Version:

Attachments (Terms of Use)
Patch to add the -B option (543 bytes, patch)
2011-02-01 06:15 UTC, Ben Marzinski 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:0523 0 normal SHIPPED_LIVE dracut bug fix and enhancement update 2011-05-18 17:44:57 UTC

Description Ben Marzinski 2011-02-01 06:15:55 UTC 
Created attachment 476317 [details]
Patch to add the -B option

Currently when multipath runs in the initramfs with user_friendly_names set, if it doesn't find existing mappings in /etc/multipath/bindings, it creates new ones, just like it does once the node is in normal operation.  Unfortunately, these can conflict with the user_friendly_names set in the normal filesystem's /etc/multipath/bindings. The new -B option caused multipath to treat the bindings file as read-only.  This option should be added to the dracut multipath scripts.
Comment 3 Harald Hoyer 2011-02-16 11:30:45 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Currently when multipath runs in the initramfs with user_friendly_names set, if it doesn't find existing mappings in /etc/multipath/bindings, it creates new
ones, just like it does once the node is in normal operation.  Unfortunately, these can conflict with the user_friendly_names set in the normal filesystem's
/etc/multipath/bindings. 
dracut now starts the multipathd daemon with the new -B option, which causes multipath to treat the bindings file as read-only.
Comment 4 Jan Stodola 2011-04-29 07:52:56 UTC 
Tested on build RHEL6.1-20110427.0 with dracut-004-53.el6.noarch on s390x architecture. Root filesystem was placed on a multipath zFCP LUN. The following log comes from /init.log from initramfs:
...
+ [ -e /pre-trigger/02multipathd.sh ]
+ . /pre-trigger/02multipathd.sh
+ [ -e /etc/multipath.conf ]
+ modprobe dm-multipath
+ multipathd -B
+ [ -e /pre-trigger/10plymouth-pretrigger.sh ]
+ . /pre-trigger/10plymouth-pretrigger.sh
+ getarg rd_NO_PLYMOUTH
...

multipathd was run with the -B option.

Moving to VERIFIED.
Comment 5 errata-xmlrpc 2011-05-19 11:54:13 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0523.html
Note You need to log in before you can comment on or make changes to this bug.