Hello,
Well it looks as though some brilliant folks have indeed solved the
installer thirst for numerous distros, by creating a generic framework that
works with many linux distros.:: [1] A '' version is in portage
(thanks!) But other versions are found in the overlays "eix -R calamares"
Ca
Remy Blank wrote on 2015-10-31 16:35:
> I guess I was looking for something like "how much data is shared
> between this snapshot and the next one", but since there's no link
> between snapshots (only between the dataset and the snapshots), ZFS
> can't provide it in "zfs list".
>
> But maybe there
Jeremi Piotrowski wrote on 2015-10-31 15:25:
> USEDSNAP refers to _data_ that is not in pool/data but in the snapshots.
> The value for USED is _data_ that is only present in *this one* snapshot,
> and not in any other snapshots or in pool/data. _data_ that is shared
> between atleast two snapshots
On Sat, Oct 31, 2015 at 10:25 AM, Jeremi Piotrowski
wrote:
>
> This is one of the problems with copy-on-write filesystems - they make
> disk space accounting more complicated especially with snapshots.
Indeed, it is one of the problems with copy-on-write anything. Shared
memory is a similar situ
On Sat, Oct 31, 2015 at 10:37:55AM +0100, Remy Blank wrote:
> I'm trying to make sense of the disk usage reported by "zfs list".
> Here's what I get:
>
> $ zfs list \
> -o name,used,avail,refer,usedbydataset,usedbychildren,usedbysnapshots \
> -t all
>
> NAME USED AVAIL REFER U
I'm trying to make sense of the disk usage reported by "zfs list".
Here's what I get:
$ zfs list \
-o name,used,avail,refer,usedbydataset,usedbychildren,usedbysnapshots \
-t all
NAME USED AVAIL REFER USEDDS USEDCHILD USEDSNAP
pool/data58.0G 718G 46.7G 46.7G
6 matches
Mail list logo
