Understanding SCVMM LUN allocation

TRYAREBOOT · ‎2014-05-13

We are running SCVMM on a Cisco UCS with a FAS3220 with both shelves filled there a mix of HDD and SSD in each so we have 2 aggregates one on each shelf utilizing flash pools. Each aggregate is approximately 17TB.

We have created a bunch of LUN's from within SCVMM utilizing the SMI-S provider and they are mounted as clustered shared volumes but they only seem to add up the approximately half the capacity of the aggregate yet we cannot create any more?

I am sure there must be a valid reason for this but I don't seem to be able to find it!

Can anybody enlighten me?

Thanks

Andrew

TRYAREBOOT · ‎2014-05-20

So does nobody else on here run with a similar config then? Or possible I am asking in the wrong place?

Thanks

psrao · ‎2014-05-20

Andrew,

Could you please tell us the capacities of HDD and SSD drives. Also, give us the sizes of all the luns on the aggregates?

Please send us the trace/log files of the agent also.

- Sreeni

TRYAREBOOT · ‎2014-05-22

OK here is some more detail.

WILNAS7756> aggr status aggrFP1 -r

Aggregate aggrFP1 (online, raid_dp, hybrid) (block checksums)

Plex /aggrFP1/plex0 (online, normal, active)

RAID group /aggrFP1/plex0/rg0 (normal, block checksums)

RAID Disk Device HA SHELF BAY CHAN Pool Type RPM Used (MB/blks) Phys (MB/blks)

--------- ------ ------------- ---- ---- ---- ----- -------------- --------------

dparity 0b.01.0 0b 1 0 SA:A 0 BSAS 7200 1695466/3472315904 1695759/3472914816

parity 0a.00.1 0a 0 1 SA:B 0 BSAS 7200 1695466/3472315904 1695759/3472914816

data 0b.01.1 0b 1 1 SA:A 0 BSAS 7200 1695466/3472315904 1695759/3472914816

data 0b.01.2 0b 1 2 SA:A 0 BSAS 7200 1695466/3472315904 1695759/3472914816

data 0b.01.3 0b 1 3 SA:A 0 BSAS 7200 1695466/3472315904 1695759/3472914816

data 0b.01.4 0b 1 4 SA:A 0 BSAS 7200 1695466/3472315904 1695759/3472914816

data 0b.01.5 0b 1 5 SA:A 0 BSAS 7200 1695466/3472315904 1695759/3472914816

data 0b.01.6 0b 1 6 SA:A 0 BSAS 7200 1695466/3472315904 1695759/3472914816

data 0b.01.7 0b 1 7 SA:A 0 BSAS 7200 1695466/3472315904 1695759/3472914816

data 0b.01.8 0b 1 8 SA:A 0 BSAS 7200 1695466/3472315904 1695759/3472914816

data 0b.01.9 0b 1 9 SA:A 0 BSAS 7200 1695466/3472315904 1695759/3472914816

data 0b.01.10 0b 1 10 SA:A 0 BSAS 7200 1695466/3472315904 1695759/3472914816

data 0b.01.11 0b 1 11 SA:A 0 BSAS 7200 1695466/3472315904 1695759/3472914816

data 0b.01.12 0b 1 12 SA:A 0 BSAS 7200 1695466/3472315904 1695759/3472914816

RAID group /aggrFP1/plex0/rg1 (normal, block checksums)

RAID Disk Device HA SHELF BAY CHAN Pool Type RPM Used (MB/blks) Phys (MB/blks)

--------- ------ ------------- ---- ---- ---- ----- -------------- --------------

dparity 0b.01.13 0b 1 13 SA:A 0 BSAS 7200 1695466/3472315904 1695759/3472914816

parity 0b.01.14 0b 1 14 SA:A 0 BSAS 7200 1695466/3472315904 1695759/3472914816

data 0b.01.15 0b 1 15 SA:A 0 BSAS 7200 1695466/3472315904 1695759/3472914816

data 0b.01.16 0b 1 16 SA:A 0 BSAS 7200 1695466/3472315904 1695759/3472914816

RAID group /aggrFP1/plex0/rg2 (normal, block checksums)

