From: Keith Busch <kbusch@kernel.org>
To: Matthieu Rolla <matthieu@minio.io>
Cc: Stefan Hajnoczi <stefanha@redhat.com>,
Klaus Jensen <its@irrelevant.dk>,
qemu-devel@nongnu.org, qemu-block@nongnu.org,
mr-083 <matthieu@min.io>, John Meneghini <jmeneghi@redhat.com>
Subject: Re: [PATCH 0/2] NVMe namespace hotplug and drive reconnection support
Date: Tue, 14 Apr 2026 12:09:19 -0600 [thread overview]
Message-ID: <ad6Cz4XmrrDc2yRH@kbusch-mbp> (raw)
In-Reply-To: <A0EE1F55-E562-4315-BE08-1D3CF70706AD@minio.io>
On Tue, Apr 14, 2026 at 03:36:19PM +0200, Matthieu Rolla wrote:
> Regarding `drive_insert`, I found that `device_del` + `device_add` works well when no filesystem is mounted on the namespace.
>
> However, when XFS is mounted (e.g. via DirectPV/CSI), the Linux kernel doesn't reuse the block device number (nvme0n1 becomes nvme0n2) because the stale mount holds a reference to the old `nvme_ns_head`, preventing `ida_free()`.
>
> This causes XFS "duplicate UUID" errors on remount.
>
> `drive_insert` avoids this by keeping the namespace device alive which means no ida cycle, same block device name.
Are you attempting some kind of covert way to swap out the backend
without the host knowing you did that? Isn't that just going to confuse
the filesystem that's actively using the previous backend when it's
in-memory context no longer aligns with the on-disk format?
next prev parent reply other threads:[~2026-04-14 18:10 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 6:01 [PATCH 0/2] NVMe namespace hotplug and drive reconnection support mr-083
2026-04-09 6:01 ` [PATCH 1/2] hw/nvme: add namespace hotplug support mr-083
2026-04-09 6:01 ` [PATCH 2/2] block/monitor: add drive_insert HMP command mr-083
2026-04-14 17:57 ` Stefan Hajnoczi
2026-04-14 18:02 ` Matthieu Rolla
2026-04-14 19:05 ` Warner Losh
2026-04-14 21:01 ` Matthieu Rolla
2026-04-15 10:48 ` Daniel P. Berrangé
2026-04-15 12:32 ` Matthieu Rolla
2026-04-16 19:52 ` Stefan Hajnoczi
2026-04-16 22:00 ` Matthieu Rolla
2026-04-15 12:33 ` Stefan Hajnoczi
2026-04-09 21:34 ` [PATCH v2] hw/nvme: add namespace hotplug support mr-083
2026-04-10 12:41 ` Stefan Hajnoczi
2026-04-10 14:30 ` [PATCH v3] " mr-083
2026-04-10 14:33 ` Matthieu Rolla
2026-04-10 20:14 ` Stefan Hajnoczi
2026-04-13 15:24 ` Matthieu Rolla
2026-04-13 17:17 ` [PATCH 0/2] NVMe namespace hotplug and drive reconnection support Klaus Jensen
2026-04-14 12:42 ` Stefan Hajnoczi
2026-04-14 13:36 ` Matthieu Rolla
2026-04-14 18:09 ` Keith Busch [this message]
2026-04-14 18:10 ` Stefan Hajnoczi
2026-04-14 18:14 ` Matthieu Rolla
2026-04-15 12:45 ` Stefan Hajnoczi
2026-04-15 17:39 ` Matthieu Rolla
2026-04-14 14:04 ` John Meneghini
2026-04-16 10:11 ` Nilay Shroff
2026-04-16 12:33 ` Matthieu Rolla
2026-04-14 14:42 ` Keith Busch
2026-04-15 17:38 ` [PATCH v4] hw/nvme: add namespace hotplug support mr-083
2026-04-16 19:42 ` Stefan Hajnoczi
2026-04-17 9:29 ` Klaus Jensen
2026-04-17 9:45 ` Matthieu Rolla
-- strict thread matches above, loose matches on Subject: below --
2026-04-09 7:01 [PATCH 0/2] NVMe namespace hotplug and drive reconnection support mr-083
2026-04-09 21:00 ` Stefan Hajnoczi
2026-04-10 0:49 ` Matthieu Rolla
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=ad6Cz4XmrrDc2yRH@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=its@irrelevant.dk \
--cc=jmeneghi@redhat.com \
--cc=matthieu@min.io \
--cc=matthieu@minio.io \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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.