Date: Thu, 10 Mar 2016 20:28:21 -0500 From: Ultima <ultima1252@gmail.com> To: marquis@roble.com Cc: freebsd-current@freebsd.org Subject: Re: zfsboot patch for /usr Message-ID: <CANJ8om6zhX8M3LO3qr4gmo3gWHt-YJ%2BRc7DEgJ2hWOQM7wuSTw@mail.gmail.com> In-Reply-To: <56e20c0b.9021620a.6a3f7.ffff9443SMTPIN_ADDED_MISSING@mx.google.com> References: <mailman.41.1457611201.12891.freebsd-current@freebsd.org> <56e20c0b.9021620a.6a3f7.ffff9443SMTPIN_ADDED_MISSING@mx.google.com>
next in thread | previous in thread | raw e-mail | index | archive | help
No need to ignore the output of zfs list, here is an explanation of zfs
list's output, this is in the zfs man page. I think you're confusing used
with refer.
used
The amount of space consumed by this dataset and all its
descendents.
This is the value that is checked against this dataset's quota and
reservation. The space used does not include this dataset's
reserva=E2=80=90
tion, but does take into account the reservations of any descenden=
t
datasets. The amount of space that a dataset consumes from its par=
=E2=80=90
ent, as well as the amount of space that are freed if this dataset
is
recursively destroyed, is the greater of its space used and its
reservation.
When snapshots (see the "Snapshots" section) are created, their
space
is initially shared between the snapshot and the file system, and
possibly with previous snapshots. As the file system changes, spac=
e
that was previously shared becomes unique to the snapshot, and
counted in the snapshot's space used. Additionally, deleting snap=
=E2=80=90
shots can increase the amount of space unique to (and used by)
other
snapshots.
The amount of space used, available, or referenced does not take
into
account pending changes. Pending changes are generally accounted
for
within a few seconds. Committing a change to a disk using fsync(2)
or
O_SYNC does not necessarily guarantee that the space usage informa=
=E2=80=90
tion is updated immediately.
available
The amount of space available to the dataset and all its children,
assuming that there is no other activity in the pool. Because spac=
e
is shared within a pool, availability can be limited by any number
of
factors, including physical pool size, quotas, reservations, or
other
datasets within the pool.
This property can also be referred to by its shortened column name=
,
avail.
referenced
The amount of data that is accessible by this dataset, which may o=
r
may not be shared with other datasets in the pool. When a snapshot
or
clone is created, it initially references the same amount of space
as
the file system or snapshot it was created from, since its content=
s
are identical.
This property can also be referred to by its shortened column name=
,
refer.
On Thu, Mar 10, 2016 at 7:06 PM, Roger Marquis <marquis@roble.com> wrote:
> > You don't mkdir it, you create it as a ZFS dataset, and mark it with th=
e
> > 'canmount=3Dno' property, so it only exists to be a parent, not as an
> > actual dataset. This is the default in zfboot currently.
>
> Thanks to everyone for pointing this out. I'll forget about mkdir then,
> ignore the output of 'zfs list' and get comfortable doing things the zfs
> way.
>
> Still have to tweak scripts/zfsboot to create a /var/spool subvol, a /hom=
e
> subvol in place of /usr/home and specify atime=3Dnone in the default data=
set.
> At least the latter works as expected.
>
> Roger
>
>
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org=
"
>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANJ8om6zhX8M3LO3qr4gmo3gWHt-YJ%2BRc7DEgJ2hWOQM7wuSTw>