From: Aaron Lauterer <a.lauterer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs] local-zfs: use correct man page for vdev infos
Date: Fri, 5 Jan 2024 10:16:46 +0100 [thread overview]
Message-ID: <20240105091646.14903-1-a.lauterer@proxmox.com> (raw)
ZFS did split up their man pages a while ago
Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
---
local-zfs.adoc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/local-zfs.adoc b/local-zfs.adoc
index 63de884..58726a7 100644
--- a/local-zfs.adoc
+++ b/local-zfs.adoc
@@ -157,7 +157,7 @@ ZFS RAID Level Considerations
There are a few factors to take into consideration when choosing the layout of
a ZFS pool. The basic building block of a ZFS pool is the virtual device, or
`vdev`. All vdevs in a pool are used equally and the data is striped among them
-(RAID0). Check the `zpool(8)` manpage for more details on vdevs.
+(RAID0). Check the `zpoolconcepts(7)` manpage for more details on vdevs.
[[sysadmin_zfs_raid_performance]]
Performance
--
2.39.2
next reply other threads:[~2024-01-05 9:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-05 9:16 Aaron Lauterer [this message]
2024-01-05 9:32 ` [pve-devel] applied: " Fiona Ebner
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=20240105091646.14903-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