Not really...aggr show_space for a volume also keeps changing for pretty long time..
Webster, Stetson wrote:
Use 'aggr show_space' rather than 'df' and see if that makes a little more sense.
Stetson M. Webster Onsite Professional Services Engineer PS - North Amer. - East
NetApp 919.250.0052 Mobile Stetson.Webster@netapp.com www.netapp.com
-----Original Message----- From: Anna M [mailto:annpurna@gmail.com] Sent: Thursday, April 03, 2008 5:46 PM To: toasters@mathworks.com Subject: impact of setting snap reserve to 0
I have a volume with following details: [xxxhost ~yyy/zzz]# rsh xxxfiler df -h /vol/vol_1111_222 Filesystem total used avail capacity Mounted on /vol/vol_1111_222/ 453GB 422GB 31GB 93% /vol/vol_1111_222/ /vol/vol_1111_222/.snapshot 0GB 101GB 0GB ---% /vol/vol_1111_222/.snapshot
when I clone a new flexclone volume using this volume and try to get the used space of that newlyc loned volume, I see that used space value changes drastically in couple of seconds We have noticed that with in 17 seconds the used space reported for this newly cloned volume was altered to the tune of 76 GBs (starting from ~387 GB to ~311 GB).
Any clue as to why would this be heppening? Can it be because snap reserve is not set properly(we have set it to zero)? -- View this message in context: http://www.nabble.com/impact-of-setting-snap-reserve-to-0-tp16468497p164 68497.html Sent from the Network Appliance - Toasters mailing list archive at Nabble.com.