From: Benjamin Marzinski <bmarzins@redhat.com>
To: Martin Wilck <martin.wilck@suse.com>
Cc: Christophe Varoqui <christophe.varoqui@opensvc.com>,
device-mapper development <dm-devel@lists.linux.dev>
Subject: Re: [PATCH 1/6] libmultipath: signal device with no table in libmp_mapinfo
Date: Thu, 21 Nov 2024 13:00:53 -0500 [thread overview]
Message-ID: <Zz91VZ3r2GUZinVj@redhat.com> (raw)
In-Reply-To: <f0bc411082a622f2cad3368be1cdc210db1fdc7a.camel@suse.com>
On Thu, Nov 21, 2024 at 09:57:28AM +0100, Martin Wilck wrote:
> On Wed, 2024-11-20 at 16:59 -0500, Benjamin Marzinski wrote:
> >
> > How would you feel about adding a parameter to do_foreach_partmaps()
> > to
> > say whether or not it should remove empty partmaps (or possibly just
> > checking if the partmap_func is remove_partmaps). Your argument
> > makes
> > sense when you are removing a device. But what about functions like
> > dm_cancel_remove_partmaps() and dm_rename_partmaps()? I'm not sure
> > that
> > these should automatically empty (a possibly being created) partition
> > devices.
>
> We're moving far into corner case land here :-)
>
> I think we should keep it as simple as possible. For me, that means
> that an empty partition map (with UUID matching the current mpath map)
> should be treated like any other partition map with matching UUID, no
> matter what the current operation is.
>
> There will be some situations where the outcome will be suboptimal. By
> keeping it simple, we'll at least be able to understand the outcome.
That's reasonable. I misunderstood your suggestion as asking to always
remove empty partition devices in do_foreach_partmaps(). We'd need to
make sure all the partmap_func()s work with empty devices. But that
shouldn't be too bad.
-Ben
> Martin
next prev parent reply other threads:[~2024-11-21 18:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-15 23:22 [PATCH 0/6] multipath-tools: Handle tableless DM devices Benjamin Marzinski
2024-11-15 23:22 ` [PATCH 1/6] libmultipath: signal device with no table in libmp_mapinfo Benjamin Marzinski
2024-11-19 16:39 ` Martin Wilck
2024-11-19 20:33 ` Benjamin Marzinski
2024-11-20 8:49 ` Martin Wilck
2024-11-20 21:59 ` Benjamin Marzinski
2024-11-21 8:57 ` Martin Wilck
2024-11-21 18:00 ` Benjamin Marzinski [this message]
2024-11-15 23:22 ` [PATCH 2/6] multipath-tools tests: fix mapinfo tests Benjamin Marzinski
2024-11-15 23:22 ` [PATCH 3/6] libmultipath: fix removing device after failed creation Benjamin Marzinski
2024-11-18 11:21 ` Martin Wilck
2024-11-18 21:23 ` Benjamin Marzinski
2024-11-15 23:22 ` [PATCH 4/6] libmultipath: Add flag to always return device ID when found Benjamin Marzinski
2024-11-15 23:22 ` [PATCH 5/6] libmultipath: check table type in dm_find_map_by_wwid Benjamin Marzinski
2024-11-15 23:22 ` [PATCH 6/6] libmultipath: handle a create corner case for empty devices Benjamin Marzinski
2024-11-18 11:18 ` [PATCH 0/6] multipath-tools: Handle tableless DM devices Martin Wilck
2024-11-18 21:14 ` Benjamin Marzinski
2024-11-19 12:20 ` Martin Wilck
2024-11-19 16:40 ` Martin Wilck
2024-11-19 19:13 ` Benjamin Marzinski
2024-11-20 8:51 ` Martin Wilck
2024-11-20 19:50 ` 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=Zz91VZ3r2GUZinVj@redhat.com \
--to=bmarzins@redhat.com \
--cc=christophe.varoqui@opensvc.com \
--cc=dm-devel@lists.linux.dev \
--cc=martin.wilck@suse.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.