Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 5 Jul 2009 02:30:59 +0300
From:      Dan Naumov <dan.naumov@gmail.com>
To:        Freddie Cash <fjwcash@gmail.com>
Cc:        FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org>
Subject:   Re: ZFS and df weirdness
Message-ID:  <cf9b1ee00907041630u12e68e58l1bb317b42a6ea5fc@mail.gmail.com>
In-Reply-To: <b269bc570907041626j53d4b3f6y5f710d2f55631ef4@mail.gmail.com>
References:  <cf9b1ee00907041455v57b1e1eatf7b4cf0a060b938c@mail.gmail.com> <b269bc570907041626j53d4b3f6y5f710d2f55631ef4@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Jul 5, 2009 at 2:26 AM, Freddie Cash<fjwcash@gmail.com> wrote:
>
>
> On Sat, Jul 4, 2009 at 2:55 PM, Dan Naumov <dan.naumov@gmail.com> wrote:
>>
>> Hello list.
>>
>> I have a single 2tb disk used on a 7.2-release/amd64 system with a
>> small part of it given to UFS and most of the disk given to a single
>> "simple" zfs pool with several filesystems without redundancy. I've
>> noticed a really weird thing regarding what "df" reports regarding the
>> "total space" of one of my filesystems:
>>
>> atom# df -h
>> Filesystem =A0 =A0 =A0 =A0 Size =A0 =A0Used =A0 Avail Capacity =A0Mounte=
d on
>> /dev/ad12s1a =A0 =A0 =A0 =A015G =A0 =A01.0G =A0 =A0 13G =A0 =A0 7% =A0 =
=A0/
>> devfs =A0 =A0 =A0 =A0 =A0 =A0 =A01.0K =A0 =A01.0K =A0 =A0 =A00B =A0 100%=
 =A0 =A0/dev
>> linprocfs =A0 =A0 =A0 =A0 =A04.0K =A0 =A04.0K =A0 =A0 =A00B =A0 100% =A0=
 =A0/usr/compat/linux/proc
>> tank/DATA =A0 =A0 =A0 =A0 =A01.8T =A0 =A0292G =A0 =A01.5T =A0 =A016% =A0=
 =A0/DATA
>> tank/home =A0 =A0 =A0 =A0 =A01.5T =A0 =A0 =A00B =A0 =A01.5T =A0 =A0 0% =
=A0 =A0/home
>> tank/home/jago =A0 =A0 1.5T =A0 =A0128K =A0 =A01.5T =A0 =A0 0% =A0 =A0/h=
ome/jago
>> tank/home/karni =A0 =A01.5T =A0 =A0 =A00B =A0 =A01.5T =A0 =A0 0% =A0 =A0=
/home/karni
>> tank/usr/local =A0 =A0 1.5T =A0 =A0455M =A0 =A01.5T =A0 =A0 0% =A0 =A0/u=
sr/local
>> tank/usr/obj =A0 =A0 =A0 1.5T =A0 =A0 =A00B =A0 =A01.5T =A0 =A0 0% =A0 =
=A0/usr/obj
>> tank/usr/ports =A0 =A0 1.5T =A0 =A0412M =A0 =A01.5T =A0 =A0 0% =A0 =A0/u=
sr/ports
>> tank/usr/src =A0 =A0 =A0 1.5T =A0 =A0495M =A0 =A01.5T =A0 =A0 0% =A0 =A0=
/usr/src
>> tank/var/log =A0 =A0 =A0 1.5T =A0 =A0256K =A0 =A01.5T =A0 =A0 0% =A0 =A0=
/var/log
>>
>> Considering that every single filesystem is part of the exact same
>> pool, with no custom options whatsoever used during filesystem
>> creation (except for mountpoints), why is the size of tank/DATA 1.8T
>> while the others are 1.5T?
>
> Did you set a reservation for any of the other filesystems?=A0 Reserved s=
pace
> is not listed in the "general" pool.

no custom options whatsoever were used during filesystem creation
(except for mountpoints).

- Dan



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