RAID Disk Device HA SHELF BAY CHAN Pool Type RPM Used (MB/blks) Phys (MB/blks)

--------- ------ ------------- ---- ---- ---- ----- -------------- --------------

dparity 0b.01.18 0b 1 18 SA:A 0 SSD N/A 190532/390209536 190782/390721968

parity 0b.01.19 0b 1 19 SA:A 0 SSD N/A 190532/390209536 190782/390721968

data 0b.01.20 0b 1 20 SA:A 0 SSD N/A 190532/390209536 190782/390721968

data 0b.01.21 0b 1 21 SA:A 0 SSD N/A 190532/390209536 190782/390721968

data 0b.01.22 0b 1 22 SA:A 0 SSD N/A 190532/390209536 190782/390721968

WILNAS7756> aggr status aggrFP1 -S

Aggregate : aggrFP1

Feature Used Used%

-------------------------------- ---------- ------

Volume Footprints 1.38TB 7%

Aggregate Metadata 23.8MB 0%

Total Used 1.38TB 7%

Created a 1024GB LUN in SCVMM

WILNAS7756> aggr status aggrFP1 -S

Aggregate : aggrFP1

Feature Used Used%

-------------------------------- ---------- ------

Volume Footprints 3.59TB 18%

Aggregate Metadata 23.8MB 0%

Total Used 3.59TB 18%

So my 1TB LUN appears to be taking over 2TB of space

Looking at the volumes I see that vol1 was created to store the LUN in. Looking at the details of that.

WILNAS7756> vol status vol1 -v

Volume State Status Options

vol1 online raid_dp, flex nosnap=off, nosnapdir=off, minra=off,

64-bit no_atime_update=off, nvfail=off,

hybrid ignore_inconsistent=off, snapmirrored=off,

create_ucode=off, convert_ucode=off,

maxdirsize=73400, schedsnapname=ordinal,

fs_size_fixed=off, guarantee=volume,

svo_enable=off, svo_checksum=off,

svo_allow_rman=off, svo_reject_errors=off,

no_i2p=off, fractional_reserve=100, extent=off,

try_first=volume_grow, read_realloc=off,

snapshot_clone_dependency=off,

dlog_hole_reserve=off, nbu_archival_snap=off

Volume UUID: d321f31e-b35e-4284-a335-92d3d3670adb

Containing aggregate: 'aggrFP1'

Plex /aggrFP1/plex0: online, normal, active

RAID group /aggrFP1/plex0/rg0: normal, block checksums

RAID group /aggrFP1/plex0/rg1: normal, block checksums

RAID group /aggrFP1/plex0/rg2: normal, block checksums

Snapshot autodelete settings for vol1:

state=off

commitment=try

trigger=volume

target_free_space=20%

delete_order=oldest_first

defer_delete=user_created

prefix=(not specified)

destroy_list=none

Volume autosize settings:

mode=grow

maximum-size=2834930072 KB

increment-size=118122084 KB

minimum-size=2253 GB

grow-threshold-percent=98%

shrink-threshold-percent=50%

Hybrid Cache:

Eligibility=read-write

So for my 1TB LUN a vol has been created with autogrow enabled consuming more than twice the capacity I needed.

I have a the trace log but its rather big. This piece seems to most relevant

21-May-2014 16:12:49.788: XmlIO [1032:0:HTTPConnection.cpp:2328]:

POST /cimom HTTP/1.1

Connection: Keep-Alive

Content-Type: application/xml; charset="utf-8"

Authorization: Basic XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Host: KNU-WDS01.WBIEGAMES.COM

User-Agent: msftsm

CIMOperation: MethodCall

CIMMethod: CreateOrModifyElementFromStoragePool

CIMObject: root%2Fontap%3AONTAP_StorageConfigurationService.CreationClassName%3D%22ONTAP_StorageConfigurationService%22%2CName%3D%22ONTAP_Storage_Configuration_Service%22%2CSystemCreationClassName%3D%22ONTAP_StorageSystem%22%2CSystemName%3D%22ONTAP%3A2015532851%22

Content-Length: 2309

