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-2458 Lustre <p>This issue was created by maloo for Andreas Dilger &lt;adilger@whamcloud.com&gt;</p> <p>This issue relates to the following test suite run: <a href="https://maloo.whamcloud.com/test_sets/d34560e2-42a0-11e2-8dba-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/d34560e2-42a0-11e2-8dba-52540035b04c</a>.</p> <p>The sanity.sh test_77i, conf-sanity.sh test_6, recovery-small.sh test_62 failed with the following error in the console logs:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>class_newdev()) Device MGC10.10.4.160@tcp already exists, won't add class_attach()) Cannot create device MGC10.10.4.160@tcp of type mgc : -17 lustre_start_simple()) MGC10.10.4.160@tcp attach error -17 lustre_fill_super()) Unable to mount (-17) DEBUG MARKER: conf-sanity test_6: @@@@@@ FAIL: test_6 failed with 87 </pre> </div></div> <p>Info required for matching: mount failed</p> LU-2458

Device MGC already exists, won't add

Bug Blocker Resolved Fixed Bob Glossman Maloo Mon, 10 Dec 2012 15:42:18 +0000 Wed, 19 Jun 2013 07:42:46 +0000 Wed, 19 Jun 2013 07:42:46 +0000 Lustre 2.1.4 Lustre 2.1.6 Lustre 2.1.6 0 10 <p>This looks like it may have started due to "jitter" introduction on the test nodes. Testing for recovery-small.sh had 5/8 failures since 12/10 05:30, but none before 12/08 06:26 (the previous b2_1 test run).</p> <p><a href="http://review.whamcloud.com/4482" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/4482</a> was the base for both passing and failing tests, but had been landed on 12/06 so it is questionable whether it was a code change that caused the problem.</p> <p>This is preventing the patches on b2_1 from passing review test group:<br/> <a href="http://review.whamcloud.com/#change,4783" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/#change,4783</a><br/> <a href="http://review.whamcloud.com/#change,4784" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/#change,4784</a><br/> <a href="http://review.whamcloud.com/#change,4782" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/#change,4782</a></p> <p>and so on.</p> <p>This also affected the test results of b2_1 build #148 on 2.1.3&lt;-&gt;2.1.4 interop combinations.</p> <p>similar problem seen a few days earlier, also on a b2_1 test run:<br/> <a href="https://maloo.whamcloud.com/test_sets/8b24f332-40d3-11e2-a16b-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/8b24f332-40d3-11e2-a16b-52540035b04c</a></p> <p>Bob</p> <p>Could you please look into this one?</p> <p>Thanks</p> <p>Peter</p> <p>It now appears that these failures are side effects of the increased number of virtual cpus in our test VMs done for TT-928/TT-968. With that change backed out of our test environment repeating the test run for <a href="http://review.whamcloud.com/#change,4516" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/#change,4516</a> (build 11037) now passes where it failed before.</p> <p>Begs the question of if our testing is really appropriate. With more and more mulitcore servers and clients in the real world, maybe our test framework should work correctly on multicore test nodes.</p> <p>Lustre Tag: v2_1_4_RC1<br/> Lustre Build: <a href="http://build.whamcloud.com/job/lustre-b2_1/159/" class="external-link" target="_blank" rel="nofollow noopener">http://build.whamcloud.com/job/lustre-b2_1/159/</a><br/> Distro/Arch: RHEL5.8/x86_64 + RHEL5.8/i686 (Server + Client)</p> <p>While running replay-dual tests, the same issue occurred:<br/> <a href="https://maloo.whamcloud.com/test_sets/df2f801c-4ad0-11e2-b87e-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/df2f801c-4ad0-11e2-b87e-52540035b04c</a></p> <p>Lustre Branch: b2_1<br/> Lustre Build: <a href="http://build.whamcloud.com/job/lustre-reviews/13578/" class="external-link" target="_blank" rel="nofollow noopener">http://build.whamcloud.com/job/lustre-reviews/13578/</a><br/> Distro/Arch: RHEL5.9/x86_64</p> <p>sanity test_77i, conf-sanity, recovery-small test_62 failed with this issue again:<br/> <a href="https://maloo.whamcloud.com/test_sets/d511b2f0-834f-11e2-98f5-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/d511b2f0-834f-11e2-98f5-52540035b04c</a><br/> <a href="https://maloo.whamcloud.com/test_sets/243a6366-8352-11e2-98f5-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/243a6366-8352-11e2-98f5-52540035b04c</a><br/> <a href="https://maloo.whamcloud.com/test_sets/681304c4-8354-11e2-98f5-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/681304c4-8354-11e2-98f5-52540035b04c</a></p> <p>Hi Chris,</p> <p>Did you turn on "jitter" on the test nodes again?</p> <p>Lustre Client: v2_1_5_RC1<br/> Lustre Server: 2.1.4</p> <p>conf-sanity, recovery-small and replay-dual failed with this issue again:<br/> <a href="https://maloo.whamcloud.com/test_sets/0f16b3ba-9327-11e2-b06e-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/0f16b3ba-9327-11e2-b06e-52540035b04c</a><br/> <a href="https://maloo.whamcloud.com/test_sets/17874dc8-9329-11e2-b06e-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/17874dc8-9329-11e2-b06e-52540035b04c</a><br/> <a href="https://maloo.whamcloud.com/test_sets/7ff9bc14-932a-11e2-b06e-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/7ff9bc14-932a-11e2-b06e-52540035b04c</a></p> <p>Lustre Tag: v2_1_6_RC1<br/> Lustre Build: <a href="http://build.whamcloud.com/job/lustre-b2_1/208" class="external-link" target="_blank" rel="nofollow noopener">http://build.whamcloud.com/job/lustre-b2_1/208</a><br/> Distro/Arch: RHEL5.9/x86_64</p> <p>sanity, conf-sanity, recovery-small tests failed with this issue again:<br/> <a href="https://maloo.whamcloud.com/test_sessions/8e59afbc-cd68-11e2-a1e0-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sessions/8e59afbc-cd68-11e2-a1e0-52540035b04c</a></p> <p>Lustre Tag: v2_1_6_RC1<br/> Lustre Build: <a href="http://build.whamcloud.com/job/lustre-b2_1/208" class="external-link" target="_blank" rel="nofollow noopener">http://build.whamcloud.com/job/lustre-b2_1/208</a><br/> Distro/Arch: RHEL5.9/i686 (client), RHEL5.9/x86_64 (server)</p> <p>sanity, conf-sanity, recovery-small, replay-dual tests failed with this issue again:<br/> <a href="https://maloo.whamcloud.com/test_sessions/dad32c08-cda7-11e2-ba28-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sessions/dad32c08-cda7-11e2-ba28-52540035b04c</a></p> <p>in b2_1, sanity, conf-sanity, recovery-small:<br/> <a href="https://maloo.whamcloud.com/test_sessions/e3e05362-d43b-11e2-9e73-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sessions/e3e05362-d43b-11e2-9e73-52540035b04c</a></p> <p>more b2_1:<br/> <a href="https://maloo.whamcloud.com/test_sessions/fb0ca642-d479-11e2-9e73-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sessions/fb0ca642-d479-11e2-9e73-52540035b04c</a></p> <p>Bob, according to the Lustre log taken during failure, this problem could the b2_1 duplicate of <a href="https://jira.whamcloud.com/browse/LU-639" title="replay-dual test_0b: @@@@@@ FAIL: mount1 fails" class="issue-link" data-issue-key="LU-639"><del>LU-639</del></a>! So, I decided to back-port associated change (<a href="http://review.whamcloud.com/1896" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/1896</a>) to b2_1 and see if it fixes. I give it a try at <a href="http://review.whamcloud.com/6670" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/6670</a>.</p> Development Rank 1|hzvdjr: Rank (Obsolete) 5801 Severity