Brock Pytlik wrote:
On the other hand, it would mean that removing earlier BE's would give a user an easy way to reduce their disk consumption since deleting the old BE's would clear up space. But, at least on my system, old BE's take a minute amount of disk space compared to my currently booted one (on the order of 50M-3G compare4d to 38G for my current BE).

The way space is accounted for is misleading:

     referenced

         The amount of data that is accessible by  this  dataset,
         which  may  or  may not be shared with other datasets in
         the pool. When a snapshot or clone is created,  it  ini-
         tially  references  the same amount of space as the file
         system or snapshot it was created from, since  its  con-
         tents are identical.

         This property can also be referred to by  its  shortened
         column name, "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 reservation, but does
         take into account the  reservations  of  any  descendent
         datasets.  The  amount  of space that a dataset consumes
         from its parent, 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, space that was
         previously shared becomes unique to  the  snapshot,  and
         counted  in  the  snapshot's  space  used. Additionally,
         deleting snapshots 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.  Com-
         mitting  a  change  to  a disk using fsync(3c) or O_SYNC
         does not necessarily  guarantee  that  the  space  usage
         information is updated immediately.

- Bart


--
Bart Smaalders                  Solaris Kernel Performance
[email protected]         http://blogs.sun.com/barts
"You will contribute more with mercurial than with thunderbird."
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss

Reply via email to