All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philipp Niemann <niemann@dimdi.de>
To: dm-devel@redhat.com
Subject: Re: Multipathing hints request
Date: Fri, 22 Jul 2005 14:09:55 +0200	[thread overview]
Message-ID: <20050722120955.GL4240@pan.dimdi.de> (raw)
In-Reply-To: <20050722095828.GA13294@averon.dyndns.org>

Well, almost at it.

On Fri, 22.07.2005-11:58:28 +0200, Christophe Varoqui wrote:
> hardware_handler and features params must be in the devices {} section, not in multipaths {}.

I changed the settings in /etc/multipath.conf again, as you advised.
Here is it:

# Begin of /etc/multipath.conf
defaults {
        multipath_tool  "/sbin/multipath -v 0 -S"
        udev_dir        /dev
        polling_interval 10
        default_selector        "round-robin 0"
        default_path_grouping_policy    failover
        default_getuid_callout  "/sbin/scsi_id -g -u -s /block/%n"
        default_prio_callout    "/bin/false"
        default_features        "0"
}
multipaths {
        multipath {
                wwid                    360060160200161a037f90d75dfca84f7
                alias                   416L3
                path_grouping_policy    failover
                path_selector           "round-robin 0"
        }
}
devices {
        device {
                vendor                  "DGC     "
                product                 "RAID 5          "
                path_grouping_policy    group_by_serial
                getuid_callout          "/sbin/scsi_id -g -u -s /block/%n"
                path_checker            emc_clariion
                path_selector           "round-robin 0"
                features                "0"
                hardware_handler        "1 emc"
        }
}
# End of /etc/multipath.conf

I figured out that the vendor value must be exactly 8 characters long.

> Also, pgpolicy is best set to group_by_serial with Clariion hw.
> You'll see it produce same grouping than failover in your case.

Hm, doesn't look the same here. It again leaves me with only one
priority group. So I stick to failover for now.

What different features are available? I just managed to freeze my
network conn (at least, haven't checked the host yet) by adding "1
queue_if_no_path" as used with the compaq entry in the examples.

I didn't manage to get failover to work, yet. Am I correct in assuming
that the multipathd daemon is only needed for path recovery? Because I
have problems getting that one to react to signals properly.

Right, gonna check what happend to the machine.
CU,
Philipp
-- 
Philipp Niemann                                       DIMDI
Abteilung D / AG D4
Peripherie / UNIX-Systembetreuer     Waisenhausgasse 36-38a
Tel. : 0221/4724-281                            50676 Koeln

  reply	other threads:[~2005-07-22 12:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-21 14:31 Multipathing hints request Philipp Niemann
2005-07-21 18:31 ` christophe varoqui
2005-07-22  8:37   ` Philipp Niemann
2005-07-22  9:58     ` Christophe Varoqui
2005-07-22 12:09       ` Philipp Niemann [this message]
2005-07-24 20:02         ` Lars Marowsky-Bree
2005-07-25 13:02           ` Philipp Niemann

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=20050722120955.GL4240@pan.dimdi.de \
    --to=niemann@dimdi.de \
    --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.