* [PATCH] intro: fix outdated pmxcfs maximum storage size
@ 2026-07-15 8:27 Dietmar Maurer
2026-07-15 15:19 ` applied: " Thomas Lamprecht
0 siblings, 1 reply; 2+ messages in thread
From: Dietmar Maurer @ 2026-07-15 8:27 UTC (permalink / raw)
To: pve-devel
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
^ permalink raw reply related [flat|nested] 2+ messages in thread
end of thread, other threads:[~2026-07-15 15:19 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-07-15 8:27 [PATCH] intro: fix outdated pmxcfs maximum storage size Dietmar Maurer
2026-07-15 15:19 ` applied: " Thomas Lamprecht
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.