But there is some good info in there.. Curious tho, how would I caculate the "real free space" in an aggr. If we have a mix of volume guarantee volume and none, with only NFS and CIFS data on an aggr, Could we not run the aggr up higher then 90% should we have a real free space in some of these volumes largely unused?
If we have 1T amount 10 vols at guarantee volume and only 10G in each, that's 100G, or 10% used. so that leaves with 900G of space "Free" right. running the aggr up to 90% means we may only really useing 80% of the aggr in this case.
I guess it depends on your definition of "real" free space.Surely a LUN with 50% free space within the OS would also constitute free space? If you thin provision all your volumes to "none" you would free up a lot more space than if you just set them at "file".
I don't think there is a simple command to show you all the info, but you could probably do something with a quick script or Excel. Chuck all the volume sizes into Excel and you could easily show the free space in volumes + aggregate.
If you set all the volumes to guarantee=file, the aggregate free space would then give you your "real" free space. If you scripted this, it wouldn't need to affect the system at all.
If you set the volumes to guarantee=none, the aggregate free space would then also show you unallocated space within your LUNs also. If you are using the SnapDrive space reclaimer, this would be more realistic than if you aren't (as deleted blocks from Windows may still be taking space on the NetApp).