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-2407 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/013a4c58-3980-11e2-9fda-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/013a4c58-3980-11e2-9fda-52540035b04c</a>.</p> <p>The sub-test test_35a failed with the following error:</p> <blockquote> <p>test_35a failed with 4</p></blockquote> <p>test log shows:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>Set up a fake failnode for the MDS CMD: client-26vm7 lctl get_param -n devices CMD: client-26vm7 /usr/sbin/lctl conf_param lustre-MDT0000.failover.node= 127.0.0.2@tcp client-26vm7: error: conf_param: No such device conf-sanity test_35a: @@@@@@ FAIL: test_35a failed with 4 </pre> </div></div> <p>MDS dmesg:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>Lustre: DEBUG MARKER: Set up a fake failnode for the MDS Lustre: DEBUG MARKER: lctl get_param -n devices Lustre: DEBUG MARKER: /usr/sbin/lctl conf_param lustre-MDT0000.failover.node= 127.0.0.2@tcp LustreError: 11886:0:(mgs_llog.c:2684:mgs_write_log_param()) err -19 on param 'failover.node=' LustreError: 11886:0:(mgs_handler.c:1147:mgs_iocontrol()) setparam err -19 Lustre: DEBUG MARKER: /usr/sbin/lctl mark conf-sanity test_35a: @@@@@@ FAIL: test_35a failed with 4 </pre> </div></div> server: 2.3 RHEL6<br/> client: lustre master build #1065 RHEL6 LU-2407

Interop 2.1.3<->2.4 Failure on test suite conf-sanity test_35a: conf_param: No such device

Bug Minor Resolved Fixed Nathaniel Clark Maloo Thu, 29 Nov 2012 19:21:31 +0000 Thu, 15 Aug 2013 06:39:50 +0000 Thu, 11 Jul 2013 14:11:06 +0000 Lustre 2.4.0 Lustre 2.4.1 Lustre 2.5.0 0 6 <p>duplicate of <a href="https://jira.whamcloud.com/browse/LU-2406" title="Interop 2.3&lt;-&gt;2.4 Failure: unable to handle kernel NULL pointer dereference at (null)" class="issue-link" data-issue-key="LU-2406"><del>LU-2406</del></a></p> <p>Hit the same issue when doing interop between 2.1.3 server and 2.4 client. The client build is lustre-master #1127 which should include the fix of <a href="https://jira.whamcloud.com/browse/LU-2406" title="Interop 2.3&lt;-&gt;2.4 Failure: unable to handle kernel NULL pointer dereference at (null)" class="issue-link" data-issue-key="LU-2406"><del>LU-2406</del></a>.</p> <p><a href="https://maloo.whamcloud.com/test_sets/351a6028-4a86-11e2-8a7b-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/351a6028-4a86-11e2-8a7b-52540035b04c</a></p> <p>another instance seen in 2.3.0 server vs 2.4 client:<br/> <a href="https://maloo.whamcloud.com/test_sets/19d3d0ea-5b54-11e2-8985-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/19d3d0ea-5b54-11e2-8985-52540035b04c</a></p> <p>also seen in 2.1.4 server vs 2.4 client:<br/> <a href="https://maloo.whamcloud.com/test_sets/ae414df4-5f35-11e2-b507-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/ae414df4-5f35-11e2-b507-52540035b04c</a></p> <p>The issue was introduced by the change of <a href="http://review.whamcloud.com/4247" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/4247</a>, which added an extra white space between "=" and "$(h2$NETTYPE $FAKENID)". This made the "lctl conf_param" command become:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>/usr/sbin/lctl conf_param lustre-MDT0000.failover.node= 127.0.0.2@tcp </pre> </div></div> <p>As we can see, the fake failover NID was not really set to "failover.node" parameter. So, we need create a patch on master and b2_4 branches to fix this script issue.</p> <p>On the other hand, although the test script had issue, why the same test passed on master and b2_4 branches but failed on master/b2_4&lt;-&gt;b2_3/b2_1 interop combinations?<br/> This is because master and b2_4 branches have the patch of <a href="http://review.whamcloud.com/3670" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/3670</a>, which improves the error handling codes in mgs_modify() and mgs_write_log_failnid_internal() to make sure that setting an empty value to "failover.node" means to remove all failover NIDs. If "failover.node" was empty before, mgs_modify() will return 1 which means no modification is done. However, on b2_3 and b2_1 branches, without the patch, setting an empty value will make mgs_modify() return -ENODEV if "failover.node" had no value before.</p> <p>So, to fix the interop issue, we need backport the error handling codes from master branch to b2_3 and b2_1 branches, or need wait for fixing the test script issue on master and b2_4 branches.</p> <p>Patch for Lustre master branch to remove the extra space: <a href="http://review.whamcloud.com/6779" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/6779</a>. The patch also needs to be cherry-picked to Lustre b2_4 branch.</p> <p>Patches merged to master</p> <blockquote><p>Patch for Lustre master branch to remove the extra space: <a href="http://review.whamcloud.com/6779" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/6779</a>. The patch also needs to be cherry-picked to Lustre b2_4 branch.</p></blockquote> <p>Hi Oleg,<br/> Could you please cherry-pick the above patch to Lustre b2_4 branch? Thanks.</p> <p>Patch was cherry-picked to Lustre b2_4 branch.</p> Development Rank 1|hzvd0v: Rank (Obsolete) 5713 Severity