From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <pve-devel-bounces@lists.proxmox.com>
Received: from gate001.proxmox.com (gate001.proxmox.com [IPv6:2a0f:8001:1:32::40])
	by lore.proxmox.com (Postfix) with ESMTPS id 15D021FF0EC
	for <inbox@lore.proxmox.com>; Sat, 07 Nov 2026 19:05:27 +0100 (CET)
Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1])
	by gate001.proxmox.com (Proxmox) with ESMTP id 5E7AB2165A;
	Sat, 07 Nov 2026 19:05:11 +0100 (CET)
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
Message-ID: <179407275570.1575726.9550300898759404777.b4-ty@b4>
X-Mailer: git-send-email 2.47.3
In-Reply-To: <20261104092939.123574-1-t.ellmenreich@proxmox.com>
References: <20261104092939.123574-1-t.ellmenreich@proxmox.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2
X-Bm-Transport-Timestamp: 1794074700764
X-SPAM-LEVEL: Spam detection results:  0
	AWL                     0.280 Adjusted score from AWL reputation of From:
 address
	DMARC_MISSING             0.1 Missing DMARC policy
	KAM_DMARC_STATUS         0.01 Test Rule for DKIM or SPF Failure with Strict
 Alignment (newer systems)
	RCVD_IN_DNSWL_MED        -2.3 Sender listed at https://www.dnswl.org/,
 medium trust
	SPF_HELO_NONE           0.001 SPF: HELO does not publish an SPF Record
	SPF_PASS               -0.001 SPF: sender matches SPF record
Message-ID-Hash: IQBFOLUZ2QBOLHF4ROKEG43ZT2KH7Y5L
X-Message-ID-Hash: IQBFOLUZ2QBOLHF4ROKEG43ZT2KH7Y5L
X-MailFrom: t.lamprecht@proxmox.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop;
 banned-address; emergency; member-moderation; nonmember-moderation;
 administrivia; implicit-dest; max-recipients; max-size; news-moderation;
 no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.10
Precedence: list
List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com>
List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help>
List-Owner: <mailto:pve-devel-owner@lists.proxmox.com>
List-Post: <mailto:pve-devel@lists.proxmox.com>
List-Subscribe: <mailto:pve-devel-join@lists.proxmox.com>
List-Unsubscribe: <mailto:pve-devel-leave@lists.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).