Disk Stress (LOGO)

This test stresses disks on a computer by sending as much asynchronous I/O as the device can handle. The test should reach the bandwidth limit of the test device for the given test system configuration.

Test details

Running the test

Before you run the test, complete the test setup as described in the following test requirements:

• Hard Disk Drive Testing Prerequisites

• Optical Disk Drive Testing Prerequisites

If you are testing any drive that requires media or testing in system-mode on a computer that contains drives that require media, you must insert media into the drives. The media that is used must be formatted and contain data that occupies at least 50% of the media's capacity.

Troubleshooting

For troubleshooting information, see Troubleshooting Device.Storage Testing.

More information

The test is passed the instance path of the target test device. It finds all hard disks and optical drives that are equal to or connected to the test device. The test will then go through the following scenarios on all of the found devices:

• Sequential read

• Sequential write

• Sequential verify (write followed by read and comparison)

• Random read

• Random write

• Random verify

The test is given a fixed run time and runs each scenario for a fraction of that time. In the case of six scenarios and a run time of 90 minutes, each scenario is run for 15 minutes. The test displays dialog boxes with the progress of the current scenario. Any write scenarios (including verify) are skipped for optical devices. The size of the individual data transfers is determined by a command-line parameter; the default size for the logo test is 32 KB.

The test tries to do raw writes, bypassing any file system that is mounted on the hard disk if it can. The test attempts raw writes if one of the following occurs:

• The test can find a raw, unpartitioned disk.

• The test can find a raw, unformatted volume.

• The test can find a volume that it can dismount.

If none of the preceding situations are available, the test performs I/O through the file system. This action is more CPU intensive and might not give accurate bandwidth and latency measurements for the device. In the third situation (the test finds a volume that it can dismount), which is the most common mode that the test is run in, the test allocates a test file to use and writes only to the extents of that file. This situation ensures that the test never corrupts the file system of the device that it is testing.

The amount of space that the test uses is determined by the free space that is available on the test device. To ensure best device performance, you should delete any unnecessary files from the test device and should cleanly format or defragment the device before running the test. The test warns you if the target's fragmentation might influence the test results.

Even though this test does measure device performance, there is currently no test case in the Logo version of this test that passes or fails based on these measurements.

Command syntax

Warning  

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

File list

Send comments about this topic to Microsoft