From: Chandra Seetharaman <sekharan-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: device-mapper development
<dm-devel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: "open-iscsi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org"
<open-iscsi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: [dm-devel] Re: multipathd: sdc: readsector0 checker reports path is down
Date: Thu, 08 Jan 2009 12:48:36 -0800 [thread overview]
Message-ID: <1231447716.9047.29.camel@chandra-ubuntu> (raw)
In-Reply-To: <20090108201007.GA8423-v48TKWNzwFw@public.gmane.org>
On Thu, 2009-01-08 at 12:10 -0800, Ray Van Dolson wrote:
> On Thu, Jan 08, 2009 at 11:58:52AM -0800, Chandra Seetharaman wrote:
> >
> >
> > On Thu, 2009-01-08 at 11:31 -0800, Ray Van Dolson wrote:
> > > I'm still getting the hang of iSCSI and multipath, so bear with me if
> > > this is a FAQ that I've missed...
> > >
> > > I have a host attaching to an MD3000i via iSCSI/dm-multipath that is
> > > working but showing a lot of the following errors in syslog:
> > >
> > > multipathd: sdc: readsector0 checker reports path is down
> > you should be using the rdac path checker. In addition to that you
> > should be using rdac hardware handler and tpc priority checker.
> >
> > If you have and entry for your MD3000i in /etc/multipath.conf, replace
> > it with this. If not add this
> > -------------------
> > devices {
> > device {
> > vendor "DELL"
> > product "MD3000i"
> > hardware_handler "1 rdac"
> > path_checker rdac
> > failback immediate
> > path_grouping_policy group_by_prio
> > no_path_retry queue
> > prio_callout "/sbin/mpath_prio_tpc /dev/%n"
> > }
> > }
> > ---------------------
> >
> > After this change you have to do:
> > - multipath -F
> > - service multipathd restart
> >
> > Let me know how it goes.
>
> This appears to have done the trick. So, I guess the default path
> checker is readsector0 and rdac is another method -- I imagine it
> directly talks to my MD3000i to determine path status?
Yes, it sends a C9 inquiry to the storage controller and determines the
state.
>
> > >
> > > My initial impression is that sdc is likely the "passive" path (for
> > > failover) whereas sdd is my active path:
> >
> > yes.
>
> Thanks much!
>
> Ray
>
> --
> dm-devel mailing list
> dm-devel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
> https://www.redhat.com/mailman/listinfo/dm-devel
prev parent reply other threads:[~2009-01-08 20:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-08 19:31 multipathd: sdc: readsector0 checker reports path is down Ray Van Dolson
[not found] ` <20090108193137.GA3953-v48TKWNzwFw@public.gmane.org>
2009-01-08 19:56 ` [dm-devel] " Konrad Rzeszutek
2009-01-08 20:16 ` Ray Van Dolson
2009-01-08 19:58 ` Chandra Seetharaman
2009-01-08 20:10 ` Ray Van Dolson
[not found] ` <20090108201007.GA8423-v48TKWNzwFw@public.gmane.org>
2009-01-08 20:48 ` Chandra Seetharaman [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=1231447716.9047.29.camel@chandra-ubuntu \
--to=sekharan-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
--cc=dm-devel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=open-iscsi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
/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.