0% CAP Reported with data present

meentsbk meentsbk at gmail.com
Fri May 20 13:09:53 EDT 2011


Ah, you are right - it might absolutely be a rounding thing.  Should
have thought about the basics before questioning it :/

I'll give that a shot with something larger and verify everything
shows appropriately, then post back to the group.

Thanks for pointing out the (hopefully) very obvious!

Brian

On May 20, 12:02 pm, "Fajar A. Nugraha" <l... at fajar.net> wrote:
> On Fri, May 20, 2011 at 8:45 PM, meentsbk <meent... at gmail.com> wrote:
> > Through nautilus, I then created a folder in tank/data/media called
> > music and copied in 3GB as a test run.  When looking at both zpool
> > status and zfs status, however, the ALLOC is showing the proper size,
> > but the CAP and  AVAIL are not changing:
>
> > zpool status
> > NAME   SIZE  ALLOC   FREE    CAP  DEDUP  HEALTH  ALTROOT
> > tank      1.81T  3.18G     1.81T     0%    1.00x      ONLINE    -
>
> > zfs status
> > NAME         USED  AVAIL  REFER  MOUNTPOINT
> > tank            3.18G   1.78T    32K      /tank
> > tank/data     58.1M  1.78T    58.1M   /tank/data
> > tank/media  3.12G   1.78T    3.12G   /tank/media
>
> > Am I just missing something extremely obvious, or do I have something
> > setup incorrectly (and thus putting my data at risk?)
>
> 3 GB is very small when compared to 1.8T (less than 1%). It's just
> rounding problem. What happens when you add more data (let's say at
> least 100GB, with dd or something similar)?
>
> --
> Fajar



More information about the zfs-discuss mailing list