<?xml version="1.0" encoding="UTF-8"?>

</LOCALNAMESPACEPATH>

<KEYVALUE VALUETYPE="string">ONTAP_StorageConfigurationService</KEYVALUE>

</KEYBINDING>

<KEYVALUE VALUETYPE="string">ONTAP_Storage_Configuration_Service</KEYVALUE>

</KEYBINDING>

<KEYVALUE VALUETYPE="string">ONTAP_StorageSystem</KEYVALUE>

</KEYBINDING>

<KEYVALUE VALUETYPE="string">ONTAP:2015532851</KEYVALUE>

</KEYBINDING>

</INSTANCENAME>

</LOCALINSTANCEPATH>

<VALUE>TestLun01</VALUE>

</PARAMVALUE>

</PARAMVALUE>

<VALUE.REFERENCE>

</LOCALNAMESPACEPATH>

<KEYVALUE VALUETYPE="string">ONTAP:2015532851:6e72b5e5-8412-4a22-8763-8df46023f95f</KEYVALUE>

</KEYBINDING>

</INSTANCENAME>

</LOCALINSTANCEPATH>

</VALUE.REFERENCE>

</PARAMVALUE>

</PARAMVALUE>

</METHODCALL>

</SIMPLEREQ>

</MESSAGE>

</CIM>

21-May-2014 16:12:49.788: Authentication [1032:HTTPAuthenticatorDelegator.cpp:427]: HTTPAuthenticatorDelegator - Authentication processing start

21-May-2014 16:12:49.788: Authentication [1032:HTTPAuthenticatorDelegator.cpp:1107]: HTTPAuthenticatorDelegator - Authentication processing ended

21-May-2014 16:12:49.819: Thread [1032:ThreadPool.cpp:330]: Initializing thread(1404) with work function and parameters: parm = 0159FF70

21-May-2014 16:12:49.819: Thread [1032:ThreadPool.cpp:350]: Signal thread to awaken

21-May-2014 16:12:49.819: Thread [1032:ThreadPool.cpp:221]: Work starting.

21-May-2014 16:12:49.819: Thread [1032:1896:ThreadPool.cpp:330]: Initializing thread(1512) with work function and parameters: parm = 0159FF70

21-May-2014 16:12:49.819: Thread [1032:ThreadPool.cpp:350]: Signal thread to awaken

21-May-2014 16:12:49.819: Thread [1032:ThreadPool.cpp:221]: Work starting.

21-May-2014 16:12:49.819: ProviderManager [1032:1932:BasicProviderManagerRouter.cpp:420]: Provider Manager for interfaceType 'CMPI' already loaded.

21-May-2014 16:12:49.819: ProviderManager [1032:1932:CMPIProviderManager.cpp:1753]: CMPIProviderManager::handleInvokeMethodRequest - Host name: KNU-WDS01 Name space: root/ontap Class name: ONTAP_StorageConfigurationService

21-May-2014 16:12:49.819: ProviderManager [1032:CMPILocalProviderManager.cpp:117]: CMPILocalProviderManager::_provider_ctrl:GET_PROVIDER()

21-May-2014 16:12:49.819: ProviderManager [1032:1932:CMPILocalProviderManager.cpp:1039]: Found Provider LONTAP_StorageConfigurationService in CMPI Provider Manager Cache

21-May-2014 16:12:49.819: ProviderManager [1032:1932:CMPILocalProviderManager.cpp:1073]: Found Provider Module C:\Program Files (x86)\Ontap\smis\pegasus/bin/ONTAP_StorageConfigurationService.dll in Provider Manager Cache

21-May-2014 16:12:49.819: ProviderManager [1032:1932:CMPILocalProviderManager.cpp:836]: Loading/Linking Provider Module C:\Program Files (x86)\Ontap\smis\pegasus/bin/ONTAP_StorageConfigurationService.dll

21-May-2014 16:12:49.819: ProviderManager [1032:1932:CMPILocalProviderManager.cpp:868]: Initializing Provider ONTAP_StorageConfigurationService

