Testing

From Lustre Wiki
Revision as of 14:45, 28 April 2015 by Justinmiller (talk | contribs)
Jump to navigation Jump to search
Lustre Test Suites
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)
fsx The file system exerciser was developed outside of Lustre and is intended to stress test unusual IO and file operations. It does buffered and mmap reads and writes with random size and offset, truncate, open, close on a file. It verifies data integrity after each step. A lustre-developed extension allows fsx to run against multiple mountpoints to verify distributed IO operation correctness. (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)
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 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)
sanity-quota A set of tests that verify filesystem quotas. (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)