Details
-
Bug
-
Resolution: Fixed
-
Minor
-
Lustre 2.13.0, Lustre 2.14.0, Lustre 2.12.4
-
None
-
9223372036854775807
Description
sanity-quota test_3 fails with 'write success, but expect EDQUOT', but looking at the client test_log we see
Total allocated inode limit: 0, total allocated block limit: 0 pid 1000 is using default file quota setting Files for project (1000): lfs: failed for '/mnt/lustre': Too many levels of symbolic links sanity-quota test_3: @@@@@@ FAIL: write success, but expect EDQUOT Trace dump: = /usr/lib64/lustre/tests/test-framework.sh:6115:error() = /usr/lib64/lustre/tests/sanity-quota.sh:152:quota_error() = /usr/lib64/lustre/tests/sanity-quota.sh:771:test_block_soft() = /usr/lib64/lustre/tests/sanity-quota.sh:827:test_3()
There is no additional errors or indication of a problem in any of the console logs.
We’ve only seen sanity-quota test 3 fail with this error and with the lfs error:
https://testing.whamcloud.com/test_sets/7a25bb86-d6ed-11e9-a2b6-52540065bddc
We've seen sanity-quota test 3 fail with the same "write success, but expect EDQUOT " error, but the test_log does not have the lfs error. The logs have a different failure:
Total allocated inode limit: 0, total allocated block limit: 0 Some errors happened when getting quota info. Some devices may be not working or deactivated. The data in "[]" is inaccurate. Files for project (1000): sanity-quota test_3: @@@@@@ FAIL: write success, but expect EDQUOT Trace dump: = /usr/lib64/lustre/tests/test-framework.sh:6114:error() = /usr/lib64/lustre/tests/sanity-quota.sh:152:quota_error() = /usr/lib64/lustre/tests/sanity-quota.sh:734:test_block_soft() = /usr/lib64/lustre/tests/sanity-quota.sh:784:test_3()
Logs for these errors are at
https://testing.whamcloud.com/test_sets/43331474-b5b5-11e9-a1bd-52540065bddc
https://testing.whamcloud.com/test_sets/5f2b2d6c-bffe-11e9-98c8-52540065bddc