From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id B50501FF136 for ; Mon, 23 Feb 2026 17:00:49 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id E86D512FB8; Mon, 23 Feb 2026 17:00:45 +0100 (CET) From: Markus Frank To: pve-devel@lists.proxmox.com Subject: [PATCH docs v2 5/11] virtiofs: add explanation for cache=metadata behavior Date: Mon, 23 Feb 2026 16:40:02 +0100 Message-ID: <20260223155951.468572-6-m.frank@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260223155951.468572-1-m.frank@proxmox.com> References: <20260223155951.468572-1-m.frank@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1771862419985 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.007 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment KAM_SHORT 0.001 Use of a URL Shortener for very short URL 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: K4MWJI67JHD42PG43KTSNI5AWEGAI23R X-Message-ID-Hash: K4MWJI67JHD42PG43KTSNI5AWEGAI23R X-MailFrom: m.frank@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 List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Adds a description of the `cache=metadata` mode and references the upstream patch that introduced it. Signed-off-by: Markus Frank --- qm.adoc | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/qm.adoc b/qm.adoc index 667fd56..4843d82 100644 --- a/qm.adoc +++ b/qm.adoc @@ -1323,7 +1323,9 @@ has been configured in the resource mapping. Additionally, you can set the `cache` option to either `always`, `never`, `metadata`, or `auto` (default: `auto`), depending on your requirements. How the different caching modes behave can be read https://lwn.net/Articles/774495/[here under the "Caching Modes" -section]. +section]. The https://gitlab.com/virtio-fs/virtiofsd/-/commit/598ca8e[`metadata`] +policy is similar to `never`, but it allows guests to cache filesystem metadata, +such as dcache and attr. The `virtiofsd` supports ACL and xattr passthrough (can be enabled with the `expose-acl` and `expose-xattr` options), allowing the guest to access ACLs and -- 2.47.3