The total space for vol0 does *not* include the SnapShot space. The real total space is the vol0 space PLUS the snapshot space. You will see this if you play with the SnapShot reserve space. Change the value and the values change.
If your SnapShot reserve fills, it does start eating active filesystem space. The snaphost reserve line will then exceed 100%. The volume may not. If, for example, you had a 5% snap reserve, but your snapshots were chewing up 10% of the total volume space, then the snap reserve would be at 200%, but the vol0 space would still be at the capacity of the total blocks used, both active and snapshots which could very well be below 100% utilization.
I hope this isn't too confusing. Let me know if you have further questions.
-- Adam Fox NetApp Professional Services, NC adamfox@netapp.com
-----Original Message----- From: Julius Talbot [mailto:jstalbot@mail.com] Sent: Wednesday, August 29, 2001 11:44 AM To: toasters@mathworks.com Subject: Ok, one last questions: Snapshots
Sorry for the newbie questions, one last question
When I do a df, for instance
/vol/vol0/ 127105232 748236 26356996 1% /vol/vol0/ /vol/vol0/.snapshot 31776304 4548 31771756 0% /vol/vol0/.snapsh ot
Does vol0's capacity include the snapshot capacity? That is to say, vol0 is really 127105232? Or, is vol0 really that plus the reserved snapshot capacity, in this case, 127105232
- 31776304?
Second I do understand from the documentation that if that snapshot exceeds the specified size, it will eat up the volumes capacity. In this case, both vol0 and snapshot would reflect the exceed capacity, right? --
FREE Personalized E-mail at Mail.com http://www.mail.com/?sr=signup
Talk More, Pay Less with Net2Phone Direct(R), up to 1500 minutes free! http://www.net2phone.com/cgi-bin/link.cgi?143