Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 27 Mar 2012 17:55:28 -0700
From:      Freddie Cash <fjwcash@gmail.com>
To:        Daniel Mayfield <dan@3geeks.org>
Cc:        freebsd-fs@freebsd.org
Subject:   Re: mismatch between zfs and zpool
Message-ID:  <CAOjFWZ4hBeBq36XppNrZrnkSC4XCB-2FaDNTGE66Q8NKvUw6Mg@mail.gmail.com>
In-Reply-To: <6275E6A5-E7A5-49A2-B15F-1BE2EF131A34@3geeks.org>
References:  <6275E6A5-E7A5-49A2-B15F-1BE2EF131A34@3geeks.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mar 27, 2012 5:00 PM, "Daniel Mayfield" <dan@3geeks.org> wrote:
>
> Any idea why these mismatch?  These are WD20EARS disks in a USB JBOD
enclosure.
>
> [dan@rooter ~] $ zfs list
> NAME                           USED  AVAIL  REFER  MOUNTPOINT
> mediavg                       1.86T  3.33T   314K  /media
> [dan@rooter ~] $ zpool list
> NAME            SIZE  ALLOC   FREE    CAP  DEDUP  HEALTH  ALTROOT
> mediavg        7.25T  2.56T  4.69T    35%  1.00x  ONLINE  -

If you the differences in used/alloc and avail/free between zfs and zpool,
it's because they show different things.

Search the archives and the zfs-discuss archives for all the gory details.

The cliff's notes version is that zpool shows raw storage available in the
pool, and zfs shows usable storage space after redundancy is taken into
account.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOjFWZ4hBeBq36XppNrZrnkSC4XCB-2FaDNTGE66Q8NKvUw6Mg>