* [pve-devel] [PATCH docs] pmxcfs: update size limit to 128 MiB
@ 2023-04-11 8:16 Aaron Lauterer
2023-05-18 11:12 ` [pve-devel] applied: " Thomas Lamprecht
0 siblings, 1 reply; 2+ messages in thread
From: Aaron Lauterer @ 2023-04-11 8:16 UTC (permalink / raw)
To: pve-devel
Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
---
I also did a reformat of that paragraph.
pmxcfs.adoc | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/pmxcfs.adoc b/pmxcfs.adoc
index ea15559..85e61d8 100644
--- a/pmxcfs.adoc
+++ b/pmxcfs.adoc
@@ -29,10 +29,10 @@ system for storing configuration files, replicated in real time to all
cluster nodes using `corosync`. We use this to store all PVE related
configuration files.
-Although the file system stores all data inside a persistent database
-on disk, a copy of the data resides in RAM. This imposes restrictions
-on the maximum size, which is currently 30MB. This is still enough to
-store the configuration of several thousand virtual machines.
+Although the file system stores all data inside a persistent database on disk,
+a copy of the data resides in RAM. This imposes restrictions on the maximum
+size, which is currently 128 MiB. This is still enough to store the
+configuration of several thousand virtual machines.
This system provides the following advantages:
--
2.30.2
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2023-05-18 11:13 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-04-11 8:16 [pve-devel] [PATCH docs] pmxcfs: update size limit to 128 MiB Aaron Lauterer
2023-05-18 11:12 ` [pve-devel] applied: " Thomas Lamprecht
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox