Details
-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
None
-
None
-
3
-
9223372036854775807
Description
This issue was created by maloo for S Buisson <sbuisson@ddn.com>
This issue relates to the following test suite run: https://testing.whamcloud.com/test_sets/6b33e480-4783-4197-bc3b-906329a4543e
test_801b failed with the following error:
Timeout occurred after 243 mins, last suite running was sanity
Test end with the messages:
total: 6 mkdir in 0.01 seconds: 485.48 ops/second CMD: trevis-68vm8 /usr/sbin/lctl barrier_freeze lustre 180 CMD: trevis-68vm8 /usr/sbin/lctl barrier_stat -s lustre File: /mnt/lustre/d801b.sanity/d5 Size: 4096 Blocks: 8 IO Block: 4096 directory Device: 2c54f966h/743766374d Inode: 144115708588992185 Links: 2 Access: (0755/drwxr-xr-x) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2021-07-07 16:44:28.000000000 +0000 Modify: 2021-07-07 16:44:28.000000000 +0000 Change: 2021-07-07 16:44:28.000000000 +0000 Birth: - CMD: trevis-68vm8 /usr/sbin/lctl barrier_stat -s lustre
No visible reason for the timeout. MDS server becomes unreachable, but not error message on that side.
VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV
sanity test_801b - Timeout occurred after 243 mins, last suite running was sanity