From: Dietmar Maurer <dietmar@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH] intro: fix outdated pmxcfs maximum storage size
Date: Wed, 15 Jul 2026 10:27:45 +0200 [thread overview]
Message-ID: <20260715082747.3342001-1-dietmar@proxmox.com> (raw)
The pmxcfs RAM copy limit was raised to 128 MiB long ago and the
pmxcfs chapter documents that value, but the introduction still
carried the old 30 MB figure.
Signed-off-by: Dietmar Maurer <dietmar@proxmox.com>
---
pve-intro.adoc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/pve-intro.adoc b/pve-intro.adoc
index 30e398c..c2a0b6a 100644
--- a/pve-intro.adoc
+++ b/pve-intro.adoc
@@ -42,7 +42,7 @@ database-driven file system for storing configuration files. It can
store the configuration of thousands of virtual machines. Corosync
replicates these files in real time to all cluster nodes. The file
system stores all data inside a persistent database on disk, while a
-copy resides in RAM, providing a maximum storage size of 30 MB—more
+copy resides in RAM, providing a maximum storage size of 128 MiB—more
than enough for thousands of VMs.
+
{pve} is the only virtualization platform using this cluster file
--
2.47.3
reply other threads:[~2026-07-15 8:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260715082747.3342001-1-dietmar@proxmox.com \
--to=dietmar@proxmox.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