Partager via


Thin Provisioning Threshold and Resource Exhaustion Test (LOGO)

This test verifies that target devices with thin provisioning feature meet Windows® requirements.

Test details

Associated requirements

Device.Storage.Hd.ThinProvisioning.BasicFunction

See the device hardware requirements.

Platforms

Windows Server 2012 (x64) Windows Server 2012 R2

Expected run time

~300 minutes

Categories

Certification Functional

Type

Automated

 

Running the test

Before you run the test, complete the test setup as described in the test requirements: Hard Disk Drive Testing Prerequisites.

Before you run the test, please make sure the thin provisioned LUN to be online initialized raw dis. Also, you should set the threshold for the thin provisioned LUN to be 70 percent (default). If the threshold is fixed, you should specify that threshold when running the test.

Troubleshooting

For troubleshooting information, see Troubleshooting Device.Storage Testing.

More information

The end to end scenario test would do threshold and resource exhaustion test. The main approach is to properly trigger the threshold notification/permanent resource exhaustion and check the sense key. When threshold is hit, we will get the log page to calculate whether the value to be at least no less than the value set for threshold. For temporary resource exhaustion, we just make this scenario to be optional, since some storage device may handle this scenario decently not to return any sense key.

Parameters

Parameter Description

TPDiskDeviceObjLink

The thin provisioned LUN.

TPDiskThresholdPercent

The percentage of the thin provisioned LUN.

Default value: 70

 

Command syntax

Command option Description

Thinprovision.exe /scenario exhaustion /thindisk "[TPDiskDeviceObjLink]" /percent “[TPDiskThresholdPercent]” /logo

Runs the test.

 

Note  

For command-line help for this test binary, type /h.

 

File list

File Location

Thinprovision.exe

<[testbinroot]>\nttest\driverstest\storage\wdk\thinprovision\

 

 

 

Send comments about this topic to Microsoft