Details
Description
All Lustre test suites that run as part of the review-* test groups should complete and pass when run under a mounted subdirectory. To run all Lustre tests with a subdirectory mounted, you can use “Test-Parameters: envdefinitions=FILESET=/subdir”.
From the following test results, we can see that not all Lustre test suites can be run successfully with Lustre mounted from a subdirectory:
https://testing.hpdd.intel.com/test_sessions/0e2c6222-5f8b-11e6-b5b1-5254006e85c2
https://testing.hpdd.intel.com/test_sessions/f30cb438-5f9e-11e6-906c-5254006e85c2
https://testing.hpdd.intel.com/test_sessions/2f30c6d8-5faf-11e6-b5b1-5254006e85c2
https://testing.hpdd.intel.com/test_sessions/9f47f55a-5ff4-11e6-b5b1-5254006e85c2
Andreas Dilger reviewed the results and stated “ … the sanity-lfsck and sanity-scrub tests should be skipped if .lustre does not exist on the mountpoint.” Thus, we need to review the failures of the above test session and submit a patch to skip certain tests/test suites when a subdirectory is used as the mount point.
Attachments
Issue Links
- is duplicated by
-
LU-10457 open_by_handle_at() in write mode triggers ETXTBSY
- Resolved
- is related to
-
LU-11686 sanity test 807 fails with mounted subdirectory with error '/mnt/lustre/d807.sanity/single_dd expected blocks: 1, got: 0'
- Open
-
LU-12633 sanity test_185a: FAIL: can't get FID for volatile
- Open
-
LU-12661 sanity test_817: FAIL: failed to execute 'true' command
- Open
-
LU-12203 sanity-lfsck test_36[b,c] defect: tests are to be skipped for FILESET
- Resolved
-
LU-16463 llapi_open_by_fid open should not be cached systematically
- Resolved
-
LU-16494 Check fileset for operations by fid
- Resolved
-
LU-10948 client cache open lock after N opens
- Open
-
LU-12806 llapi: have llapi_fd2fid rely on name_to_handle_at() rather than ioctl()
- Resolved
- is related to
-
LU-11501 use the dcache properly with .lustre/fid
- In Progress
-
LU-15835 sanityn test_102: [20108.951589] WARNING: CPU: 1 PID: 722753 at fs/exportfs/expfs.c:96 reconnect_path+0x22b/0x2c0
- Reopened
- mentioned in
-
Page Loading...