Linux Device Mapper development
 help / color / mirror / Atom feed
From: Konrad Rzeszutek <konrad@virtualiron.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: RE: Temporarily squelching multipathd errors
Date: Wed, 26 Nov 2008 12:43:18 -0500	[thread overview]
Message-ID: <20081126174317.GA19425@mars.virtualiron.com> (raw)
In-Reply-To: <65F9ACC78BD8304BAAEB817634C62D4C06EAFB63@AUSMAIL01.americas.ppdi.local>

On Fri, Nov 21, 2008 at 01:54:01PM -0600, Daniel Keisling wrote:
> I am still getting multipath errors when unpresenting and presenting
> LUNs.  I've traced it down to getting path failures everytime I either
> remove or add a LUN to the system.  The strange thing is that I get path
> errors for maps that aren't related to the LUNs I am deleting or adding.
> In this case, I am deleting the LUN with the map 'mpath18,' but other
> maps complain whenever the LUN is deleted:
> 
> Nov 21 13:47:05 ausracdbd01 multipathd: checker failed path 67:208 in
> map orabackup_hs
> Nov 21 13:47:05 ausracdbd01 kernel: device-mapper: multipath: Failing
> path 67:208.
> Nov 21 13:47:08 ausracdbd01 multipathd: checker failed path 70:160 in
> map mpath18
> Nov 21 13:47:08 ausracdbd01 kernel: device-mapper: multipath: Failing
> path 70:160.
> Nov 21 13:47:09 ausracdbd01 multipathd: checker failed path 69:0 in map
> orabackup_hs
> Nov 21 13:47:09 ausracdbd01 kernel: device-mapper: multipath: Failing
> path 69:0.
> Nov 21 13:47:10 ausracdbd01 multipathd: checker failed path 65:192 in
> map ph1d
> Nov 21 13:47:10 ausracdbd01 kernel: device-mapper: multipath: Failing
> path 65:192.
> Nov 21 13:47:10 ausracdbd01 multipathd: checker failed path 65:224 in
> map limsd
> Nov 21 13:47:10 ausracdbd01 kernel: device-mapper: multipath: Failing
> path 65:224.
> Nov 21 13:47:10 ausracdbd01 multipathd: checker failed path 65:240 in
> map limsd_arch
> 

Can you attach the 'multipath -ll' output? Run the program before
you delete/add the LUNs and after, please.

How do you delete/add the LUNs? Are you re-using the LUN number, or are you
actually deleting a LUN, deleting the block device as well, and then
when adding (with a new LUN number higher than the deleted one), rescanning 
the SCSI host channel to get the new block device for the LUN?

  reply	other threads:[~2008-11-26 17:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-19  8:27 Temporarily squelching multipathd errors Christophe Varoqui
2008-10-30 15:48 ` Daniel Keisling
2008-10-30 16:15   ` Domenico Viggiani
2008-11-21 19:54     ` Daniel Keisling
2008-11-26 17:43       ` Konrad Rzeszutek [this message]
2009-01-16 20:59         ` Daniel Keisling
     [not found]         ` <65F9ACC78BD8304BAAEB817634C62D4C07441224@AUSMAIL01.americas.ppdi.local>
2009-01-16 21:28           ` Konrad Rzeszutek
2009-01-16 21:52             ` Daniel Keisling
2009-01-19 15:07               ` Konrad Rzeszutek

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=20081126174317.GA19425@mars.virtualiron.com \
    --to=konrad@virtualiron.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox