Details
Description
This test failed in both 2.3.0 client and 2.1.3 client.
It failed because the test suite try to execute lfsck at the client, which does not have e2fsprogs rpm installed and caused "command not found" error: (see dmsg log of service331)
lfsck -c -l --mdsdb /var/acc-sm-shared/mdsdb --ostdb /var/acc-sm-shared/ostdb-0 /var/acc-sm-shared/ostdb-1 /mnt/nbp0-1
/usr/lib64/lustre/tests/test-framework.sh: line 3246: lfsck: command not found
lfsck : @@@@@@ FAIL: lfsck -c -l --mdsdb /var/acc-sm-shared/mdsdb --ostdb /var/acc-sm-shared/ostdb-0 /var/acc-sm-shared/ostdb-1 /mnt/nbp0-1 returned 127, should be <= 1
The return code '127' is when command not found.
If I allow the return code to be either <= 1 or equals to 127, the test suite would complete. I do not understand why the test suite that tries to execute lfsck on client. If e2fsprogs rpm is not required on clients, the test is flawed.
Test_logs tarball is attached.
Attachments
Activity
Fix Version/s | New: Lustre 2.4.0 [ 10154 ] | |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Progress [ 3 ] | New: Resolved [ 5 ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Assignee | Original: WC Triage [ wc-triage ] | New: Emoly Liu [ emoly.liu ] |
Landed for 2.4