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-4804 Lustre <p>This issue was created by maloo for Nathaniel Clark &lt;nathaniel.l.clark@intel.com&gt;</p> <p>This issue relates to the following test suite run: <a href="http://maloo.whamcloud.com/test_sets/97cf2bae-b21d-11e3-9a4b-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">http://maloo.whamcloud.com/test_sets/97cf2bae-b21d-11e3-9a4b-52540035b04c</a>.</p> <p>The sub-test test_17n failed with the following error:</p> <blockquote> <p>create remote dir error 0</p></blockquote> <p>Info required for matching: sanity 17n</p> LU-4804

Test failure sanity test_17n: create remote dir error

Bug Minor Resolved Cannot Reproduce WC Triage Nathaniel Clark Mon, 24 Mar 2014 15:09:07 +0000 Tue, 5 Nov 2019 20:05:28 +0000 Tue, 5 Nov 2019 20:05:28 +0000 Lustre 2.6.0 0 6 <p>Di,<br/> Can you please comment on this ticket?<br/> Thank you!</p> <p>Just checking the debug log, LWP(between other MDTs and MDT0) is evicted, but I am not sure which RPC is failed because of this, we already add failover support for seq lookup in <a href="https://jira.whamcloud.com/browse/LU-4571" title="sanity test_17n: create remote dir error 0" class="issue-link" data-issue-key="LU-4571"><del>LU-4571</del></a>, so it has to be some other RPC. Unfortunately, I can not find further information in the debug log. Probably we should go with option2 suggested in <a href="https://jira.whamcloud.com/browse/LU-4571" title="sanity test_17n: create remote dir error 0" class="issue-link" data-issue-key="LU-4571"><del>LU-4571</del></a>, i.e. not evict LWP during reconnect after reboot, but then it needs quota to set special flag not to replay the quota lock during recovery. Niu, Could you please comment here?</p> <p>Di,<br/> Am I correct when I think the scenario you describe can also apply to other stages of sanity/test_17n, like the one ending with a "destroy remote dir" error ? I am thinking about this because one of my test session triggered this error (<a href="https://maloo.whamcloud.com/test_sets/92c4a4ee-e4fa-11e3-a294-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/92c4a4ee-e4fa-11e3-a294-52540035b04c</a>), like a few others I found into Maloo stats/search, and the related Lustre debug-logs seem to indicate that an -ESTALE/-116 was returned due to some communication failure between MDSs.</p> <p>Bruno,</p> <p>I did not see the connection between MDT0 and MDT1 is being evicted according to the information in <a href="https://maloo.whamcloud.com/test_sets/92c4a4ee-e4fa-11e3-a294-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/92c4a4ee-e4fa-11e3-a294-52540035b04c</a>, probably different problem as I see. Hmm, I saw this in the debug message,</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>Lustre: lustre-MDT0001-osp-MDT0000: Connection to lustre-MDT0001 (at 10.1.5.234@tcp) was lost; in progress operations using this service will wait for recovery to complete Lustre: lustre-MDT0001-osp-MDT0000: Connection restored to lustre-MDT0001 (at 10.1.5.234@tcp) LustreError: 11613:0:(osp_object.c:355:osp_attr_get()) lustre-MDT0001-osp-MDT0000:osp_attr_get update error [0x440000400:0x22:0x0]: rc = -116 </pre> </div></div> <p>You probably need create a new ticket, or is there one already? Thanks.</p> <p>Bruno,<br/> I created <a href="https://jira.whamcloud.com/browse/LU-5130" title="Test failure sanity test_17n: destroy remote dir error 0" class="issue-link" data-issue-key="LU-5130"><del>LU-5130</del></a> for "destroy remote dir" error</p> <p>Haven't seen this in a long time.</p> Development Rank 1|hzwi6v: Rank (Obsolete) 13219 Severity