Using our experience in the I/O industry, we have designed busSTRESS to test the I/O system in ways that can produce failures not often seen using traditional test tools. This can be an invaluable tool in helping you ensure that your I/O subsystem is reliable.
We allow you to adjust various stress test parameters including the number of stress test threads to run. When a failure occurs, or a data miscompare is detected, busSTRESS notifies you exactly which file system API failed and what the return code was. If a miscompare was detected, we show you what we wrote out and what was incorrectly read back.
One extremely valuable feature of busSTRESS is its complete integration with our busTRACE software bus analyzer. If you place a checkmark next to the "Capture with busTRACE" option, busTRACE can show you all of the captured busSTRESS file system APIs (e.g. CreateFile(), WriteFile(), ReadFile(), etc.) as well as any underlying Command Descriptor Blocks.
If a file system API were to fail, you would be able to see exactly which low-level CDB failed and what sense code was returned from the device. You can then save the busTRACE results to file and share with others.