Solved: Snapdrive 7.1.2 - This volume is not designated for thin provisioning.

ol15 · ‎2016-01-18

hello,

snapdrive 7.1.2

7-Mode: 8.2.3P6

i have this info log on my filer /etc/messages :

Mon Jan 18 13:21:04 CET [nache13a:app.log.info:info]: serv_name: SnapDrive 7.1.2: (380) Service execution status: Found non-space reserved LUN(s) on volume '/vol/XXXXXXXXX1'. This volume is not designated for thin provisioning.

what does it mean ?

it has option with guarantee=none, and created with snapdrive with "tin provisioning" checkbox

how to resolve this message ?

regards

georgevj · ‎2016-01-25

[nache13a:app.log.info:info]:

This is a message of severity level "info" , being issued for information purpose only. No need to worry about this message.

What this means is that the volume where the LUN resides is not designated for thin provisioning, as the volume itself is already thin provisioned. Please note that if the volume is created with space guarantee set to "none", that volume, and the files created within it including LUNs, will be all thin provisioned. For now, you can ignore this message.

If this post resolved your issue, help others by selecting ACCEPT AS SOLUTION or adding a KUDO.
Cannot find the answer you need? No need to open a support case - just CHAT and we’ll handle it for you.

View solution in original post

Sahana · ‎2016-01-24

Hi

Try storacl command. refer https://library.netapp.com/ecmdocs/ECMP1189419/html/GUID-FD1A83AF-37B6-409D-9E37-63BDAC79C63A.html

If this post resolved your issue, help others by selecting ACCEPT AS SOLUTION or adding a KUDO.

georgevj · ‎2016-01-25

[nache13a:app.log.info:info]:

This is a message of severity level "info" , being issued for information purpose only. No need to worry about this message.

What this means is that the volume where the LUN resides is not designated for thin provisioning, as the volume itself is already thin provisioned. Please note that if the volume is created with space guarantee set to "none", that volume, and the files created within it including LUNs, will be all thin provisioned. For now, you can ignore this message.

If this post resolved your issue, help others by selecting ACCEPT AS SOLUTION or adding a KUDO.
Cannot find the answer you need? No need to open a support case - just CHAT and we’ll handle it for you.