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-3730 Lustre <p>Sanity-hsm test_3 is failing alot:</p> <p>One example can be seen here: <a href="https://maloo.whamcloud.com/test_sets/0c378cde-ff90-11e2-a3fb-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/0c378cde-ff90-11e2-a3fb-52540035b04c</a></p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>test_3 Error: 'could not create file' Failure Rate: 27.00% of last 100 executions [all branches] </pre> </div></div> <p>The only thing of interest I found so far is from the MDS console. <br/> 1454 error messages:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>05:39:27:Lustre: DEBUG MARKER: == sanity-hsm test 3: Check file dirtyness when opening for write == 05:39:24 (1375879164) 05:39:27:LustreError: 1146:0:(mdt_xattr.c:134:mdt_getxattr_one()) getxattr failed: -61 05:39:27:LustreError: 1146:0:(mdt_xattr.c:134:mdt_getxattr_one()) Skipped 1453 previous similar messages 05:39:27:Lustre: DEBUG MARKER: /usr/sbin/lctl mark sanity-hsm test_3: @@@@@@ FAIL: could not create file </pre> </div></div> <p>Tests after this tend to fail as well.</p> autotest LU-3730

sanity-hsm test_3 Error: 'could not create file'

Bug Critical Resolved Fixed Jinshan Xiong Keith Mannthey HSM revzfs Fri, 9 Aug 2013 16:15:14 +0000 Tue, 31 Aug 2021 03:50:54 +0000 Thu, 12 Sep 2013 15:35:01 +0000 Lustre 2.5.0 0 8 <p>Another failure at: <a href="https://maloo.whamcloud.com/test_sets/aa3d4616-001d-11e3-a856-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/aa3d4616-001d-11e3-a856-52540035b04c</a><br/> This one with ZFS.</p> <p>Jinshan, as you already documented in <a href="https://jira.whamcloud.com/browse/LU-3704" title="sanity-hsm test_21 - test_24 Error: &#39;could not release file&#39;" class="issue-link" data-issue-key="LU-3704"><del>LU-3704</del></a>, test_3 failures are due to ENODATA return during <span class="error">&#91;cp -p /etc/passwd $TESTFILE.append || error &quot;could not create file&quot;&#93;</span> command when trying to set "system.posix_acl_access" XATTR. But why are some XATTRs part of "cp -p" work ? And in any case we may just check that file content after copy is ok in the test ?</p> <p>There was no such information to indicate why reading acl access info failed. From the test case itself, I feel it's not necessary to use `cp -p' so changing it to `cp' would work.</p> <p>This appears to be a duplicate of <a href="https://jira.whamcloud.com/browse/LU-3713" title="Failure on test suite sanity test_17k: get_xattr_names: llistxattr failed" class="issue-link" data-issue-key="LU-3713"><del>LU-3713</del></a></p> <p>This should be fixed by <a href="https://jira.whamcloud.com/browse/LU-3669" title="(mdt_xattr.c:178:mdt_getxattr()) ASSERTION( lu_object_assert_exists(&amp;info-&gt;mti_object-&gt;mot_obj) ) failed:" class="issue-link" data-issue-key="LU-3669"><del>LU-3669</del></a> patch <a href="http://review.whamcloud.com/7208/" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/7208/</a></p> <p>This seems to be fixed now that <a href="https://jira.whamcloud.com/browse/LU-3669" title="(mdt_xattr.c:178:mdt_getxattr()) ASSERTION( lu_object_assert_exists(&amp;info-&gt;mti_object-&gt;mot_obj) ) failed:" class="issue-link" data-issue-key="LU-3669"><del>LU-3669</del></a> has been closed.</p> Duplicate LU-3713 LU-3669 Related LU-3704 Development Rank 1|hzvxmf: Rank (Obsolete) 9628 Severity