From: Martin Wilck <martin.wilck@suse.com>
To: "bblock@linux.ibm.com" <bblock@linux.ibm.com>
Cc: "dm-devel@redhat.com" <dm-devel@redhat.com>,
"wucy11@chinatelecom.cn" <wucy11@chinatelecom.cn>
Subject: Re: [dm-devel] [PATCH 2/2] multipathd: add recheck_wwid_time option to verify the path wwid
Date: Wed, 10 Feb 2021 19:57:08 +0000 [thread overview]
Message-ID: <cf6a5910c2ab53e710c6692c574b3e2d3b78a4bb.camel@suse.com> (raw)
In-Reply-To: <YCQhW4uHx4j+xXmL@t480-pf1aa2c2.linux.ibm.com>
On Wed, 2021-02-10 at 19:09 +0100, Benjamin Block wrote:
>
> Yeah, just for reference, I saw this happening in practice when
> something with the LU mapping changed on IBM storage - IIRC I saw it
> with capacity changes. You end up in this code in the kernel:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/scsi/scsi_error.c?id=92bf22614b21a2706f4993b278017e437f7785b3#n416
>
> And from there you ought to get an uevent for the sdev.
>
> The WWID in sysfs might still be wrong though AFAIK. The kernel seems
> to
> ignore the UA after it delivered the uevent.
Right.
We could trigger a device rescan if such an event was received. Could
be done from udev rules, or even from multipathd itself.
Thanks,
Martin
--
Dr. Martin Wilck <mwilck@suse.com>, Tel. +49 (0)911 74053 2107
SUSE Software Solutions Germany GmbH
HRB 36809, AG Nürnberg GF: Felix Imendörffer
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
next prev parent reply other threads:[~2021-02-10 19:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 5:19 [dm-devel] [PATCH 0/2] Handle remapped LUNs better Benjamin Marzinski
2021-02-09 5:19 ` [dm-devel] [PATCH 1/2] libmultipath: fix use-after-free in uev_add_path Benjamin Marzinski
2021-02-09 20:57 ` Martin Wilck
2021-02-09 5:19 ` [dm-devel] [PATCH 2/2] multipathd: add recheck_wwid_time option to verify the path wwid Benjamin Marzinski
2021-02-09 22:19 ` Martin Wilck
2021-02-10 18:09 ` Benjamin Block
2021-02-10 19:57 ` Martin Wilck [this message]
2021-02-11 11:25 ` Benjamin Block
2021-02-11 4:48 ` Benjamin Marzinski
2021-02-11 12:14 ` Martin Wilck
2021-02-18 3:22 ` Chongyun Wu
2021-02-19 10:46 ` Martin Wilck
2021-02-27 6:02 ` Benjamin Marzinski
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=cf6a5910c2ab53e710c6692c574b3e2d3b78a4bb.camel@suse.com \
--to=martin.wilck@suse.com \
--cc=bblock@linux.ibm.com \
--cc=dm-devel@redhat.com \
--cc=wucy11@chinatelecom.cn \
/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;
as well as URLs for NNTP newsgroup(s).