21-May-2014 16:12:49.819: ProviderManager [1032:1932:CMPILocalProviderManager.cpp:150]: Returning Provider LONTAP_StorageConfigurationService

21-May-2014 16:12:49.819: ProviderManager [1032:1932:CMPIProviderManager.cpp:1798]: Calling provider.invokeMethod: ONTAP_StorageConfigurationService

21-May-2014 16:12:49.819: CMPIProvider [1032:1932:CMPI_BrokerEnc.cpp:1424]: ONTAP_StorageConfigurationService: CreateOrModifyElementFromStoragePool operation starting

21-May-2014 16:12:49.819: CMPIProvider [1032:1932:CMPI_BrokerEnc.cpp:1424]: ONTAP_StorageConfigurationService: Extracting ElementName parameter

21-May-2014 16:12:49.819: CMPIProvider [1032:1932:CMPI_BrokerEnc.cpp:1424]: ONTAP_StorageConfigurationService: Extracting ElementType parameter

21-May-2014 16:12:49.819: CMPIProvider [1032:1932:CMPI_BrokerEnc.cpp:1424]: ONTAP_StorageConfigurationService: Extracting Size parameter

21-May-2014 16:12:49.819: CMPIProvider [1032:1932:CMPI_BrokerEnc.cpp:1424]: ONTAP_StorageConfigurationService: Extracting TheElement parameter

21-May-2014 16:12:49.819: CMPIProvider [1032:1932:CMPI_BrokerEnc.cpp:1424]: ONTAP_StorageConfigurationService: Extracting Pool parameter

21-May-2014 16:12:49.819: CMPIProvider [1032:1932:CMPI_BrokerEnc.cpp:1424]: ONTAP_StorageConfigurationService: create Storage Volume operation starting

21-May-2014 16:12:49.819: CMPIProvider [1032:1932:CMPI_BrokerEnc.cpp:1424]: ONTAP_StorageConfigurationService: Choosing name for flexible volume

21-May-2014 16:12:49.819: CMPIProvider [1032:1932:CMPI_BrokerEnc.cpp:1424]: ONTAP_StorageConfigurationService: Flexible Volume name chosen

21-May-2014 16:12:49.819: CMPIProvider [1032:1932:CMPI_BrokerEnc.cpp:1424]: wbemontapi: Calling na_server_invoke_elem on filer: 10.103.85.247, API:

<volume-create>

<containing-aggr-name>aggrFP1</containing-aggr-name>

<space-reserve>volume</space-reserve>

</volume-create>

21-May-2014 16:12:49.819: Thread [1032:ThreadPool.cpp:224]: Work finished.

21-May-2014 16:12:51.840: CMPIProvider [1032:1932:CMPI_BrokerEnc.cpp:1424]: wbemontapi: ONTAP Invoke: na_server_invoke_elem completed

21-May-2014 16:12:51.840: CMPIProvider [1032:1932:CMPI_BrokerEnc.cpp:1424]: wbemontapi: Calling na_server_invoke_elem on filer: 10.103.85.247, API:

<volume-get-root-name/>

21-May-2014 16:12:51.860: CMPIProvider [1032:1932:CMPI_BrokerEnc.cpp:1424]: wbemontapi: ONTAP Invoke: na_server_invoke_elem completed

21-May-2014 16:12:51.860: CMPIProvider [1032:1932:CMPI_BrokerEnc.cpp:1424]: wbemontapi: Calling na_server_invoke_elem on filer: 10.103.85.247, API:

<volume-list-info>

</volume-list-info>

21-May-2014 16:12:51.878: CMPIProvider [1032:1932:CMPI_BrokerEnc.cpp:1424]: wbemontapi: ONTAP Invoke: na_server_invoke_elem completed

21-May-2014 16:12:51.878: CMPIProvider [1032:CMPI_BrokerEnc.cpp:1424]: wbemontapi: Calling na_server_invoke_elem on filer: 10.103.85.247, API:

<snapshot-get-reserve>

</snapshot-get-reserve>

21-May-2014 16:12:51.878: CMPIProvider [1032:CMPI_BrokerEnc.cpp:1424]: wbemontapi: ONTAP Invoke: na_server_invoke_elem completed

