From: Benjamin Marzinski <bmarzins@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: Creation of the mpath# devices
Date: Thu, 15 Nov 2007 15:29:43 -0600 [thread overview]
Message-ID: <20071115212943.GF4900@ether.msp.redhat.com> (raw)
In-Reply-To: <342d47870711151302o68e3172fn92c8c1e323812905@mail.gmail.com>
On Thu, Nov 15, 2007 at 03:02:45PM -0600, Scott Moseman wrote:
> I guess my problems are never completely eliminated... :)
>
> Setup device-mapper multipathing in RHEL 4
> http://kbase.redhat.com/faq/FAQ_51_7170.shtm
>
> Per the above KB, after the multipath daemon is configured and
> started, "The multipath -v2 command prints out multipathed paths that
> show which devices are multipathed. If the command does not print
> anything out, ensure that all SAN connections are set up properly and
> the system is multipathed."
>
> # multipath -v2
>
> I get nothing on my server. Although here's what I do get.
>
> # multipath -l
> 30690a018f015191a6472441d1500f057
> [size=4 GB][features="0"][hwhandler="0"]
> \_ round-robin 0 [active]
> \_ 3:0:0:0 sdc 8:32 [active][ready]
> \_ round-robin 0 [enabled]
> \_ 1:0:1:0 sdb 8:16 [active][ready]
>
> # multipath -v3
> --- snipped ---
> #
> # all paths in cache :
> #
> 30690a018f015191a6472441d1500f057 1:0:1:0 sdb 8:16 [active][ready] EQLOGIC /
> 30690a018f015191a6472441d1500f057 3:0:0:0 sdc 8:32 [active][ready] EQLOGIC /
> hda blacklisted
> sda blacklisted
> --- snipped ---
>
> What am I missing? As far as I can tell, I'm following the RHEL KB
> perfectly and it's still not working as expected (although now I'm
> much farther than before!).
If you were only expecting to have /dev/sdb and /dev/sdc multipathed,
then you are fine. The problem is in the Knowledge Base article.
# multipath -v2
only prints out the multipath maps that it creates. If, as in your
case, the map already exists, it should print nothing.
# multipath -l
prints out all the existing multipath devices.
You should see the device node
/dev/mapper/30690a018f015191a6472441d1500f057
and the symbolic link
/dev/mpath/30690a018f015191a6472441d1500f057
Which you can use to access the device. If you don't like dealing with
such a cumbersome name, you can always add
user_friendly_names yes
to the defaults section of /etc/multipath.conf
-Ben
> Thanks!
> Scott
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
next prev parent reply other threads:[~2007-11-15 21:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-15 21:02 Creation of the mpath# devices Scott Moseman
2007-11-15 21:29 ` Benjamin Marzinski [this message]
2007-11-15 22:36 ` Scott Moseman
2007-11-16 13:55 ` Kevin Foote
2007-11-19 15:30 ` Scott Moseman
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=20071115212943.GF4900@ether.msp.redhat.com \
--to=bmarzins@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.