conf-sanity
|
A set of unit tests that verify the configuration tools, and runs Lustre with multiple different setups to ensure correct operation in unusual system configurations. (Source HPDD Wiki Auster)
|
insanity
|
A set of tests that verify the multiple concurrent failure conditions. (Source HPDD Wiki Auster)
|
lfsck
|
Tests e2fsck and lfsck to detect and fix filesystem corruption. (Source HPDD Wiki Auster)
|
lnet-selftest
|
Runs LNET self test on hosts defined in test configuration.
|
lustre-rsync-test
|
|
metadata-updates
|
A Metadata Update Test tests that metadata updates are properly completed when multiple clients create/delete files and modify the attributes of files.
|
mmp
|
Tests for multiple mount protection (MMP) feature.
|
ost-pools
|
A tests that exercises the OST pools feature.
|
racer
|
A test that attempts to create race conditions.
|
recovery-small
|
A set of unit tests that verify RPC replay after communications failure. (Source HPDD Wiki Auster)
|
replay-dual
|
A set of unit tests that verify the recovery from two clients after server failure. (Source HPDD Wiki Auster)
|
replay-ost-single
|
A set of unit tests that verify recovery after OST failure. (Source HPDD Wiki Auster)
|
replay-single
|
A set of unit tests that verify recovery after MDS failure. (Source HPDD Wiki Auster)
|
runtests
|
Simple basic regression test that verifies data persistence across write, unmount, and remount. This is one of the few tests that verifies data integrity across a full filesystem shutdown and remount, unlike many tests which at most only verify the existence/size of files. (Source HPDD Wiki Auster)
|
sanity-gss
|
Sanity test for gssapi
|
sanity-hsm
|
Sanity test for HSM feature.
|
sanity-krb5
|
Sanity test for krb5 gssapi plugin.
|
sanity-lfsck
|
Sanity test for lfsck
|
sanity-quota
|
A set of tests that verify filesystem quotas. (Source HPDD Wiki Auster)
|
sanity-scrub
|
|
sanity-sec
|
Sanity test for security features, including UID/GID mapping
|
sanity
|
A set of regression tests that verify operation under normal operating conditions. This tests a large number of unusual operations that have previously caused functional or data correctness issues with Lustre. Some of the tests are Lustre specific, and hook into the Lustre fault injection framework using the "lctl set_param fail_loc=X" command to activate triggers in the code to simulate unusual operating conditions that would otherwise be difficult or impossible to simulate. (Source HPDD Wiki Auster)
|
sanityn
|
Tests that verify operations from two clients under normal operating conditions. This is done by mounting the same filesystem twice on a single client, in order to allow a single script/program to execute and verify filesystem operations on multiple "clients" without having to be a distributed program itself.(Source HPDD Wiki Auster)
|