From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs] fix #6388: disk health: sync list of scanned devices
Date: Mon, 12 May 2025 10:23:47 +0200 [thread overview]
Message-ID: <20250512082347.444284-1-f.gruenbichler@proxmox.com> (raw)
taken straight from the man page.
Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
---
Notes:
switched to a list to avoid weird reflows in the middle of device paths, but
not too happy about that either..
pve-disk-health-monitoring.adoc | 13 ++++++++++---
1 file changed, 10 insertions(+), 3 deletions(-)
diff --git a/pve-disk-health-monitoring.adoc b/pve-disk-health-monitoring.adoc
index 0109860..64218cf 100644
--- a/pve-disk-health-monitoring.adoc
+++ b/pve-disk-health-monitoring.adoc
@@ -33,9 +33,16 @@ you can enable it with the command:
For more information on how to use smartctl, please see `man smartctl`.
-By default, smartmontools daemon smartd is active and enabled, and scans
-the disks under /dev/sdX and /dev/hdX every 30 minutes for errors and warnings, and sends an
-e-mail to root if it detects a problem.
+By default, the smartmontools daemon smartd is active and enabled, and scans
+any devices matching
+
+- `/dev/sd[a-z]`
+- `/dev/sd[a-z][a-z]`
+- `/dev/hd[a-t]`
+- or `/dev/nvme[0-99]`
+
+every 30 minutes for errors and warnings, and sends an e-mail to root if it
+detects a problem.
For more information about how to configure smartd, please see `man smartd` and
`man smartd.conf`.
--
2.39.5
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2025-05-12 8:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-12 8:23 Fabian Grünbichler [this message]
2025-07-16 14:48 ` [pve-devel] applied: " Thomas Lamprecht
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=20250512082347.444284-1-f.gruenbichler@proxmox.com \
--to=f.gruenbichler@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 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.