-
Bug
-
Resolution: Duplicate
-
Minor
-
None
-
Lustre 2.12.0
-
None
-
3
-
9223372036854775807
sanity test 244 hangs in recent testing. The last thing seen in the test_log is a hang during test 10 or 11
== sanity test 244: sendfile with group lock tests =================================================== 18:46:27 (1531334787) 35+0 records in 35+0 records out 36700160 bytes (37 MB) copied, 0.482129 s, 76.1 MB/s Starting test test10 at 1531334788
In all cases, the stack_dump is empty and the only thing seen in the console logs and dmesg is the test starting, rebooting and start testing sanity-sec. There’s about a one hour gap between when the test last reports in and when the node is rebooted
[ 5769.663115] Lustre: DEBUG MARKER: /usr/sbin/lctl mark == sanity test 244: sendfile with group lock tests =================================================== 18:46:27 \(1531334787\) [ 5769.858388] Lustre: DEBUG MARKER: == sanity test 244: sendfile with group lock tests =================================================== 18:46:27 (1531334787) <ConMan> Console [trevis-12vm4] disconnected from <trevis-12:6003> at 07-11 19:49. <ConMan> Console [trevis-12vm4] connected to <trevis-12:6003> at 07-11 19:49.
It looks like there is no information on why this test hung.
We have several instances of this with logs at
https://testing.whamcloud.com/test_sets/fca99f92-6fcd-11e8-aa24-52540065bddc
https://testing.whamcloud.com/test_sets/553d0058-80cd-11e8-b441-52540065bddc
https://testing.whamcloud.com/test_sets/f52eaf70-8d67-11e8-87f3-52540065bddc
- duplicates
-
-
- Resolved
-