21-May-2014 16:12:51.878: CMPIProvider [1032:CMPI_BrokerEnc.cpp:1424]: wbemontapi: Calling na_server_invoke_elem on filer: 10.103.85.247, API:

<snapshot-list-info>

</snapshot-list-info>

21-May-2014 16:12:51.878: CMPIProvider [1032:CMPI_BrokerEnc.cpp:1424]: wbemontapi: ONTAP Invoke: na_server_invoke_elem completed

21-May-2014 16:12:53.878: CMPIProvider [1032:1932:CMPI_BrokerEnc.cpp:1424]: wbemontapi: Calling na_server_invoke_elem on filer: 10.103.85.247, API:

<aggr-list-info>

<aggregate>aggrFP1</aggregate>

</aggr-list-info>

21-May-2014 16:12:53.894: CMPIProvider [1032:1932:CMPI_BrokerEnc.cpp:1424]: wbemontapi: ONTAP Invoke: na_server_invoke_elem completed

21-May-2014 16:12:53.894: CMPIProvider [1032:1932:CMPI_BrokerEnc.cpp:1424]: wbemontapi: Calling na_server_invoke_elem on filer: 10.103.85.247, API:

<system-get-version/>

21-May-2014 16:12:53.910: CMPIProvider [1032:1932:CMPI_BrokerEnc.cpp:1424]: wbemontapi: ONTAP Invoke: na_server_invoke_elem completed

21-May-2014 16:12:53.910: CMPIProvider [1032:CMPI_BrokerEnc.cpp:1424]: wbemontapi: Calling na_server_invoke_elem on filer: 10.103.85.247, API:

<perf-object-get-instances>

<objectname>volume</objectname>

</instances>

<counter>wv_fsinfo_blks_total</counter>

<counter>wv_fsinfo_blks_reserve</counter>

<counter>wv_fsinfo_blks_used</counter>

<counter>wv_fsinfo_blks_used_by_plane0</counter>

<counter>wv_fsinfo_blks_blks_rsrv_holes</counter>

<counter>wv_fsinfo_blks_blks_rsrv_overwrite</counter>

<counter>wv_fsinfo_blks_overwrite_slider_pct</counter>

<counter>wvblk_snap_reserve</counter>

<counter>wv_fsinfo_blks_snap_reserve_pct</counter>

</counters>

</perf-object-get-instances>

21-May-2014 16:12:53.910: CMPIProvider [1032:CMPI_BrokerEnc.cpp:1424]: wbemontapi: ONTAP Invoke: na_server_invoke_elem completed

21-May-2014 16:12:55.923: CMPIProvider [1032:1932:CMPI_BrokerEnc.cpp:1424]: wbemontapi: Calling na_server_invoke_elem on filer: 10.103.85.247, API:

<volume-autosize-set>

<is-enabled>true</is-enabled>

</volume-autosize-set>

21-May-2014 16:12:55.939: CMPIProvider [1032:1932:CMPI_BrokerEnc.cpp:1424]: wbemontapi: ONTAP Invoke: na_server_invoke_elem completed

21-May-2014 16:12:55.939: CMPIProvider [1032:1932:CMPI_BrokerEnc.cpp:1424]: ONTAP_StorageConfigurationService: create Flexible volume operation completed successfully.

21-May-2014 16:12:55.939: CMPIProvider [1032:1932:CMPI_BrokerEnc.cpp:1424]: ONTAP_StorageConfigurationService: Invoking lun-create by size operation

21-May-2014 16:12:55.939: CMPIProvider [1032:1932:CMPI_BrokerEnc.cpp:1424]: wbemontapi: Calling na_server_invoke_elem on filer: 10.103.85.247, API:

<lun-create-by-size>

<path>/vol/vol1/TestLun01</path>

<ostype>hyper_v</ostype>

<space-reservation-enabled>true</space-reservation-enabled>

</lun-create-by-size>

21-May-2014 16:12:55.954: CMPIProvider [1032:1932:CMPI_BrokerEnc.cpp:1424]: wbemontapi: ONTAP Invoke: na_server_invoke_elem completed

