https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-7097 Lustre <p>conf-sanity fails on DNE setup.<br/> Simple reproducer:<br/> MDSCOUNT=2 ONLY=84 sh ./conf-sanity.sh</p> LU-7097

conf-sanity test_84 (check recovery_time_hard) fails on DNE setup

Bug Major Resolved Incomplete Hongchao Zhang Sergey Cheremencev Thu, 3 Sep 2015 14:09:11 +0000 Wed, 13 Oct 2021 02:20:18 +0000 Wed, 13 Oct 2021 02:20:18 +0000 0 3 <p>Sergey Cheremencev (sergey_cheremencev@xyratex.com) uploaded a new patch: <a href="http://review.whamcloud.com/16217" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/16217</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-7097" title="conf-sanity test_84 (check recovery_time_hard) fails on DNE setup" class="issue-link" data-issue-key="LU-7097"><del>LU-7097</del></a> tests: add DNE support to conf-sanity_84<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: 836e0145ed22bba1b2107523c74f322f630b9588</p> <p>Sergey - What failure message do you get when this test fails? Could you upload any relevant logs?</p> <p>Test failed due to timeout. There is not DNE support in test.</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>Lustre: DEBUG MARKER: == conf-sanity test 84: check recovery_time_hard == 12:21:27 (1417263687) LustreError: 11-0: lustre-MDT0000-mdc-ffff88005beb5000: Communicating with 192.168.112.5@tcp, operation mds_connect failed with -11. LustreError: 11-0: lustre-MDT0001-mdc-ffff88005beb5000: Communicating with 192.168.112.5@tcp, operation mds_connect failed with -19. LustreError: Skipped 1 previous similar message Lustre: Mounted lustre-client LustreError: 11-0: lustre-MDT0001-mdc-ffff88005aa65400: Communicating with 192.168.112.5@tcp, operation mds_connect failed with -19. LustreError: Skipped 1 previous similar message LustreError: 11-0: lustre-MDT0001-mdc-ffff88005beb5000: Communicating with 192.168.112.5@tcp, operation mds_connect failed with -19. LustreError: Skipped 1 previous similar message LustreError: 11-0: lustre-MDT0001-mdc-ffff88005beb5000: Communicating with 192.168.112.5@tcp, operation mds_connect failed with -19. LustreError: Skipped 1 previous similar message LustreError: 11-0: lustre-MDT0001-mdc-ffff88005beb5000: Communicating with 192.168.112.5@tcp, operation mds_connect failed with -19. LustreError: Skipped 3 previous similar messages LustreError: 11-0: lustre-MDT0001-mdc-ffff88005beb5000: Communicating with 192.168.112.5@tcp, operation mds_connect failed with -19. LustreError: Skipped 7 previous similar messages LustreError: 11-0: lustre-MDT0001-mdc-ffff88005beb5000: Communicating with 192.168.112.5@tcp, operation mds_connect failed with -19. LustreError: Skipped 13 previous similar messages LustreError: 11-0: lustre-MDT0001-mdc-ffff88005beb5000: Communicating with 192.168.112.5@tcp, operation mds_connect failed with -19. LustreError: Skipped 25 previous similar messages LustreError: 11-0: lustre-MDT0001-mdc-ffff88005beb5000: Communicating with 192.168.112.5@tcp, operation mds_connect failed with -19. LustreError: Skipped 51 previous similar messages Lustre: lustre-MDT0000-mdc-ffff88005aa65400: Connection to lustre-MDT0000 (at 192.168.112.5@tcp) was lost; in progress operations using this service will wait for recovery to complete LustreError: 167-0: lustre-MDT0000-mdc-ffff88005aa65400: This client was evicted by lustre-MDT0000; in progress operations using this service will fail. LustreError: 5312:0:(ldlm_resource.c:781:ldlm_resource_complain()) lustre-MDT0000-mdc-ffff88005aa65400: namespace resource [0x240000401:0x1:0x0].0 (ffff88003fd94e40) refcount nonzero (1) after lock cleanup; forcing cleanup. LustreError: 5312:0:(ldlm_resource.c:1421:ldlm_resource_dump()) --- Resource: [0x240000401:0x1:0x0].0 (ffff88003fd94e40) refcount = 2 LustreError: 5312:0:(ldlm_resource.c:1424:ldlm_resource_dump()) Granted locks (in reverse order): LustreError: 5312:0:(ldlm_resource.c:1427:ldlm_resource_dump()) ### ### ns: lustre-MDT0000-mdc-ffff88005aa65400 lock: ffff88005c258b00/0xf5fcc28fef022372 lrc: 3/0,0 mode: PR/PR res: [0x240000401:0x1:0x0].0 bits 0x1b rrc: 2 type: IBT flags: 0x52f400000000 nid: local remote: 0x73481ecc0160356c expref: -99 pid: 4521 timeout: 0 lvb_type: 0 Lustre: lustre-MDT0000-mdc-ffff88005aa65400: Connection restored to lustre-MDT0000 (at 192.168.112.5@tcp)</pre> </div></div> <p>It seems issue is already fixed by "<a href="https://jira.whamcloud.com/browse/LU-7222" title="conf-sanity test_84: invalid llog tail at log id 0x4:10/0 offset 16384" class="issue-link" data-issue-key="LU-7222"><del>LU-7222</del></a> tests: add Mulitple MDTs to test_84".<br/> But on the other hand my patch introduces mdsfailover_HOST support for test_84.<br/> Also it starts all possible clients and waits that just one of them will be evicted.</p> <p>Can reopen ticket if new patch is submitted.</p> Related LU-7222 LU-7428 Development Rank 1|hzxmdr: Rank (Obsolete) 9223372036854775807 Severity