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-3391 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="http://maloo.whamcloud.com/test_sets/f5f6460c-c409-11e2-a2df-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">http://maloo.whamcloud.com/test_sets/f5f6460c-c409-11e2-a2df-52540035b04c</a>.</p> <p>The sub-test test_154 failed with the following error:</p> <blockquote> <p>setxattr should fail.</p></blockquote> <p>MDS dmesg shows:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>Lustre: DEBUG MARKER: == sanity test 154: Open-by-FID == 16:34:42 (1369352082) LustreError: 23760:0:(fld_handler.c:169:fld_server_lookup()) srv-lustre-MDT0000: Cannot find sequence 0xf00000400: rc = -5 LustreError: 23760:0:(fld_handler.c:169:fld_server_lookup()) Skipped 1 previous similar message Lustre: 23760:0:(mdd_device.c:561:obf_lookup()) lustre-MDD0000: bad FID format [f.sanity.154], should be [0x200000400:0x1:0x0] Lustre: DEBUG MARKER: sanity test_154: @@@@@@ FAIL: setxattr should fail. </pre> </div></div> client: 2.3.0<br/> server: lustre-master tag-2.4.50 LU-3391

Interop 2.3.0<->2.4 failure on test suite sanity test_154: setxattr should fail

Bug Minor Resolved Won't Fix Nathaniel Clark Maloo Fri, 24 May 2013 03:38:38 +0000 Thu, 25 Feb 2016 18:04:00 +0000 Thu, 25 Feb 2016 18:04:00 +0000 Lustre 2.3.0 0 6 <p>It looks like there is a bug in the test script, where it is using the filename instead of the FID for open-by-fid in some cases. Not sure why it is inconsistent. </p> <p>My guess is the unknown sequence error is because the "fid" that is passed coincidentally has "f" at the start, and somehow gets interpreted as 0xf00000400? </p> <p>If that is not the case, then there may be a more serious underlying problem, so we'd like some investigation (hopefully today) to determine the root cause. </p> <p>In change <a href="http://review.whamcloud.com/5298" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/5298</a> the prohibition to setxattr on .lustre and .lustre/fid was removed so the 2.3.0 check to ensure it fails is no longer valid for 2.4 MDTs (2.3.64 and following).</p> <p>Should I submit a patch on b2_3 to fix this?</p> <p>Lustre client: <a href="http://build.whamcloud.com/job/lustre-b2_3/41/" class="external-link" target="_blank" rel="nofollow noopener">http://build.whamcloud.com/job/lustre-b2_3/41/</a> (2.3.0)<br/> Lustre server: <a href="http://build.whamcloud.com/job/lustre-b2_4/44/" class="external-link" target="_blank" rel="nofollow noopener">http://build.whamcloud.com/job/lustre-b2_4/44/</a> (2.4.1 RC1)</p> <p>sanity test 154 hit the same failure:<br/> <a href="https://maloo.whamcloud.com/test_sets/cde5bab8-14f3-11e3-9828-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/cde5bab8-14f3-11e3-9828-52540035b04c</a></p> <p>Lustre client: <a href="http://build.whamcloud.com/job/lustre-b2_3/41/" class="external-link" target="_blank" rel="nofollow noopener">http://build.whamcloud.com/job/lustre-b2_3/41/</a> (2.3.0)<br/> Lustre server: <a href="http://build.whamcloud.com/job/lustre-b2_4/69/" class="external-link" target="_blank" rel="nofollow noopener">http://build.whamcloud.com/job/lustre-b2_4/69/</a> (2.4.2 RC1)</p> <p>sanity test 154 hit the same failure:<br/> <a href="https://maloo.whamcloud.com/test_sets/3c82ea6e-685e-11e3-a16f-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/3c82ea6e-685e-11e3-a16f-52540035b04c</a></p> Development Rank 1|hzvrrr: Rank (Obsolete) 8394 Severity