From: Martin Wilck <mwilck@suse.com>
To: dm-devel@redhat.com
Subject: Re: [multipath-tools] [BUG] segfault in uev_update_path
Date: Wed, 29 Mar 2017 23:22:42 +0200 [thread overview]
Message-ID: <1490822562.10580.9.camel@suse.com> (raw)
In-Reply-To: <20170328164221.GN3421@octiron.msp.redhat.com>
On Tue, 2017-03-28 at 11:42 -0500, Benjamin Marzinski wrote:
> Now the question is, what to we do if the path changes wwid, but it's
> not part of a multipath device yet. We could simply print a warning
> message that the wwid has changed, and allow it to happen, since
> there's
> no multipath device currently using the LUN. However, I have seen
> cases
> where multiple LUNs that have already been discovered by a node get
> unmapped, and all the unmapped LUNs from a device get the same
> ID_SERIAL
> value in the uevent for the mapping change. This would cause
> find_multipaths to create a multipath device that includes all of
> these
> unmapped devices, which is clearly wrong.
and in that siutation there'd be no way to detect that these are
unmapped LUNs which don't qualify as paths for a multipath device?
Regards
Martin
--
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
next prev parent reply other threads:[~2017-03-29 21:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-23 9:17 [multipath-tools] [BUG] segfault in uev_update_path Shichangkuo
2017-03-28 16:42 ` Benjamin Marzinski
2017-03-29 21:22 ` Martin Wilck [this message]
2017-04-04 23:33 ` 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=1490822562.10580.9.camel@suse.com \
--to=mwilck@suse.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 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.