[LU-13166] sanity test_812b: FAIL: lfs quota should succeed Created: 21/Jan/20  Updated: 14/Feb/20  Resolved: 14/Feb/20

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: None
Fix Version/s: Lustre 2.14.0

Type: Bug Priority: Minor
Reporter: Maloo Assignee: Wang Shilong (Inactive)
Resolution: Fixed Votes: 0
Labels: rhel8
Environment:

RHEL 8.1 client and server


Issue Links:
Related
is related to LU-12637 Support RHEL 8.1 Resolved
Severity: 3
Rank (Obsolete): 9223372036854775807

 Description   

This issue was created by maloo for jianyu <yujian@whamcloud.com>

This issue relates to the following test suite run: https://testing.whamcloud.com/test_sets/2f7e1a68-3c34-11ea-971c-52540065bddc

test_812b failed with the following error:

Unexpected quotactl error: Operation not supported
Disk quotas for usr 0 (uid 0):
     Filesystem  kbytes   quota   limit   grace   files   quota   limit   grace
   /mnt/lustre/     [0]       0       0       -     [0]       0       0       -
Some errors happened when getting quota info. Some devices may be not working or deactivated. The data in "[]" is inaccurate.
 sanity test_812b: @@@@@@ FAIL: lfs quota should succeed

Console log on client node:

LustreError: 14417:0:(osc_quota.c:308:osc_quotactl()) ptlrpc_queue_wait failed, rc: -95
LustreError: 14417:0:(mdc_request.c:2057:mdc_quotactl()) ptlrpc_queue_wait failed, rc: -95
LustreError: 14417:0:(lmv_obd.c:3526:lmv_quotactl()) getquota on mdt 0 failed. -95
Lustre: DEBUG MARKER: /usr/sbin/lctl mark  sanity test_812b: @@@@@@ FAIL: lfs quota should succeed 

VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV
sanity test_812b - lfs quota should succeed



 Comments   
Comment by Peter Jones [ 22/Jan/20 ]

Shilong

Could you please advise?

Thanks

Peter

Comment by Wang Shilong (Inactive) [ 03/Feb/20 ]

The related error messages from server side only:

00000100:00100000:0.0:1579599907.636454:0:18272:0:(service.c:2301:ptlrpc_server_handle_request()) Handling RPC req@00000000f1308370 pname:cluuid+ref:pid:xid:nid:opc:job ll_ost00_009:36678156-a82e-4+6:14417:x1656326625936384:12345-10.9.5.35@tcp:19:lfs.0
00000100:00100000:0.0:1579599907.636517:0:18272:0:(service.c:2350:ptlrpc_server_handle_request()) Handled RPC req@00000000f1308370 pname:cluuid+ref:pid:xid:nid:opc:job ll_ost00_009:36678156-a82e-4+6:14417:x1656326625936384:12345-10.9.5.35@tcp:19:lfs.0 Request processed in 62us (78us total) trans 0 rc -95/-95

It is not clear where -95 is acutally from, might need push some debug patch.

Comment by Gerrit Updater [ 03/Feb/20 ]

Wang Shilong (wshilong@ddn.com) uploaded a new patch: https://review.whamcloud.com/37403
Subject: LU-13166 debug
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 3d54a2a3a7ea9550e0e2d0ba50abc5a0d7e798de

Comment by Gerrit Updater [ 04/Feb/20 ]

Wang Shilong (wshilong@ddn.com) uploaded a new patch: https://review.whamcloud.com/37421
Subject: LU-13166 test: skip sanity 812b if quota is disabled
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 6c94a11e4c58acdf7fedc1ec16bd5b3c82f3c979

Comment by Jian Yu [ 04/Feb/20 ]

The "Unexpected quotactl error: Operation not supported" failure affects sanity-quota testing:
https://testing.whamcloud.com/test_sets/3509d044-41ca-11ea-9847-52540065bddc

Comment by Wang Shilong (Inactive) [ 05/Feb/20 ]

It turned out this is not really related to test scripts, as quota accounting is enabled by default, so we don't need setup quota enforcement to make test pass.

The real reason seems that lustre fail to read quota system inode which makes support of quota fail, i just refresh fix patch, i think patch could be related to sanity-quota test fail as well.

Comment by Gerrit Updater [ 14/Feb/20 ]

Oleg Drokin (green@whamcloud.com) merged in patch https://review.whamcloud.com/37421/
Subject: LU-13166 osd-ldiskfs: fix to allow to get system inode
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: 2c0b2b75404ea2ac8960c8ca45d0c08d858e991d

Comment by Peter Jones [ 14/Feb/20 ]

Landed for 2.14

Generated at Sat Feb 10 02:58:57 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.