21-May-2014 16:12:55.954: CMPIProvider [1032:1932:CMPI_BrokerEnc.cpp:1424]: wbemontapi: Calling na_server_invoke_elem on filer: 10.103.85.247, API:

<lun-list-info>

<path>/vol/vol1/TestLun01</path>

</lun-list-info>

21-May-2014 16:12:55.970: CMPIProvider [1032:1932:CMPI_BrokerEnc.cpp:1424]: wbemontapi: ONTAP Invoke: na_server_invoke_elem completed

21-May-2014 16:12:55.970: CMPIProvider [1032:1932:CMPI_BrokerEnc.cpp:1424]: wbemontapi: Calling na_server_invoke_elem on filer: 10.103.85.247, API:

<lun-stats-list-info>

<path>/vol/vol1/TestLun01</path>

</lun-stats-list-info>

21-May-2014 16:12:55.988: CMPIProvider [1032:1932:CMPI_BrokerEnc.cpp:1424]: wbemontapi: ONTAP Invoke: na_server_invoke_elem completed

21-May-2014 16:12:55.988: CMPIProvider [1032:1932:CMPI_BrokerEnc.cpp:1424]: wbemontapi: Calling na_server_invoke_elem on filer: 10.103.85.247, API:

<volume-get-root-name/>

21-May-2014 16:12:56.4: CMPIProvider [1032:1932:CMPI_BrokerEnc.cpp:1424]: wbemontapi: ONTAP Invoke: na_server_invoke_elem completed

21-May-2014 16:12:56.4: CMPIProvider [1032:1932:CMPI_BrokerEnc.cpp:1424]: wbemontapi: Calling na_server_invoke_elem on filer: 10.103.85.247, API:

<volume-list-info>

</volume-list-info>

21-May-2014 16:12:56.19: CMPIProvider [1032:1932:CMPI_BrokerEnc.cpp:1424]: wbemontapi: ONTAP Invoke: na_server_invoke_elem completed

21-May-2014 16:12:56.19: CMPIProvider [1032:CMPI_BrokerEnc.cpp:1424]: wbemontapi: Calling na_server_invoke_elem on filer: 10.103.85.247, API:

<snapshot-get-reserve>

</snapshot-get-reserve>

21-May-2014 16:12:56.19: CMPIProvider [1032:CMPI_BrokerEnc.cpp:1424]: wbemontapi: ONTAP Invoke: na_server_invoke_elem completed

21-May-2014 16:12:56.19: CMPIProvider [1032:CMPI_BrokerEnc.cpp:1424]: wbemontapi: Calling na_server_invoke_elem on filer: 10.103.85.247, API:

<snapshot-list-info>

</snapshot-list-info>

21-May-2014 16:12:56.19: CMPIProvider [1032:CMPI_BrokerEnc.cpp:1424]: wbemontapi: ONTAP Invoke: na_server_invoke_elem completed

21-May-2014 16:12:58.20: CMPIProvider [1032:1932:CMPI_BrokerEnc.cpp:1424]: wbemontapi: Calling na_server_invoke_elem on filer: 10.103.85.247, API:

<aggr-list-info>

<aggregate>aggrFP1</aggregate>

</aggr-list-info>

21-May-2014 16:12:58.36: CMPIProvider [1032:1932:CMPI_BrokerEnc.cpp:1424]: wbemontapi: ONTAP Invoke: na_server_invoke_elem completed

21-May-2014 16:12:58.36: CMPIProvider [1032:1932:CMPI_BrokerEnc.cpp:1424]: wbemontapi: Calling na_server_invoke_elem on filer: 10.103.85.247, API:

<system-get-version/>

21-May-2014 16:12:58.52: CMPIProvider [1032:1932:CMPI_BrokerEnc.cpp:1424]: wbemontapi: ONTAP Invoke: na_server_invoke_elem completed

21-May-2014 16:12:58.52: CMPIProvider [1032:CMPI_BrokerEnc.cpp:1424]: wbemontapi: Calling na_server_invoke_elem on filer: 10.103.85.247, API:

<perf-object-get-instances>

<objectname>volume</objectname>

