Thick provisoned LUNs inside thin provisoned volumes?

[sedakill1]

Hello All!

I've took over a FAS6280 and I'm trying to get a better understanding on how space is calculated using the following structure.

The engineer before me create all of his LUNs leveraging thick provisioning and then he put them in a volume that's thin provisioned. Where I'm getting confused is if I look at the volume's utilization it's showing as your would expect, i.e., the LUNs full thick provisoned size; however, if I look at the actual aggr utilization it doesn't show this space as being accounted for? Why is this?  

TIA!

MY second question is when you flip between thin vs thick provisioning is the space immediately returned?

[aborzenkov]

Space reservations on this provisioned volumes are not honored by containing aggregate. So in your case you have logical space reservation (in a volume) but it is not backed up by physical (in aggregate).

Отправлено с iPhone

29 нояб. 2013 г., в 0:42, "John Luin" <xdl-communities@communities.netapp.com<mailto:xdl-communities@communities.netapp.com>> написал(а):

<https://communities.netapp.com/index.jspa>

Thick provisoned LUNs inside thin provisoned volumes?

created by John Luin<https://communities.netapp.com/people/sedakill1> in Products & Solutions - View the full discussion<https://communities.netapp.com/message/121549#121549>

Hello All!

I've took over a FAS6280 and I'm trying to get a better understanding on how space is calculated using the following structure.

The engineer before me create all of his LUNs leveraging thick provisioning and then he put them in a volume that's thin provisioned. Where I'm getting confused is if I look at the volume's utilization it's showing as your would expect, i.e., the LUNs full thick provisoned size; however, if I look at the actual aggr utilization it doesn't show this space as being accounted for? Why is this?

TIA!

Reply to this message by replying to this email -or- go to the message on NetApp Community<https://communities.netapp.com/message/121549#121549>

Start a new discussion in Products & Solutions by email<mailto:discussions-community-products_and_solutions@communities.netapp.com> or at NetApp Community<https://communities.netapp.com/choose-container.jspa?contentType=1&containerType=14&container=2068>

[saranraj456]

Reclamation of space will be done slowly based on the removal of inode in background

[saranraj456]

depends on the usage /size of the volumes,

[radek_kubka]

Yes, this is very confusing with thick LUNs inside thin volumes. Volume reservation set to "file" gives a more logical outcome - if (and only if) a LUN is thick provisioned, the space will be reserved both in the containing volume & in the aggregate.

From my experience flipping between thick & thin provisioning returns reserved space immediately (the space isn't really filled with any data or zeroes, just reserved)

[saranraj456]

i meant the reclamation process will be slow , when it is filled by data .

Saran