From: Hannes Reinecke <hare@suse.de>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: Multipath issues with kernel device errors
Date: Wed, 29 Aug 2007 08:14:39 +0200 [thread overview]
Message-ID: <46D50ECF.6020701@suse.de> (raw)
In-Reply-To: <1188338656.12737.18.camel@linuxchandra>
Chandra Seetharaman wrote:
> You do not have the latest table.
> Try with the table below (converted from 0.4.8 version's hwtable.c)
> devices {
> device {
> vendor "COMPAQ"
> product "MSA1000"
> path_grouping_policy group_by_prio
> path_checker tur
> prio_callout "/sbin/mpath_prio_alua /dev/%n"
> getuid_callout "/sbin/scsi_id -g -u -s /block/%n"
> failback immediate
> }
> }
>
Errm. Not quite. My sources indicate that this machine
runs the older active/passive firmware, which requires
the 'hp_sw' hardware handler to run properly.
So better use this:
devices {
device {
vendor "COMPAQ"
product "MSA1000"
hardware_handler "1 hp_sw"
path_grouping_policy group_by_prio
path_checker hp_sw
prio_callout "/sbin/mpath_prio_hp_sw /dev/%n"
getuid_callout "/sbin/scsi_id -g -u -s /block/%n"
failback manual
}
}
if mpath_prio_hp_sw is missing complain to Ben Marzinski :-)
Alternatively you can use
path_grouping_policy failover
and omit the prio_callout altogether. But then only one path
per SP are used.
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Markus Rex, HRB 16746 (AG Nürnberg)
next parent reply other threads:[~2007-08-29 6:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8CED8CEBA23FC0409E1A3009F7F47BE502471065@exchange.g2switchworks.com>
[not found] ` <1188333723.12737.7.camel@linuxchandra>
[not found] ` <8CED8CEBA23FC0409E1A3009F7F47BE502471086@exchange.g2switchworks.com>
[not found] ` <1188338656.12737.18.camel@linuxchandra>
2007-08-29 6:14 ` Hannes Reinecke [this message]
2007-08-29 13:29 ` Multipath issues with kernel device errors Jeffry Bilder
2007-08-29 16:58 ` Jeffry Bilder
2007-10-04 18:49 ` Dave Wysochanski
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=46D50ECF.6020701@suse.de \
--to=hare@suse.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.