Thank you very much, this explains it perfectly.
I had been coming to the conclusion that the shared data must be what accounts
for the "missing" space, but previously my thinking/expectation was that it
would be "charged" against the snapshot in which the shared data first
appeared. Doing that
Ha ha, I know! Like I say, I do get COW principles!
I guess what I'm after is for someone to look at my specific example (in txt
file attached to first post) and tell me specifically how to find out where the
13.8GB number is coming from.
I feel like a total numpty for going on about this, I re
I do understand these concepts, but to me that still doesn't explain why adding
the size of each snapshot together doesn't equal the size reported by zfs list
in USEDSNAP.
I'm clearly missing something. Hmmm...
--
This message posted from opensolaris.org
> Well, I see USEDSNAP 13.8 GB for the dataset, so if you delete ALL
> snapshots you'd probably be able to get that much.
I agree, it's just hard to see how...
> As for "which snapshot to delete to get most space",
> that's a liitle
> bit tricky. See
> rpool/export/home/m...@zfs-auto-snap:monthly
Hi, thanks for the info.
Can you have a look at the attachment on the original post for me?
Everything you said is what I expected to see in the output there, but a lot of
the values are blank where I hoped they would at least be able to tell me a
breakdown of the USEDSNAP figure
As far as I k
The guide is good, but didn't tell me anything I didn't already know about this
area unfortunately.
Anyway, I freed up a big chunk of space by first deleting the snapshot which
was reported by zfs list as being the largest (2GB). Doing zfs list after this
deletion revealed that several of the n
Please can someone take a look at the attached file which shows the output on
my machine of
zfs list -r -t filesystem,snapshot -o space rpool/export/home/matt
The USEDDS figure of ~2GB is what I would expect, and is the same figure
reported by the Disk Usage Analyzer. Where is the remaining 13.8
