|
FLSCK 1.5 test plan (ldiskfs only)
****************
1. Correctness
----------------
1.1) sanity-lfsck on Maloo with commit message "Test-Parameters: envdefinitions=ENABLE_QUOTA=yes testlist=sanity-lfsck". All test cases should pass.
1.2) sanity-scrub on Maloo with commit message "Test-Parameters: envdefinitions=ENABLE_QUOTA=yes testlist=sanity-scrub". All test cases should pass.
1.3) normal acc-sm tests on Maloo. All test cases should pass except for some known master failures.
2. Performance
----------------
The file set to be tested should be generated with the following conditions:
A) Create single test root directroy.
B) Create N sub-directories under the test root directory.
C) Under each sub-directory, create 100K objects, include 1K multiple-linked objects, and 1K symlink objects, and 8K empty directories, the others are normal files.
2.1) lfsck against healthy 2.x MDT device for consistency routine check.
2.1.1) Create above test file set with Lustre-2.4.
2.1.2) Test the highest lfsck speeds (full speed, without other work load) under different file sets: N = 100, 200, 400, 800, 1600
2.2) lfsck against 2.x MDT device which is restored from file-level backup.
2.2.1) Create above test file set with Lustre-2.4.
2.2.2) Perform MDT file-level backup/restore.
2.2.3) Test the highest lfsck speeds (full speed, without other work load) under different file sets: N = 10, 20, 40, 80, 160
2.3) lfsck agaist the MDT device which is upgraded from 1.8.
2.3.1) Create above test file set with Lustre-1.8
2.3.2) Update the system to 2.4. Use "tunefs --dirdata" to enable FID-in-dirent on MDT.
2.3.3) Test the highest lfsck speeds (full speed, without other work load) under different file sets: N = 100, 200, 400, 800, 1600
3. Create performance impact by lfsck
----------------
Measure how much the routine lfsck will affect normal create performance. Generate test file set as described in section 2 with N = 400.
3.1) Run lfsck with full speed on the file set. At the same time, use C threads to create 10M files (mds-survey) in parallel. Each thread creates under its private directory, and create 10M / C files.
3.2) Measure the create performance with different lfsck speed limit. According to the 3.1) result, we can know the highest speed for lfsck with create work load, assume it is S. Then repeate the test with lfsck speed limit = (1/4)S, (1/2)S, (3/4)S.
4. Scale test
----------------
Run mdtest on Hyperion, the routine lfsck should run background repeatedly. We can inject some known failure stubs by set fail_loc on MDS, such as OBD_FAIL_FID_INDIR, OBD_FAIL_FID_INLMA, OBD_FAIL_LFSCK_LINKEA_MORE, OBD_FAIL_LFSCK_LINKEA_LESS, and so on, then the lfsck can repair something during the check. There should be no failures reported.
5. DNE support
----------------
LFSCK correctness verification under DNE mode, depends on LU-2646.
5.1) Setup the DNE environment with 2 MDSes.
5.2) Generate file set, include remote objects.
5.3) Run lfsck on each MDS in parallel to check whether there are failures.
6. Resource requirement.
----------------
6.1) Test 1 can be done locally and on Maloo.
6.2) Test 2 and 3 can be done on Toro with 1 fat node.
6.3) Test 4 needs to be tested on Hyperion. It is better if some guys can help to do that.
6.4) Test 5 can be done on Toro with 4 nodes.
| 
LFSCK15_Demonstration_Milestone_Completion_r2.pdf
sanity-lfsck_20121229.log