From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Aaron Lauterer <a.lauterer@proxmox.com>
Subject: [pve-devel] applied: [PATCH docs v1] Add section with more infos about ZFS RAID levels
Date: Wed, 22 Jul 2020 12:45:28 +0200 [thread overview]
Message-ID: <2c87bf19-afe1-f857-c296-7dce2d16ed6e@proxmox.com> (raw)
In-Reply-To: <20200721125829.23083-1-a.lauterer@proxmox.com>
On 21.07.20 14:58, Aaron Lauterer wrote:
> This new section explains the performance and failure properties of
> mirror and RAIDZ VDEVs as well as the "unexpected" higher space usage by
> ZVOLs on a RAIDZ.
>
> Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
> ---
>
> draft->v1:
> * incorporate Stoikos suggestions [0]
> * went with lower case vdev as this is the way it is used in the zpool
> manpage
> * used N-P(arity) in the RAIDZ sizing part
> * added a short explanation of vdevs at the beginning and mention the
> zpool manpage
>
>
> This is a first version to explain the performance characteristics of the
> different RAID levels / vdev types, as well as their failure behavior.
>
> Additionally it explains the situation why a VM disk (ZVOL) can end up
> using quite a bit more space than expected when placed on a pool made of
> RAIDZ VDEVs.
>
> The motivation behind this is, that in the recent past, these things
> came up quite a bit. Thus it would be nice to have some documentation
> that we can link to and having it in the docs might help users to make
> an informed decision from the start.
>
> I hope I did not mess up any technical details and that it is
> understandable enough.
>
> [0] https://lists.proxmox.com/pipermail/pve-devel/2020-July/044453.html
>
> local-zfs.adoc | 95 ++++++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 95 insertions(+)
>
>
applied, thanks!
prev parent reply other threads:[~2020-07-22 10:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-21 12:58 [pve-devel] " Aaron Lauterer
2020-07-22 10:45 ` Thomas Lamprecht [this message]
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=2c87bf19-afe1-f857-c296-7dce2d16ed6e@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=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