From: Andrei Perepiolkin <andrei.perepiolkin@open-e.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: [pve-devel] storage plugin volume sync during live migration
Date: Tue, 17 Feb 2026 07:06:05 -0500 [thread overview]
Message-ID: <f843995b-8f7b-493c-9183-fc5497e9610a@open-e.com> (raw)
Hi,
I have a question regarding Proxmox storage plugin
activate_volume/deactivate_volume concurrency for shared volumes.
During live migration volume can be simultaneously attached to multiple
nodes at same time.
If vm migrates from node1 to node2, activate volume on node2 will
be called before deactivate is done on node1.
This raises question regarding concurrency, a specially for sync-like
operations.
Does Proxmox have any mean to guaranty that no I/O will be performed on
node2 until deactivation on node1 is completed?
Can I/O operation take place on node2 before activation on node2 is
completed?
Best regards,
Andrei Perepiolkin
next reply other threads:[~2026-02-17 12:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-17 12:06 Andrei Perepiolkin [this message]
2026-02-18 7:30 ` Fabian Grünbichler
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=f843995b-8f7b-493c-9183-fc5497e9610a@open-e.com \
--to=andrei.perepiolkin@open-e.com \
--cc=pve-devel@lists.proxmox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox