Details
-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
Lustre 2.12.0, Lustre 2.12.1, Lustre 2.14.0, Lustre 2.12.6
-
None
-
3
-
9223372036854775807
Description
replay-singe test_0c fails with ‘mount fails’.
Looking at a recent failure, https://testing.whamcloud.com/test_sets/5532dea2-fd87-11e8-93ea-52540065bddc , we can see in the client test_log that there is a problem unmounting the file system because it is busy and then failover MDS1 (vm9)
CMD: trevis-9vm9 /usr/sbin/lctl mark mds1 REPLAY BARRIER on lustre-MDT0000
umount: /mnt/lustre: target is busy
(In some cases useful info about processes that
use the device is found by lsof(8) or fuser(1).)
Failing mds1 on trevis-9vm9
Then we see that the file system fails to mount because it is already mouted
CMD: trevis-9vm6 mkdir -p /mnt/lustre CMD: trevis-9vm6 mount -t lustre -o user_xattr,flock trevis-9vm9@tcp:/lustre /mnt/lustre mount.lustre: according to /etc/mtab trevis-9vm9@tcp:/lustre is already mounted on /mnt/lustre replay-single test_0c: @@@@@@ FAIL: mount fails
It’s possible that the file system never unmounted.
replay-single test_0d always fails after 0c and in the same way.
Looking over all branches for the past year, this test started to fail on July 31, 2018.
Logs for past failures are at
https://testing.whamcloud.com/test_sets/d02535e4-958e-11e8-8ee3-52540065bddc
https://testing.whamcloud.com/test_sets/ab6bf330-9838-11e8-b0aa-52540065bddc
https://testing.whamcloud.com/test_sets/26d280e4-a35f-11e8-8853-52540065bddc
https://testing.whamcloud.com/test_sets/9438cbfa-dee9-11e8-89f8-52540065bddc
aarch64
https://testing.whamcloud.com/test_sets/6d97765e-ed94-11e8-815b-52540065bddc
ppc64
https://testing.whamcloud.com/test_sets/925cab5a-a783-11e8-80f7-52540065bddc
https://testing.whamcloud.com/test_sets/33d0ef58-fb55-11e8-8a18-52540065bddc
Suse 12
https://testing.whamcloud.com/test_sets/3c98eace-9a8d-11e8-8ee3-52540065bddc