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-480 Lustre <p>This issue was created by maloo for yujian &lt;yujian@whamcloud.com&gt;</p> <p>This issue relates to the following test suite run: <a href="https://maloo.whamcloud.com/test_sets/8771913e-a451-11e0-b786-52540025f9af" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/8771913e-a451-11e0-b786-52540025f9af</a>.</p> <p>The sub-test test_36 failed with the following error:</p> <blockquote> <p>LBUG/LASSERT detected</p></blockquote> LU-480

Test failure on test suite sanityn: LBUG/LASSERT detected

Bug Blocker Resolved Fixed Zhenyu Xu Maloo Mon, 4 Jul 2011 04:18:20 +0000 Thu, 7 Jul 2011 10:46:04 +0000 Thu, 7 Jul 2011 10:46:04 +0000 Lustre 2.1.0 Lustre 2.1.0 0 4 <p>The issue occurred on many sanityn sub-tests:<br/> <a href="https://maloo.whamcloud.com/test_sets/419609a4-a4fd-11e0-b786-52540025f9af" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/419609a4-a4fd-11e0-b786-52540025f9af</a><br/> <a href="https://maloo.whamcloud.com/test_sets/bda31ee8-a204-11e0-aee5-52540025f9af" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/bda31ee8-a204-11e0-aee5-52540025f9af</a><br/> <a href="https://maloo.whamcloud.com/test_sets/3791c1d0-a1df-11e0-aee5-52540025f9af" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/3791c1d0-a1df-11e0-aee5-52540025f9af</a></p> <p>Chris,</p> <p>What is the pdsh full command being used in the autotest?</p> <p>You'll have to give me a bit more info to enable me to understand that <br/> question. Which pdsh command when? If you asking about the pdsh command <br/> used for test 41g then that will be the whatever the standard scripts <br/> create. The test environment will not change or customize it?</p> <p>What other output could help you?</p> <p>those error was due to pdsh command times out, and pdsh IMO is set when we call auster.sh.</p> <p>Yu Jian points out that there is a autotest_config.sh or similar script which she saw in</p> <p>Provisioning-1.Provision_1.autotest.client-21vm1.log:<br/> pdsh -w client-21vm1,client-21vm2 scp client-21vm1:/root/autotest_config.sh /usr/lib64/lustre/tests/cfg/ </p> <p>I suggest we add "-t 120" option for pdsh, like "pdsh -w -t 120 xxxxxxxxxxxxxxxx" in it. pdsh default use 10 seconds as timeout, -t 120 can extend it to 120 seconds.</p> <p>Per this provisioning log: <a href="https://maloo.whamcloud.com/test_logs/bcb00110-a450-11e0-b786-52540025f9af/show_text" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_logs/bcb00110-a450-11e0-b786-52540025f9af/show_text</a></p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>12:00:25:(/home/autotest/lab/tools/run_test.sh:55): 12:00:25:cat /home/autotest/lab/tools/mecturk.sh 12:00:25:((/home/autotest/lab/tools/run_test.sh:57): 12:00:25:hostname -s 12:00:25:(/home/autotest/lab/tools/run_test.sh:57): 12:00:25:CPYLINE='scp client-21vm1:/root/autotest_config.sh /usr/lib64/lustre/tests/cfg/' 12:00:27:(/home/autotest/lab/tools/run_test.sh:58): 12:00:27:pdsh -w client-21vm1,client-21vm2 scp client-21vm1:/root/autotest_config.sh /usr/lib64/lustre/tests/cfg/ </pre> </div></div> <p>The PDSH variable was set in /home/autotest/lab/tools/mecturk.sh:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>$ grep PDSH /home/autotest/lab/tools/mecturk.sh PDSH="pdsh -S -Rrsh -w" </pre> </div></div> <p>Chris, could you please change it to "pdsh -t 120 -S -Rrsh -w" to see whether the upcoming autotest results hit those timeout issues or not?</p> <p>OK, I've change the pdsh in mecturk, let's see if it stops failing.</p> <p>Closing for now. Reopen if this reoccurs with the change in place</p> Development Rank 1|hzvi5j: Rank (Obsolete) 6590 Severity