solarg writes:
> >> # zfs list
> >> NAME USED AVAIL REFER
> >> MOUNTPOINT
> >> rpool/zones/catalogue2/ROOT/zbe 4.49G 17.9G 7.47G legacy
> >> rpool/zones/catalogue3/ROOT/zbe 149M 17.9G 6.80G legacy
> >> rpool/zones/test-drupal/ROOT/zbe 511M 17.9G 5.21G legacy
> >>
> >> on another os2008.11 machine, i created a new zone, and don't notice
> >> these high values:
> >> # zfs list
> >> NAME USED AVAIL REFER MOUNTPOINT
> >> rpool/export/catalogue4 4.07M 16.1G 21K /export/catalogue4
> >> rpool/export/catalogue4/ROOT 4.05M 16.1G 18K legacy
> >> rpool/export/catalogue4/ROOT/zbe 4.03M 16.1G 235M legacy
> >>
> >> what is the meaning of REFER? can i gain more space?
"REFER" is documented on the zfs(1M) man page. It's the amount of
space accessible by the dataset and some or all of it may be shared
with another dataset. If you're interested in the amount of disk
space used, then the "USED" column is what you want.
At a guess, the difference between these two machines is that
'catalogue4' was likely created as a sparse-root zone, while
'catalogue2' was created as a whole-root zone. The clones of that
whole-root zone ('catalogue3' and 'test-drupal') use little disk
space, as most of it is 'referred' from 'catalogue2'.
This part of the output shows the relationships:
> rpool/zones/catalogue2/ROOT/zbe 4.52G 7.47G
> rpool/zones/catalogue/ROOT/z...@catalogue2_snap
> rpool/zones/catalogue2/ROOT/z...@test_drupal_snap 358M 4.75G -
> rpool/zones/catalogue2/ROOT/z...@catalogue3_snap 85.2M 7.47G -
[...]
> rpool/zones/catalogue3/ROOT/zbe 149M 6.66G
> rpool/zones/catalogue2/ROOT/z...@catalogue3_snap
[...]
> rpool/zones/test-drupal/ROOT/zbe 511M 5.21G
> rpool/zones/catalogue2/ROOT/z...@test_drupal_snap
--
James Carlson, Solaris Networking <[email protected]>
Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
_______________________________________________
zones-discuss mailing list
[email protected]
