From: Chandra Seetharaman <sekharan@us.ibm.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: Sun StorageTek 2530 and dm?
Date: Mon, 24 Aug 2009 13:24:16 -0700 [thread overview]
Message-ID: <1251145456.24406.16.camel@chandra-ubuntu> (raw)
In-Reply-To: <20090824205529.6b78aa3a@pc-jsosic.srce.hr>
I do not think adding that patch would not resolve the=problem you are
seeing.
On Mon, 2009-08-24 at 20:55 +0200, Jakov Sosic wrote:
> On Mon, 24 Aug 2009 11:38:18 -0700
> Chandra Seetharaman <sekharan@us.ibm.com> wrote:
>
> >
> > You need to have a stanza similar to following one for your device
> > in /etc/multipath.conf
> > --------------------
> > devices {
> > device {
> > vendor "IBM"
> > product "1815"
> > path_grouping_policy group_by_prio
> > hardware_handler "1 rdac"
> > path_checker rdac
> > failback immediate
> > no_path_retry queue
> > prio_callout "/sbin/mpath_prio_tpc /dev/%n"
> > }
> > }
> > ---------------------
>
> Hi!
>
> Yes, I've added that section, and still I get these:
>
> Aug 24 20:47:38 node03 multipathd: 8:16: reinstated
> Aug 24 20:47:38 node03 multipathd: 8:64: reinstated
> Aug 24 20:47:38 node03 multipathd: qd: remaining active paths: 2
> Aug 24 20:47:38 node03 multipathd: qd: switch to path group #2
> Aug 24 20:47:38 node03 multipathd: qd: switch to path group #2
> Aug 24 20:47:38 node03 multipathd: dm-0: add map (uevent)
> Aug 24 20:47:38 node03 multipathd: dm-0: devmap already registered
> Aug 24 20:47:47 node03 kernel: sd 1:0:1:0: queueing MODE_SELECT command.
> Aug 24 20:47:48 node03 openais[5236]: [CMAN ] lost contact with quorum
> device
> Aug 24 20:47:58 node03 multipathd: dm-0: add map (uevent)
> Aug 24 20:47:58 node03 multipathd: dm-0: devmap already registered
> Aug 24 20:47:58 node03 multipathd: 8:64: mark as failed
> Aug 24 20:47:58 node03 kernel: end_request: I/O error, dev sde, sector 8
> Aug 24 20:47:58 node03 multipathd: qd: remaining active paths: 1
> Aug 24 20:47:58 node03 kernel: device-mapper: multipath: Failing path
> 8:64.
> Aug 24 20:47:58 node03 kernel: sd 1:0:0:0: queueing MODE_SELECT
> command.
> Aug 24 20:48:07 node03 multipathd: 8:64: reinstated
> Aug 24 20:48:07 node03 multipathd: qd: remaining active paths: 2
> Aug 24 20:48:07 node03 multipathd: qd: switch to path group #2
> Aug 24 20:48:07 node03 multipathd: qd: switch to path group #2
> Aug 24 20:48:07 node03 multipathd: dm-0: add map (uevent)
> Aug 24 20:48:07 node03 multipathd: dm-0: devmap already registered
> Aug 24 20:48:07 node03 kernel: sd 1:0:1:0: queueing MODE_SELECT command.
> Aug 24 20:48:17 node03 multipathd: 8:64: reinstated
>
>
>
>
> So it does not work ok :(
>
> So far I've tried:
>
> 1. defaults with initiators set to "Linux"
> one path constantly failed
> 2. AVT with initiators set to "Solaris (with Veritas DMP or other)"
> multipath flopping constantly - every 20 minutes there is enter in
> main log about path failing
> 3. RDAC with initiators set to "Linux"
> logs filled with messages like these show up in the message,
> constantly flip/flopping
>
> I haven't patch scsi_dh_rdac because I don't know how to add support
> for "SUN"/"LCSM100_S", and although I could figure it out, I'm not
> really a fan of compiling the kernel if it is not absolutely necessary.
>
>
next prev parent reply other threads:[~2009-08-24 20:24 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-23 19:05 Sun StorageTek 2530 and dm? Jakov Sosic
2009-08-23 19:34 ` Jakov Sosic
2009-08-24 15:41 ` Charlie Brady
2009-08-24 15:48 ` Jakov Sosic
2009-08-24 16:00 ` Jakov Sosic
2009-08-24 18:38 ` Chandra Seetharaman
2009-08-24 18:55 ` Jakov Sosic
2009-08-24 20:24 ` Chandra Seetharaman [this message]
2009-08-24 20:37 ` Jakov Sosic
2009-08-24 20:44 ` Chandra Seetharaman
2009-08-24 20:53 ` Jakov Sosic
2009-08-24 21:06 ` Chandra Seetharaman
2009-08-24 21:37 ` Jakov Sosic
2009-08-24 21:54 ` Chandra Seetharaman
2009-08-24 22:58 ` Charlie Brady
2009-08-24 23:09 ` Jakov Sosic
2009-08-24 23:18 ` Chandra Seetharaman
2009-08-24 23:22 ` Jakov Sosic
2009-08-24 23:11 ` Chandra Seetharaman
2009-08-24 23:11 ` Jakov Sosic
2009-08-24 18:29 ` Jakov Sosic
2009-08-24 18:48 ` Chandra Seetharaman
2009-08-24 18:59 ` Jakov Sosic
2009-08-24 20:24 ` Chandra Seetharaman
2009-08-24 20:36 ` Jakov Sosic
2009-08-24 20:57 ` Chandra Seetharaman
2009-08-24 21:14 ` Jakov Sosic
2009-08-24 21:41 ` Chandra Seetharaman
2009-08-24 21:53 ` Jakov Sosic
2009-08-24 23:07 ` Chandra Seetharaman
2009-08-24 23:13 ` Jakov Sosic
2009-08-25 0:06 ` Jakov Sosic
2009-08-25 0:18 ` Chandra Seetharaman
2009-08-25 3:36 ` Charlie Brady
2009-08-25 18:07 ` Chandra Seetharaman
2009-08-25 19:21 ` Charlie Brady
2009-08-25 19:55 ` Chandra Seetharaman
2009-08-25 20:51 ` Charlie Brady
2009-08-25 21:09 ` Jakov Sosic
2009-08-26 21:57 ` Charlie Brady
2009-08-26 22:31 ` Chandra Seetharaman
2009-08-26 23:01 ` Charlie Brady
2009-08-27 8:30 ` Jakov Sosic
2009-08-27 16:02 ` Charlie Brady
2009-08-27 19:11 ` Chandra Seetharaman
2009-08-24 21:19 ` Jakov Sosic
2009-08-24 21:43 ` Chandra Seetharaman
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=1251145456.24406.16.camel@chandra-ubuntu \
--to=sekharan@us.ibm.com \
--cc=dm-devel@redhat.com \
--cc=sekharan@linux.vnet.ibm.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.