All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Wilck <mwilck@suse.com>
To: dm-devel@redhat.com, liuqing@huayun.com
Subject: Re: Multipath ID not equal to LUN scsi ID
Date: Mon, 10 Jul 2017 15:55:12 +0200	[thread overview]
Message-ID: <1499694912.29151.12.camel@suse.com> (raw)
In-Reply-To: <2017071017581348809421@huayun.com>

On Mon, 2017-07-10 at 17:58 +0800, liuqing@huayun.com wrote:
> Dear list,
> We have a FC storage and using multipathd to manager the FC paths.
> I've met an issue in this environment. The following is how to
> recreate the issue.

Which version of multipath-tools have you been using? Could you please
run multipathd with "-v 3" and provide the logs of the procedure below?

Is there a specific reason why you are using the "getuid_callout"
option rather than "uid_attribute"?

Regards,
Martin

> 
> =======
> 1. Map a LUN to host with LUN ID 0,
> 2. rescan fc_host, a new path will be found by multipath.
> 3. Unmap LUN 0.  path will failed as following.
> [root@localhost sys]# multipath -ll
> Jul 10 18:41:50 | sdp: couldn't get asymmetric access state
> Jul 10 18:41:50 | sdq: couldn't get asymmetric access state
> 36005076300810eadf800000000000156 dm-3 IBM,2145
> size=8.0G features='2 queue_if_no_path retain_attached_hw_handler' hw
> handler='1 alua' wp=rw
> |-+- policy='service-time 0' prio=0 status=enabled
> | `- 2:0:0:0 sdp 8:240 failed faulty running
> `-+- policy='service-time 0' prio=0 status=enabled
>   `- 2:0:1:0 sdq 65:0  failed faulty running
> 4. Map another LUN which have different ID_SERIAL but with the same
> LUN ID(0). Multipath(check_path function) will set the paths up, tur
> checker will successfully test the LUN. 
> [root@localhost sys]# /lib/udev/scsi_id --whitelisted --replace-
> whitespace --device=/dev/mapper/36005076300810eadf800000000000156
> 36005076300810eadf800000000000155
>  I think this is not right, although I do not remove the device by
> 'echo 1> /sys/block/sdp/device/delete'. A multipath is identified by
> LUN scsi ID, in this situation the multipath
> ID is not equal to LUN scsi ID. And if I add the previous LUN back,
> the paths will also be added to that multipath
> id(36005076300810eadf800000000000156).
> 
> Any suggestion on how to make it create a new node in /dev with
> correct scsi ID? Thanks.
> 
> 
> ===========
> [root@localhost sys]# cat /etc/multipath.conf
> defaults {
>     features "0"
>     no_path_retry           queue
>     getuid_callout "/lib/udev/scsi_id --whitelisted --replace-
> whitespace --device=/dev/%n"
> }
> blacklist {
>     devnode "sd[a-m]"
> }
> 
> liuqing@huayun.com
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel

-- 
Dr. Martin Wilck <mwilck@suse.com>, Tel. +49 (0)911 74053 2107
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)

--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel

  parent reply	other threads:[~2017-07-10 13:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-10  9:58 Multipath ID not equal to LUN scsi ID liuqing
2017-07-10 13:02 ` Steffen Maier
2017-07-10 13:55 ` Martin Wilck [this message]
2017-07-11  1:32   ` liuqing
  -- strict thread matches above, loose matches on Subject: below --
2017-07-11  3:49 liuqing
2017-07-11  9:07 ` Steffen Maier
2017-07-11  9:40   ` Steffen Maier
2017-07-12  2:14 liuqing

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=1499694912.29151.12.camel@suse.com \
    --to=mwilck@suse.com \
    --cc=dm-devel@redhat.com \
    --cc=liuqing@huayun.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.