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-1625 Lustre <p>This issue was created by maloo for sarah &lt;sarah@whamcloud.com&gt;</p> <p>This issue relates to the following test suite run: <a href="https://maloo.whamcloud.com/test_sets/4a115426-cba8-11e1-8847-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/4a115426-cba8-11e1-8847-52540035b04c</a>.</p> <p>The sub-test test_metabench failed with the following error:</p> <blockquote> <p>test failed to respond and timed out</p></blockquote> <p>From the log, this test took more than 35 minutes before it was ended. I check several pass runs, it usual takes less than 1800s, so the test may just be killed by the system. </p> LU-1625

Test failure on test suite parallel-scale-nfsv4, subtest test_metabench

Bug Blocker Resolved Fixed Keith Mannthey Maloo Thu, 12 Jul 2012 03:22:49 +0000 Fri, 22 Feb 2013 11:19:51 +0000 Sun, 19 Aug 2012 16:02:00 +0000 Lustre 2.3.0 Lustre 2.1.3 Lustre 1.8.8 Lustre 2.3.0 Lustre 2.1.3 Lustre 1.8.9 0 8 <p>Yangsheng</p> <p>Could you please look into this one?</p> <p>Thanks</p> <p>Peter</p> <p>Looks like this just test timeout. There about 1 hours between compilebeach &amp; metabeach.</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>Lustre: DEBUG MARKER: == parallel-scale-nfsv4 test compilebench: compilebench == 12:49:59 (1342036199) Lustre: DEBUG MARKER: == parallel-scale-nfsv4 test metabench: metabench == 13:53:31 (1342040011) </pre> </div></div> <p>Is the SLOW=yes has seted?</p> <p>I think yes, the full test suite run by Autotest should set SLOW=yes as usual. </p> <p>So looks compilebeach works normal. Just metabench was killed by timeout. But got less info from the logs. I'll trying to search other failed instance to investigate.</p> <p>I suspect this issue relate to some nfs problem. from stacktrace, the nfsv4-svc thread always running same location. I'll do more check for that.</p> <p>Bobijam will help with this one</p> <p>Sarah,</p> <p>what the timeout rule for autotest? as in <a href="https://maloo.whamcloud.com/test_sessions/3b113b66-e157-11e1-b541-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sessions/3b113b66-e157-11e1-b541-52540035b04c</a>, I saw parallel-scale-nfsv3 can run 9499 seconds, while parallel-scale-nfsv4 timed out in 3600 seconds.</p> <p>Bobi, I think for each test, timeout is set to 3600s, 9499s was the total number for 5 tests</p> <p>Minh, could you please just change the default compilebench numbers to "2" and "2" for parallel-scale-nfs.sh. This is a trivial change, and reduces the testing time, rather than making it take longer, and I don't think the benefits of testing NFS for such a long time is matched by the number of users who use NFS.</p> <p>I think this is simply the following:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>test_compilebench() { export cbench_IDIRS=${cbench_IDIRS:-2} export cbench_RUNS=${cbench_RUNS:-2} run_compilebench } run_test compilebench "compilebench" </pre> </div></div> <p>If there are other sub-parts of parallel-scale-nfsv4 that are taking a long time, I think they can also be shortened in a similar manner.</p> <p>patch to reduce parallel-scale for nfs<br/> <a href="http://review.whamcloud.com/#change,3596" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/#change,3596</a></p> <p>RHEL6.3/x86_64 (2.1.3 Server + 1.8.8-wc1 Client):<br/> <a href="https://maloo.whamcloud.com/test_sets/7422aff4-e42a-11e1-b6d3-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/7422aff4-e42a-11e1-b6d3-52540035b04c</a></p> <p>Patch landed for 2.1.3 and 2.3. If there are still issues with this with Minh's changes in place then please reopen</p> <p>One extra change is need. I missed part of the needed patch. <a href="http://review.whamcloud.com/3701" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/3701</a> has been pushed to fix this issue. </p> <p>Extra tweak landed too</p> <p>Patch for b1_8 is at <a href="http://review.whamcloud.com/4949" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/4949</a></p> Development Rank 1|hzv5vz: Rank (Obsolete) 4488 Severity