Date: Tue, 20 Oct 2020 14:10:40 -0400 From: Paul Procacci <pprocacci@gmail.com> To: Jon Schneider <freebsd@jschneider.net> Cc: freebsd-questions@freebsd.org Subject: Re: Pool space inconsistency Message-ID: <CAFbbPug%2BoeQYp-f-MVsC=UcjJ5h4uRwWSnrw8NuSWgiNvs%2B9UA@mail.gmail.com> In-Reply-To: <76ce98a6-f561-a997-7512-d2ce96f250bb@jschneider.net> References: <76ce98a6-f561-a997-7512-d2ce96f250bb@jschneider.net>
next in thread | previous in thread | raw e-mail | index | archive | help
This disparity is describe in the zpool man page.
" The space usage properties report actual physical space available to
the
storage pool. The physical space can be different from the total amount
of space that any contained datasets can actually use. The amount of
space used in a raidz configuration depends on the characteristics of
the
data being written. In addition, ZFS reserves some space for internal
accounting that the zfs(8) command takes into account, but the zpool(8)
command does not. For non-full pools of a reasonable size, these
effects
should be invisible. For small pools, or pools that are close to being
completely full, these discrepancies may become more noticeable."
~Paul
On Tue, Oct 20, 2020 at 8:09 AM Jon Schneider <freebsd@jschneider.net>
wrote:
> zpool list says
>
> NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAG CAP DEDUP
> HEALTH ALTROOT
> zroot 1.81T 1.68T 137G - - 45% 92% 1.00x
> ONLINE -
>
> whereas zfs list (and df -h) claim 79GB available.
>
> NAME USED AVAIL REFER MOUNTPOINT
> zroot 1.68T 78.9G 88K /zroot
>
> How does the discrepancy between 137GB and 79GB come about ?
>
> Perfectly default dataset arrangements with no reservations on 11.2 .
>
> Jon
> _______________________________________________
> freebsd-questions@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "
> freebsd-questions-unsubscribe@freebsd.org"
>
--
__________________
:(){ :|:& };:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFbbPug%2BoeQYp-f-MVsC=UcjJ5h4uRwWSnrw8NuSWgiNvs%2B9UA>