From: Jonas Theisen <j.theisen@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH pve-docs] zfs: Add paragraph on adding hot-spares
Date: Thu, 3 Sep 2026 10:01:00 +0200 [thread overview]
Message-ID: <20260903080120.61911-1-j.theisen@proxmox.com> (raw)
Add command to add hot spare to existing ZFS pool since it came up
in a Proxmox VE Training.
Reference https://docs.oracle.com/cd/E19253-01/819-5461/gcvcw/index.html
Signed-off-by: Jonas Theisen <j.theisen@proxmox.com>
---
local-zfs.adoc | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/local-zfs.adoc b/local-zfs.adoc
index cdc17a4..029f628 100644
--- a/local-zfs.adoc
+++ b/local-zfs.adoc
@@ -504,6 +504,17 @@ You can also add ZIL and cache separately.
# zpool add <pool> log <log-device>
----
+[[sysadmin_zfs_add_hot_spare]]
+Adding a hot spare drive to an existing pool
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+ZFS supports hot spare drives which allow the system to automatically replace
+a failed disk with the spare without manual intervention.
+
+.Add a hot spare to an existing pool
+----
+# zpool add <pool> spare <spare-device>
+----
[[sysadmin_zfs_change_failed_dev]]
Changing a failed device
--
2.47.3
reply other threads:[~2026-09-03 8:01 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=20260903080120.61911-1-j.theisen@proxmox.com \
--to=j.theisen@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