[LU-2571] test: lfsck FAIL: lfsck returned 127, should be <= 1 Created: 03/Jan/13  Updated: 19/Mar/13  Resolved: 19/Mar/13

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: Lustre 2.3.0, Lustre 2.1.3
Fix Version/s: Lustre 2.4.0

Type: Bug Priority: Minor
Reporter: Jay Lan (Inactive) Assignee: Emoly Liu
Resolution: Fixed Votes: 0
Labels: None
Environment:

Server: 2.1.3-1nasS, centos 6.3, 2.6.32_279.2.1.el6
Client: 2.3.0-2nasC, sles11sp2, 3.0.42_0.7.3
1 mds (S337), 2 oss (S361, S362), 2 clients (S331, S332)


Attachments: File lfsck-not-found.tgz    
Severity: 3
Rank (Obsolete): 6004

 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.



 Comments   
Comment by Peter Jones [ 03/Jan/13 ]

Emoly

Could you please look into this issue?

Thanks

Peter

Comment by Emoly Liu [ 03/Jan/13 ]

OK, I will have a look.

Comment by Emoly Liu [ 16/Jan/13 ]

Usually we install e2fsprogs rpm on all the nodes by default and run lfsck on client. But, I agree that it's not necessary to have e2fsprogs rpm on clients.

I have some ideas to fix this check:
1. only install lfsck on client, instead of the whole e2fsprogs rpm, and
2. let me check if we can run lfsck on server and then modify the test script.

Andreas, do you have any advice?

Comment by Andreas Dilger [ 17/Jan/13 ]

If the fikesystem is mounted on the MDS this would allow LFSCK lfsck to be run there.

Comment by Emoly Liu [ 21/Jan/13 ]

Patch at http://review.whamcloud.com/#change,5139

Comment by Jay Lan (Inactive) [ 15/Mar/13 ]

If you guys feel no need to address this issue, I am OK you close this bug. I have changed my setup to always include /usr/sbin/lfsck in my environment.

Comment by Emoly Liu [ 16/Mar/13 ]

Jay, the patch is ready for landing. Oleg, will we land it soon?

Comment by Peter Jones [ 19/Mar/13 ]

Landed for 2.4

Generated at Sat Feb 10 01:26:19 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.