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-9406 Lustre <p>conf-sanity test_82b fails when Lustre is configured with the MGS and MDS on separate nodes with </p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>conf-sanity test_82b: @@@@@@ FAIL: /usr/sbin/lctl pool_add scratch.test_82b scratch-OST[32b4,06a8,7070] failed </pre> </div></div> <p>From the console log, it looks like the OST pools are never created</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>eagle-48vm1: Warning, pool scratch.test_82b not found eagle-48vm1: Pool scratch.test_82b not found eagle-48vm1: Pool scratch.test_82b not found eagle-48vm1: Pool scratch.test_82b not found eagle-48vm1: pool_add: No such file or directory pdsh@eagle-48vm6: eagle-48vm1: ssh exited with exit code 2 conf-sanity test_82b: @@@@@@ FAIL: /usr/sbin/lctl pool_add scratch.test_82b scratch-OST[32b4,06a8,7070] failed </pre> </div></div> <p>test 82b checks that you can create OST pools with the –ost-list option. For OST pools to work with the MDS and the MGS on separate nodes, there must be a client running on the MGS. The problem is that all clients and servers are stopped at the beginning of the test and then only a single client is started. That single client may or may not be the client on the MGS. </p> <p>From conf-sanity test 82b:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java">5846 # Setup Lustre filesystem. 5847 start_mgsmds || error <span class="code-quote">"start_mgsmds failed"</span> 5848 <span class="code-keyword">for</span> i in $(seq $OSTCOUNT); <span class="code-keyword">do</span> 5849 start ost$i $(ostdevname $i) $OST_MOUNT_OPTS || 5850 error <span class="code-quote">"start ost$i failed"</span> 5851 done 5852 5853 mount_client $MOUNT || error <span class="code-quote">"mount client $MOUNT failed"</span> </pre> </div></div> <p>One solution to this problem is to restart all clients in this test. </p> A Lustre configuration with the MDS and the MGS on separate nodes LU-9406

conf-sanity test 82b fails with ‘FAIL: /usr/sbin/lctl pool_add scratch.test_82b scratch-OST[*] failed’

Bug Minor Resolved Fixed James Nunez James Nunez test Wed, 26 Apr 2017 17:41:37 +0000 Mon, 17 Jun 2019 15:42:11 +0000 Mon, 17 Jun 2019 15:42:11 +0000 Lustre 2.10.0 Lustre 2.11.0 0 2 <p>James Nunez (james.a.nunez@intel.com) uploaded a new patch: <a href="https://review.whamcloud.com/26844" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/26844</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-9406" title="conf-sanity test 82b fails with ‘FAIL: /usr/sbin/lctl pool_add scratch.test_82b scratch-OST[*] failed’" class="issue-link" data-issue-key="LU-9406"><del>LU-9406</del></a> test: conf-sanity 82b start all clients<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: a353f402a69e9953c32bda118da43cbdd835c8d6</p> <p>conf-sanity test 82 is fixed in patch <a href="https://review.whamcloud.com/#/c/28806" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/#/c/28806</a></p> <p>Patch <a href="https://review.whamcloud.com/26844" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/26844</a> was abandoned.</p> <p>conf-sanity test 82b was fixed by restarting all clients when testing with a separate MGS.</p> Related LU-8688 Development Rank 1|hzzban: Rank (Obsolete) 9223372036854775807 Severity