</instances>

<counter>wv_fsinfo_blks_total</counter>

<counter>wv_fsinfo_blks_reserve</counter>

<counter>wv_fsinfo_blks_used</counter>

<counter>wv_fsinfo_blks_used_by_plane0</counter>

<counter>wv_fsinfo_blks_blks_rsrv_holes</counter>

<counter>wv_fsinfo_blks_blks_rsrv_overwrite</counter>

<counter>wv_fsinfo_blks_overwrite_slider_pct</counter>

<counter>wvblk_snap_reserve</counter>

<counter>wv_fsinfo_blks_snap_reserve_pct</counter>

</counters>

</perf-object-get-instances>

21-May-2014 16:12:58.52: CMPIProvider [1032:CMPI_BrokerEnc.cpp:1424]: wbemontapi: ONTAP Invoke: na_server_invoke_elem completed

21-May-2014 16:13:00.59: CMPIProvider [1032:1932:CMPI_BrokerEnc.cpp:1424]: ONTAP_StorageConfigurationService: lun-create by size succeeed

21-May-2014 16:13:00.59: CMPIProvider [1032:1932:CMPI_BrokerEnc.cpp:1424]: ONTAP_StorageConfigurationService: Storage Volume creation succeeded

21-May-2014 16:13:00.90: ProviderManager [1032:SimpleResponseHandler.cpp:57]: SimpleResponseHandler::processing()

21-May-2014 16:13:00.90: ProviderManager [1032:SimpleResponseHandler.cpp:330]: SimpleMethodResultResponseHandler::deliver()

21-May-2014 16:13:00.90: ProviderManager [1032:1932:CMPIProviderManager.cpp:1819]: Returning from provider.invokeMethod: ONTAP_StorageConfigurationService

21-May-2014 16:13:00.90: ProviderManager [1032:SimpleResponseHandler.cpp:66]: SimpleResponseHandler::complete()

21-May-2014 16:13:00.90: ProviderManager [1032:1932:OperationResponseHandler.cpp:256]: InvokeMethodResponseHandler::transfer

21-May-2014 16:13:00.90: ProviderManager [1032:SimpleResponseHandler.cpp:87]: SimpleResponseHandler: getLanguages()

21-May-2014 16:13:00.90: Thread [1032:ThreadPool.cpp:224]: Work finished.

21-May-2014 16:13:00.90: Thread [1032:ThreadPool.cpp:330]: Initializing thread(1512) with work function and parameters: parm = 015E66C8

21-May-2014 16:13:00.90: Thread [1032:ThreadPool.cpp:350]: Signal thread to awaken

21-May-2014 16:13:00.90: Thread [1032:ThreadPool.cpp:221]: Work starting.

21-May-2014 16:13:00.90: XmlIO [1032:1932:HTTPConnection.cpp:935]:

HTTP/1.1 200 OK

Content-Type: application/xml; charset=utf-8

content-length: 0000001193

CIMOperation: MethodResponse

TRYAREBOOT · ‎2014-11-05

I know this was back in May but we are still plagued with this issue. Any pointers on how to procede? Should I just log a support incident?

nigelslocum · ‎2014-11-05

I have not used the SMI-S plugin but it would appear that the volume created is sized according to traditional thick provisioning rules. LUN size x2 +snapshot space. So for a 1TB LUN you need 2TB volume plus snapshot space which is typically 20% leaving you with a 2200g volume. This guarantee's space of the entire LUN and 100% overwrite and snapshots.

Have a look and see if you can configure the volume provisioning settings. I suggest reading up on thin provisioning and deciding if you prefer to use that method as it will save space within the aggregate. Just remember if you plan on overcommiting your aggregate you need to have good monitoring in place.

vinith · ‎2014-11-05

Please raise a support ticket while we reproduce this in our labs.

Community

Understanding SCVMM LUN allocation

Understanding SCVMM LUN allocation

Re: Understanding SCVMM LUN allocation

Re: Understanding SCVMM LUN allocation

Re: Understanding SCVMM LUN allocation

Re: Understanding SCVMM LUN allocation

Re: Understanding SCVMM LUN allocation