* [pve-devel] [PATCH docs] local-zfs: use correct man page for vdev infos
@ 2024-01-05 9:16 Aaron Lauterer
2024-01-05 9:32 ` [pve-devel] applied: " Fiona Ebner
0 siblings, 1 reply; 2+ messages in thread
From: Aaron Lauterer @ 2024-01-05 9:16 UTC (permalink / raw)
To: pve-devel
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* [pve-devel] applied: [PATCH docs] local-zfs: use correct man page for vdev infos
2024-01-05 9:16 [pve-devel] [PATCH docs] local-zfs: use correct man page for vdev infos Aaron Lauterer
@ 2024-01-05 9:32 ` Fiona Ebner
0 siblings, 0 replies; 2+ messages in thread
From: Fiona Ebner @ 2024-01-05 9:32 UTC (permalink / raw)
To: Proxmox VE development discussion, Aaron Lauterer
Am 05.01.24 um 10:16 schrieb Aaron Lauterer:
> ZFS did split up their man pages a while ago
>
> Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
applied, thanks!
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2024-01-05 9:32 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-01-05 9:16 [pve-devel] [PATCH docs] local-zfs: use correct man page for vdev infos Aaron Lauterer
2024-01-05 9:32 ` [pve-devel] applied: " Fiona Ebner
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox