We’re converting thin-provisioned luns to thick provisioned and it seems that to do that, we need extra storage space assigned to the volumes containing the luns. Example. a 450GB thin-provisioned lun requires around 620GB size volume to be able to convert it from thin to thick.
Each volume has one lun and when we convert the luns from thin to thick provisioning, it needed ~250GB added to the volume to be able to complete successfully. Right now the extra storage is less because I had the user run space reclamation and resized the volume, but it is still more than what they need. All they need is 450GB lun and the volume needs about 620GB to host a 450GB lun.
Could someone please explain this to me.
LUN Filer LUN Size (GB) Thick provisioned UN19 nas5 460 no UN20 nas5 470 no UN24 nas5 450 no UN28 nas5 450 no UN29 nas5 450 no UN30 nas5 450 no UN31 nas5 450 no
Thanks for reply. Actually I’m looking for something which explains me other way around. I’m converting a thin Lun to thick Lun but it requires almost 250GB more in the volume then actual lun size to convert it back to thick. Why is it asking for more space in the volume then needed for Lun?
Its something to do with Fractional reserve and snapshot reserve to gurantee space for the LUN when you convert to thick. NetApp handles thin and thick provisioning using reservers which gurantees space.
To understand more on fractional reserve you may have to read a bit since its not easy to describe for me over communities , sorry about that.I hope you should be able to understand it fast and justify the extra space 🙂
This FlexVol volume and file or LUN configuration combination provides the ability to use storage efficiency technologies and does not require you to actively monitor your free space, because sufficient space is allocated up front.
The following settings are required to configure a space-reserved file or LUN in a volume using thick provisioning:
Optional; if enabled, aggregate free space must be actively monitored.