From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com,
Thomas Ellmenreich <t.ellmenreich@proxmox.com>
Subject: applied: [PATCH container 0/2] mountpoint: allow certain options to be hotplugged
Date: Sat, 7 Nov 2026 19:01:17 +0100 [thread overview]
Message-ID: <179407275570.1575726.9550300898759404777.b4-ty@b4> (raw)
In-Reply-To: <20261104092939.123574-1-t.ellmenreich@proxmox.com>
On Wed, 04 Nov 2026 10:29:37 +0100, Thomas Ellmenreich wrote:
> Ticking the backup or replicate flag on a container mountpoint and the
> replicate flag on the containers rootfs can be applied directly even if
> the container is running. This should be possible because it does not
> affect the actual mountpoint/disk.
>
> This functionality is already present for VMs, but not for containers.
>
> [...]
Applied, thanks!
[1/2] mountpoint: allow changing mountpoint properties at runtime
commit: aea9ec4b5b9d4ff3bbf797af63322fc7a4971a2c
[2/2] mountpoint: allow changing rootfs properties at runtime
commit: 0646f519d6d8a9471e81d46a8962eb35d3371f63
Folded in two small fixes: dropped a stray blank line at the end of the test
Makefile in the first patch, and fixed a subtest name in the second that
mentioned a backup difference, as rootfs has no backup option (its always
backed up).
prev parent reply other threads:[~2026-11-07 18:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 9:29 [PATCH container 0/2] mountpoint: allow certain options to be hotplugged Thomas Ellmenreich
2026-11-04 9:29 ` [PATCH pve-container 1/2] mountpoint: allow changing mountpoint properties at runtime Thomas Ellmenreich
2026-11-04 9:29 ` [PATCH pve-container 2/2] mountpoint: allow changing rootfs " Thomas Ellmenreich
2026-11-07 18:01 ` Thomas Lamprecht [this message]
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=179407275570.1575726.9550300898759404777.b4-ty@b4 \
--to=t.lamprecht@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=t.ellmenreich@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 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.