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-6291 Lustre <p>This issue was created by maloo for wangdi &lt;di.wang@intel.com&gt;</p> <p>This issue relates to the following test suite run: <a href="https://testing.hpdd.intel.com/test_sets/79052dac-bd31-11e4-8d85-5254006e85c2" class="external-link" target="_blank" rel="nofollow noopener">https://testing.hpdd.intel.com/test_sets/79052dac-bd31-11e4-8d85-5254006e85c2</a>.</p> <p>The sub-test test_41a failed with the following error:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>test failed to respond and timed out </pre> </div></div> <p>Please provide additional information about the failure here.</p> <p>Info required for matching: conf-sanity 41a</p> LU-6291

conf-sanity test_41a: failed to respond and timed out

Bug Minor Resolved Fixed Niu Yawei Maloo dne2 Thu, 26 Feb 2015 00:09:42 +0000 Fri, 9 Sep 2016 20:18:02 +0000 Tue, 31 Mar 2015 04:20:24 +0000 Lustre 2.8.0 Lustre 2.8.0 0 3 <p>That's a test script problem, in the DNE environment, this test (conf-sanity 41a) starts only the master MDT, so client mount will always fail for -EAGAIN. See tgt_handle_connect() -&gt; mdt_obd_connect() -&gt; lod_obd_get_info().</p> <p>I think we'd change the test script to replace the "start $SINGLEMDS" to "start_mds". Some other tests have the same problem, 41b for instance.</p> <p>The -EAGAIN error is introduced by: </p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java">commit daa691c4dcbc5a70acf4cf161c581b45c104c87a Author: Wang Di &lt;di.wang@intel.com&gt; Date: Mon Aug 11 13:46:38 2014 -0700 LU-3536 lod: write updates to update log For cross-MDT operation, LOD will write updates into the update log on all of MDTs. 1. In transaction start, LOD perpare the update records buffer <span class="code-keyword">for</span> cross-MDT operation. 2. Sub LOD collects all updates in execution phase. 3. In transaction stop, LOD will write thse updates as llog record on all of MDTs. Change-Id: Ibba79267393db00ba05e0aa2df9865f88149eaa4 Signed-off-by: Wang Di &lt;di.wang@intel.com&gt; </pre> </div></div> <p>Which means client won't be able to mount until all MDTs started, I'm not sure if it's by design or a defect. If it's a defect, we'd fix it rather than fix the test script.</p> <p>Yes, that is the rule, if the failover MDT can not connect to all of other MDTs, it has to wait until the administrator abort the recovery. I will fix the test script for now.</p> Related LU-3534 Development Rank 1|hzx74f: Rank (Obsolete) 17624 Severity