Thn provision to thick provision

[saranraj456]

Hi.,

Is it possible to convert a thick provision vol to thin provision vol or viceversa,if so please provide the procedure for that..

Thanks,

Saran

[HENRYPAN2]

Saran,

The easiest way is to use the System Manager ->

Select the volume ->

Pick 'Edit' ->

In 'General' section, check or un-check 'Thin Provisioned'

Good luck

Henry

[saranraj456]

Thanks Henry..!

do we have any option to change the same on CLI, because of i am not used to system manager..

Saran

[HENRYPAN2 · Accepted solution]

Sure Saran,

2.4 COMMAND SUMMARY

This section describes the various commands and parameters that can be used in combination with thin provisioning. This information provides an overview of the commands, which are discussed in more detail later in this document.

Table 6) Provisioning commands and parameters. Command	Summary
Volume provisioning (new volume):   vol create flexvol_name aggr_name –s [volume|file|none] size [k|m|g|t]	Creates a FlexVol volume with the specified space guarantee type (volume, file, or none) and the desired size of the guaranteed space (KB, MB, GB, or TB). To use volume thin provisioning set guarantee to ―none.‖ To use volume thin provisioning but allow individual LUNs to reserve space at the aggregate level (for LUN-level thick provisioning) set guarantee to ―file.‖ To use volume thick provisioning set guarantee to ―volume.‖
Volume provisioning (existing volume):   vol options flexvol_name aggr_name guarantee [volume|file|none]	Changes the space guarantee setting of an existing FlexVol volume. To use volume thin provisioning set guarantee to ―none.‖ To use volume thin provisioning but allow individual LUNs to reserve space at the aggregate level (for LUN-level thick provisioning) set guarantee to ―file.‖ To use volume thick provisioning set guarantee to ―volume.‖
LUN overwrite reserve (fractional_reserve):   vol options flexvol_name fractional_reserve percent	Reserves space within a volume for LUNs to use for non-snapshot data after all other storage space in the volume is used. It is used as a safeguard so that there is enough space set aside in the volume for data that is being overwritten in the LUNs between Snapshot copies, even if large amounts of new data are written between Snapshot copies, causing the Snapshot copies to use up excessive space in the volume. (default = 100%)
Volume autosizing:   vol autosize flexvol_name [-m <size>[k|m|g|t]] [-i <size>[k|m|g|t]] [ on | off | reset ]	Determines if a volume should grow when nearly full (default = off)
Try_first:   vol options volname try_first [snap_delete|volume_grow]	Determines whether autovolume growing or auto Snapshot copy deleting is tried first
Volume snapshot reserve:   snap reserve –V flexvol_name percent	Reserves space within the volume for storing only Snapshot copies by removing the defined percentage of space from the volume (default = 20%)
Volume snapshot autodelete:   snap autodelete flexvol_name [on|off|show|reset|help]	Determines when (if) Snapshot copies will be automatically deleted (default = off)

Command	Summary
LUN provisioning (new LUN):   lun create -s size –t ostype [–o noreserve] lun_path	Creates a LUN with specified space guarantee type, reserve or noreserve (default = reserve). To use LUN thin provisioning use ― –o noreserve.‖ To use LUN thick provisioning omit ‖-o noreserve‖ and use default.   NOTE: LUN thick provisioning enables space to be available in the volume for the LUN, but does not ensure that space is available in the aggregate for the volume. See volume provisioning for more information.
LUN provisioning (existing LUN):   lun set reservation lun_path [enable|disable]	Changes the reserve setting of an existing LUN, enable or disable (default = enable). To use LUN thin provisioning set reservation to ―disable.‖ To use LUN thick provisioning, set reserve to ―enable.‖   NOTE: Setting the value of ―reserve‖ enables space to be available in the volume for the LUN, but does not ensure that space is available in the aggregate for the volume.

Good luck

Henry

[saranraj456]

Thanks a lot henry

[aborzenkov]

NetApp does not really have notion of thick vs. thin. There are multiple volume and LUN parameters that affect space allocation and reservation. Depending on your requirements, they may be set differently.

I suggest to read TR-3965 for detail description of various options that control space allocation.