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-3761 Lustre <p>This issue was created by maloo for Li Wei &lt;liwei@whamcloud.com&gt;</p> <p>This issue relates to the following test suite run: <a href="http://maloo.whamcloud.com/test_sets/b716e4c2-0523-11e3-925a-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">http://maloo.whamcloud.com/test_sets/b716e4c2-0523-11e3-925a-52540035b04c</a>.</p> <p>The sub-test test_55 failed with the following error:</p> <blockquote> <p>request on 0x2000013a3:0x2:0x0 is not FAILED</p></blockquote> <p>Info required for matching: sanity-hsm 55</p> <blockquote> <p>== sanity-hsm test 55: Truncate during an archive cancels it == 08:22:27 (1376493747)<br/> Purging archive<br/> Starting copytool<br/> lhsmtool_posix --hsm-root /tmp/arc --daemon --bandwidth 1 /mnt/lustre<br/> 2+0 records in<br/> 2+0 records out<br/> 2097152 bytes (2.1 MB) copied, 0.464772 s, 4.5 MB/s<br/> CMD: wtm-10vm7 /usr/sbin/lctl get_param -n mdt.lustre-MDT0000.hsm.agent_actions | grep 0x2000013a3:0x2:0x0 | grep action=ARCHIVE | cut -f 13 -d ' ' | cut -f 2 -d =<br/> <span class="error">&#91;...&#93;</span><br/> CMD: wtm-10vm7 /usr/sbin/lctl get_param -n mdt.lustre-MDT0000.hsm.agent_actions | grep 0x2000013a3:0x2:0x0 | grep action=ARCHIVE | cut -f 13 -d ' ' | cut -f 2 -d =<br/> Update not seen after 100s: wanted 'FAILED' got ''<br/> sanity-hsm test_55: @@@@@@ FAIL: request on 0x2000013a3:0x2:0x0 is not FAILED </p></blockquote> LU-3761

sanity-hsm 55: request on 0x2000013a3:0x2:0x0 is not FAILED

Bug Critical Resolved Duplicate Jinshan Xiong Maloo HSM Thu, 15 Aug 2013 01:44:39 +0000 Wed, 19 Mar 2014 16:08:29 +0000 Wed, 19 Mar 2014 16:08:29 +0000 Lustre 2.5.0 0 6 <p>Jinshan,<br/> Can you have a look at this one and upgrade to blocker if needed?<br/> Thank you!</p> <p>It turns out the way wait_request_state() implemented is unreliable. It depends on the HSM llog state for the progress but if the operation already finished when the client is acquiring the state, the check will fail because there is nothing in agent_actions.</p> <p>Probably we can change HSM llog a little bit to delay deleting items. It should be good for testing purpose.</p> <p>There is already a tunnable cdt_delay which set the number of seconds before a llog entry in a finished state (SUCCESS ou FAILURE) is removed. The default is 60s, sanity-hsm change it to 10s, so this value is too small.</p> <p>Is this parameter for testing purpose only? Because I can't think of a reason why coordinator needs to delay deleting an entry.</p> <p>So I wonder why is this a blocker, can somebody explain the nature of the problem in some detail please?</p> <p>I tend to think this is a timing issue where we expect that archive would fail when a truncate is on going, however, the archive operation may have already finished before truncate is started. In that case, this test case will fail.</p> <p>I will work out a patch.</p> <p>The posix CT has a parameter --bandwith which limit the visible BW on read an writes, so given a file size you have an idea of the archive/restore time. If the file is large enough the race will disappear</p> <p>This issue should have been fixed at <a href="https://jira.whamcloud.com/browse/LU-3815" title="Fix sanity-hsm test 34: &quot;Remove file during restore&quot;" class="issue-link" data-issue-key="LU-3815"><del>LU-3815</del></a> where it addressed a similar issue. Let's close it for now.</p> Related LU-3863 LU-3969 Development Rank 1|hzvy07: Rank (Obsolete) 9693 Severity