All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ray Van Dolson <rvandolson@esri.com>
To: dm-devel@redhat.com
Cc: open-iscsi@googlegroups.com
Subject: multipathd: sdc: readsector0 checker reports path is down
Date: Thu, 8 Jan 2009 11:31:38 -0800	[thread overview]
Message-ID: <20090108193137.GA3953@esri.com> (raw)

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

My initial impression is that sdc is likely the "passive" path (for
failover) whereas sdd is my active path:

  # multipath -ll
  sdc: checker msg is "readsector0 checker reports path is down"
  mpath2 (36001ec9000f338370000000000000000) dm-2 DELL,Universal Xport
  [size=20M][features=0][hwhandler=0]
  \_ round-robin 0 [prio=0][enabled]
   \_ 4:0:0:31 sdf 8:80  [active][ready] 
  mpath1 (36001ec9000f337dd0000000000000000) dm-1 DELL,Universal Xport
  [size=20M][features=0][hwhandler=0]
  \_ round-robin 0 [prio=0][enabled]
   \_ 3:0:0:31 sde 8:64  [active][ready] 
  mpath0 (36001ec9000f337dd0000065b491854a4) dm-0 DELL,MD3000i
  [size=150G][features=0][hwhandler=1 rdac]
  \_ round-robin 0 [prio=3][active]
   \_ 3:0:0:0  sdd 8:48  [active][ready] 
  \_ round-robin 0 [prio=0][enabled]
   \_ 4:0:0:0  sdc 8:32  [failed][faulty]

  # iscsiadm -m discovery -t sendtargets -p 192.168.132.101:3260
  0.0.0.0:3260,1 iqn.1984-05.com.dell:powervault.6001ec9000f337dd0000000048bdc862
  0.0.0.0:3260,2 iqn.1984-05.com.dell:powervault.6001ec9000f337dd0000000048bdc862
  192.168.132.101:3260,1 iqn.1984-05.com.dell:powervault.6001ec9000f337dd0000000048bdc862
  192.168.132.102:3260,2 iqn.1984-05.com.dell:powervault.6001ec9000f337dd0000000048bdc862

  # iscsiadm -m session -P 1
  Target: iqn.1984-05.com.dell:powervault.6001ec9000f337dd0000000048bdc862
    Current Portal: 192.168.132.101:3260,1
    Persistent Portal: 192.168.132.101:3260,1
      **********
      Interface:
      **********
      Iface Name: default
      Iface Transport: tcp
      Iface Initiatorname: iqn.1994-05.com.redhat:2738e0d3bd21
      Iface IPaddress: 192.168.132.202
      Iface HWaddress: default
      Iface Netdev: default
      SID: 1
      iSCSI Connection State: LOGGED IN
      iSCSI Session State: Unknown
      Internal iscsid Session State: NO CHANGE
    Current Portal: 192.168.132.102:3260,2
    Persistent Portal: 192.168.132.102:3260,2
      **********
      Interface:
      **********
      Iface Name: default
      Iface Transport: tcp
      Iface Initiatorname: iqn.1994-05.com.redhat:2738e0d3bd21
      Iface IPaddress: 192.168.132.202
      Iface HWaddress: default
      Iface Netdev: default
      SID: 2
      iSCSI Connection State: LOGGED IN
      iSCSI Session State: Unknown
      Internal iscsid Session State: NO CHANGE

sde and sdf are the silly 20MB partition that the MD3000 creates and
I'm not using either.

My ultimate goal is to not have so many of the path is down errors
showing up in my syslog file (hundreds and hundreds of them).  I'm not
sure if their presence is normal (indicative of a passive path) or
indicative of a problem.

Also, I'm not clear as to how I should identify which target
corresponds with which drive (sdc or sdd).

Any thoughts?  I don't have direct access to the MD3000i
unfortunately... this is from a CentOS 5.2 system btw.

Ray

             reply	other threads:[~2009-01-08 19:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-08 19:31 Ray Van Dolson [this message]
     [not found] ` <20090108193137.GA3953-v48TKWNzwFw@public.gmane.org>
2009-01-08 19:56   ` [dm-devel] multipathd: sdc: readsector0 checker reports path is down 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       ` [dm-devel] " 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=20090108193137.GA3953@esri.com \
    --to=rvandolson@esri.com \
    --cc=dm-devel@redhat.com \
    --cc=open-iscsi@googlegroups.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.