2012-01-13 12:43 AM
The documentation defines this alarm as:
Specifies the percentage(100% default) at which a volume is considered to have consumed the whole of the overcommitted space for that volume.
How should we understand that?
- Thin prov enabled (aka reserve=none)
- Space used in this thin prov volume = size of the volume as defined as defined when created?
Thanks for your help
Solved! SEE THE SOLUTION
2012-01-13 01:51 AM
This value is that when a thin provisioned volume is created with a size of 2TB and now the current data in the volume is equal to size of the Volume which was created then you would get this error.
Size of the volume at the time of creation : 2TB ( thin provisioned)
During the course of time the data increased and now the cureent size of the data is 2TB .
Then this message would pop up in DFM
2012-01-13 02:14 AM
Yes as per the defnition the result would be the same , herewith pasting excerpt from the DFM documentation
The corrective on both case is to free some space . Refer link below for more details
2012-01-13 02:16 AM
No. Its not.
Volume Quota overcommitment is due to the oversubscription of qtree quotas inside the volume.Lets take the example of 10 GB volume
Now inside that volume if you create a 5 qtrees with 3GB quota then the volume is over committed by 5GB or 50% due to the quota since the volume itself is only 10GB.
Where as Aggregate Overcommitment is due to the oversubscription of volumes in that aggr. Lets again take an example of 100GB aggr.
Now inside that aggr if you create 5 volume of 10GB then the aggr is not overcommitted.But if you create 5 volume of 25 GB each ( This can only be done if the volume guarantee is set to none) then the aggr is overcommited by 25 GB for 25%.
Hope this helps.