From: Chandra Seetharaman <sekharan@us.ibm.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: Configuring multipath for root device
Date: Wed, 19 Dec 2007 13:18:13 -0800 [thread overview]
Message-ID: <1198099093.26366.32.camel@linuxchandra> (raw)
In-Reply-To: <110b17190712191302o60d521eaj693410c26d07c1ad@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 779 bytes --]
I am working on a multipath usage document. Attached is the installation
section of that document.
Note that it is written for RHEL5 U1 and SLES10 SP1.
Good Luck,
chandra
On Wed, 2007-12-19 at 13:02 -0800, Pradipmaya Maharana wrote:
> Hi All,
>
> Is there a process/document that talks about how to configure
> root/boot device for multipath?
>
> Thanks and Regards,
> Pradipmaya.
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
--
----------------------------------------------------------------------
Chandra Seetharaman | Be careful what you choose....
- sekharan@us.ibm.com | .......you may get it.
----------------------------------------------------------------------
[-- Attachment #2: f1 --]
[-- Type: text/plain, Size: 2970 bytes --]
4.1. Installation instructions for SLES10
Note: This is tested on SLES10 SP1. If you have any other version, your
mileage may vary.
1. Install the OS in a device that has multiple paths. Make sure the
root device's "Mount by" option is set to "Device by-id" (this option is
available under "expert partitioner" as "fstab options").
2. Complete the installation. Let the system boot up in multiuser mode.
Make sure the root device, swap device are all referenced by their by-id
device node entries instead of /dev/sd* type names. If they are not, fix
them first.
3. Once booted, update /etc/multipath.conf If you have to make changes
to /etc/multipath.conf, make the changes.
Note: the option "user_friendly_names" is not supported by initrd.
So, if you have user_friendly_names in your /etc/multipath.conf file,
comment it for now, you can uncomment it later.
4. Enable multipathing by running the following commands
* chkconfig boot.multipath on
* chkconfig multipathd on
5. Add multipath module to initrd
Edit the file /etc/sysconfig/kernel and add "dm-multipath" to
INITRD_MODULES". Note: If your storage devices needs a hardware handler,
add the corresponding module to INITRD_MODULES, in addition to
"dm-multipath". For example add "dm-rdac" and "dm-multipath" to support
IBM's DS4K storage devices
6. Run mkinitrd
Note: You can uncomment the user friendly name if you have commented it above.
7. Reboot
The system will come up with the root disk on a multipathed device.
Note: You can switch off multipathing to the root device by adding
multipath=off to the kernel command line.
4.2. Installation instructions for RHEL5
Note: This is tested on RHEL5 U1. If you have any other version, your
mileage may vary.
1. Start the installation with the kernel command line "linux mpath"
* You will see multipathed devices (/dev/mapper/mpath*) as
* installation devices.
2. Finish the installation.
3. Reboot.
* If your boot device does not need multipath.conf and does not
* have a special hardware handler, then you are done. If you have
* either of these, follow the steps below.
4. Once booted, update multipath.conf file, if needed.
5. Run mkinitrd, if you need a hardware handler, add it to initrd with --with option.
* # mkinitrd /boot/initrd.final.img --with=dm-rdac
6. Replace the initrd in your grub.conf/lilo.conf/yaboot.conf with the
newly built initrd.
7. Reboot.
The system will come up with the root disk on a multipathed device.
Note: You can switch off multipathing to the root device by adding
multipath=off to the kernel command line. Note: By default, RedHat disables
dm-multipath by blacklisting all devices in /etc/multipath.conf. It just
excludes your root device. If you do not see your other multipath devices
through "multipath -ll", then check and fix the blacklist in
/etc/multipath.conf
[-- Attachment #3: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2007-12-19 21:18 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-19 21:02 Configuring multipath for root device Pradipmaya Maharana
2007-12-19 21:18 ` Chandra Seetharaman [this message]
2007-12-19 21:26 ` Pradipmaya Maharana
2007-12-20 16:46 ` Pradipmaya Maharana
2007-12-21 16:26 ` Benjamin Marzinski
2007-12-21 19:06 ` Pradipmaya Maharana
2008-01-07 7:38 ` Hannes Reinecke
2008-01-07 18:11 ` Pradipmaya Maharana
2008-01-07 20:19 ` Pradipmaya Maharana
2008-01-07 20:28 ` malahal
2008-01-07 20:40 ` Pradipmaya Maharana
2008-01-07 20:46 ` malahal
2008-01-07 20:56 ` Pradipmaya Maharana
2008-01-07 21:57 ` malahal
2008-01-08 0:13 ` Pradipmaya Maharana
2008-01-08 0:29 ` malahal
2008-01-08 7:17 ` Hannes Reinecke
2008-01-16 2:25 ` Pradipmaya Maharana
2008-01-16 2:32 ` Chandra Seetharaman
2008-01-16 17:36 ` malahal
2008-01-16 18:49 ` Pradipmaya Maharana
2008-01-17 20:21 ` malahal
2008-01-17 20:38 ` Pradipmaya Maharana
2008-01-18 21:52 ` Pradipmaya Maharana
2008-01-16 4:24 ` Romanowski, John (OFT)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1198099093.26366.32.camel@linuxchandra \
--to=sekharan@us.ibm.com \
--cc=dm-devel@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.