From: Fiona Ebner <f.ebner@proxmox.com>
To: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>,
"Christian Ebner" <c.ebner@proxmox.com>,
"Proxmox VE development discussion" <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH v2 storage] api: fix get content call for volumes
Date: Tue, 7 Mar 2023 10:15:52 +0100 [thread overview]
Message-ID: <a73703b3-6caf-9ce0-1158-066ab7f24280@proxmox.com> (raw)
In-Reply-To: <1678178711.44w60pfavx.astroid@yuna.none>
Am 07.03.23 um 09:51 schrieb Fabian Grünbichler:
> On March 7, 2023 9:31 am, Fiona Ebner wrote:
>
> unfortunately not the case - a zvol can take up (significantly) more space than
> volsize:
>
> $ zpool get ashift testpool
> NAME PROPERTY VALUE SOURCE
> testpool ashift 12 local
> $ zfs get volsize,volblocksize,space testpool/test
> NAME PROPERTY VALUE SOURCE
> testpool/test volsize 5G local
> testpool/test volblocksize 8K default
> testpool/test name testpool/test -
> testpool/test available 11.2G -
> testpool/test used 7.43G -
> testpool/test usedbysnapshots 0B -
> testpool/test usedbydataset 7.32G -
> testpool/test usedbyrefreservation 111M -
> testpool/test usedbychildren 0B -
>
> this is the common "ashift=12 / volblocksize=8 / raidz2" pitfall..
Oh, right. Well, I'd say usedbydataset is still more consistent with the
current values for $used and I guess it's technically true even if $used
> $size.
next prev parent reply other threads:[~2023-03-07 9:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-06 13:07 Christian Ebner
2023-03-07 8:31 ` Fiona Ebner
2023-03-07 8:51 ` Fabian Grünbichler
2023-03-07 9:15 ` Fiona Ebner [this message]
2023-03-07 9:17 ` Christian 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=a73703b3-6caf-9ce0-1158-066ab7f24280@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=c.ebner@proxmox.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox