From: Aaron Lauterer <a.lauterer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs v2] system-requirements: mention that SSDs with PLP should be used
Date: Wed, 20 Mar 2024 14:14:19 +0100 [thread overview]
Message-ID: <20240320131419.180987-1-a.lauterer@proxmox.com> (raw)
Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
---
Thanks for the feedback. I think this variant transports the important
infomation in simple english.
pve-system-requirements.adoc | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/pve-system-requirements.adoc b/pve-system-requirements.adoc
index bc3689d..98279bb 100644
--- a/pve-system-requirements.adoc
+++ b/pve-system-requirements.adoc
@@ -49,7 +49,9 @@ Recommended System Requirements
(BBU) or non-RAID for ZFS and Ceph. Neither ZFS nor Ceph are compatible with a
hardware RAID controller.
** Shared and distributed storage is possible.
-
+** Enterprise grade SSDs are recommended for good performance. Check for power
+ loss protection (PLP) to avoid using consumer-grade SSDs, which are not
+ recommended.
* Redundant (Multi-)Gbit NICs, with additional NICs depending on the preferred
storage technology and cluster setup.
--
2.39.2
reply other threads:[~2024-03-20 13:14 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=20240320131419.180987-1-a.lauterer@proxmox.com \
--to=a.lauterer@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