Hi Sanjeev and Milek, thanks for your replies but I'm afraid they are somewhat 
missing the point.
I have a situation (and I believe it would be fairly common) where early 
snapshots would be sharing most data with the current filesystem and more 
recent snapshots are holding onto data that has been deleted from the current 
filesystem (after a recent big deletion of unused data).

It is impossible to see what snapshots would need to be deleted to free up the 
space that was deleted from the current fs, without deleting the snapshots one 
by one. I think in any filesystem it is reasonable to expect to be able to 
determine what entities use up disk space. But ZFS is currently lacking this 
for snapshots.

See the below "USED" column. The total "USED" adds up to about 11G. However the 
total data consumed by the snapshots is more in the range of 100G. But from the 
listing below it is simply impossible to see which snapshots are using it.

NAME                           USED  AVAIL  REFER  MOUNTPOINT
storage                        457G   127G  28.4K  /storage
storage/myfilesystem                 457G   127G   251G  /storage/myfilesystem

NAME                                                        USED  AVAIL  REFER  
MOUNTPOINT
[EMAIL PROTECTED]                                            0      -  28.4K  -
[EMAIL PROTECTED]                                    0      -  28.4K  -
storage/[EMAIL PROTECTED]                    4.26G      -   187G  -
storage/[EMAIL PROTECTED]                              61.1M      -   206G  -
storage/[EMAIL PROTECTED]                               773M      -   201G  -
storage/[EMAIL PROTECTED]                              33.2M      -   192G  -
storage/[EMAIL PROTECTED]                            62.6M      -   212G  -
storage/[EMAIL PROTECTED]                              5.29G      -   217G  -
-- 
This message posted from opensolaris.org
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

Reply via email to