From: Josef Whiter <jwhiter@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: Multipathing using device mapper howto?
Date: Fri, 28 Oct 2005 16:36:20 -0400 [thread overview]
Message-ID: <43628BC4.5010909@redhat.com> (raw)
In-Reply-To: <43628C96.2090605@trilegiant.com>
Bruen, Mark wrote:
> I'm just beginning to look at device mapper to multipath SAN luns.
> I've been searching for some time and can't find a simple reference on
> how to create the multipathed devices from the same luns presented to
> two or more HBA paths. Is there a source for that information?
> Thanks.
> -Mark
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
I don't know of any external sources, but the quick and dirty way is to
first fdisk your /dev/sd devices, and then edit your /etc/multipath.conf
file and comment out hte lines
devnode_blacklist {
devnode "*"
}
and then uncomment out the lines
defaults {
multipath_tool "/sbin/multipath -v0"
udev_dir /dev
polling_interval 10
default_selector "round-robin 0"
default_path_grouping_policy multibus
default_getuid_callout "/sbin/scsi_id -g -u -s /block/%n"
default_prio_callout "/bin/true"
default_features "0"
rr_wmin_io 100
failback immediate
}
Then reboot, and it should work. You're devices should show up in
/dev/dm-#, then all you want to do is do a kpartx -a on /dev/dm-# and it
will create a new /dev/dm-#+1 for the partitions (ie if my disk was
/dev/dm-0 and i had one partition, and i ran kpartx -a i would get
/dev/dm-1. its equivalent of /dev/sda and /dev/sda1). Thank you,
Josef
--
Josef Whiter, RHCE
Global Support Services
Red Hat, Inc.
919-754-3700 x44429
prev parent reply other threads:[~2005-10-28 20:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-28 20:39 Multipathing using device mapper howto? Bruen, Mark
2005-10-28 20:36 ` Josef Whiter [this message]
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=43628BC4.5010909@redhat.com \
--to=jwhiter@redhat.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.