Details
-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
Lustre 2.14.0
-
3
-
9223372036854775807
Description
This issue was created by maloo for Andreas Dilger <adilger@whamcloud.com>
This issue relates to the following test suite run: https://testing.whamcloud.com/test_sets/4a0c244b-cc64-455a-9d41-a8cf9790407c
test_280 failed with the following error:
== sanity test 280: Race between MGS umount and client llog processing ===== 10.9.6.22@tcp:/lustre /mnt/lustre lustre rw,seclabel,flock,user_xattr,lazystatfs,noencrypt 0 0 CMD: trevis-45vm1.trevis.whamcloud.com grep -c /mnt/lustre' ' /proc/mounts Stopping client trevis-45vm1.trevis.whamcloud.com /mnt/lustre (opts:) CMD: trevis-45vm1.trevis.whamcloud.com lsof -t /mnt/lustre CMD: trevis-45vm1.trevis.whamcloud.com umount /mnt/lustre 2>&1 CMD: trevis-25vm1.trevis.whamcloud.com mount -t lustre -o user_xattr,flock,skpath=/tmp/test-framework-keys trevis-25vm4@tcp:/lustre /mnt/lustre : Starting client: trevis-25vm1.trevis.whamcloud.com: -o user_xattr,flock,skpath=/tmp/test-framework-keys trevis-25vm4@tcp:/lustre /mnt/lustre CMD: trevis-25vm1.trevis.whamcloud.com mkdir -p /mnt/lustre CMD: trevis-25vm1.trevis.whamcloud.com mount -t lustre -o user_xattr,flock,skpath=/tmp/test-framework-keys trevis-25vm4@tcp:/lustre /mnt/lustre mount.lustre: according to /etc/mtab trevis-25vm4@tcp:/lustre is already mounted on /mnt/lustre sanity test_280: @@@@@@ FAIL: mount client failed
It looks like this is failing intermittently since 2020-07-30 (about 35 times over 4 months) for review-dne-ssk and review-dne-selinux-ssk sessions. Note that it does not happen for review-dne-selinux sessions, and the few failures on other test sessions look like they were related to many previous tests failing also.
It may just be a test script issue (e.g. SSK is causing the client mount to be slower, and the race that the subtest is trying to trigger is happening differently as a result).
VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV
sanity test_280 - mount client failed