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-1525 Lustre <p>This is a track ticket to submit patch 1874, 2025 and 2026 to 2.3 release.</p> <p>Based on the situation that there is no layout lock implementation on the server side, some stub code is expected on the server side to make sure those patches are working.</p> LU-1525

Submit HSM client side to 2.3 release

Task Minor Resolved Won't Do Jinshan Xiong Jinshan Xiong Fri, 15 Jun 2012 01:27:07 +0000 Mon, 29 May 2017 04:31:17 +0000 Mon, 29 May 2017 04:31:17 +0000 0 8 <p>A memo of test cases will be needed to make sure HSM code is working:</p> <p>1. JC: <a href="http://review.whamcloud.com/#patch,sidebyside,897,12,lustre/tests/sanity.sh" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/#patch,sidebyside,897,12,lustre/tests/sanity.sh</a><br/> 2. JC: yes a simple test is to use lfs setstripe and to check the layout generation number increases and the new stripe is the targeted one<br/> 3. Johann: A test case which just assumes that the layout has been invalidated (e.g. by failing the generation comparison) would have been welcomed</p> <p>Please update this ticket if you think of more test cases, thanks.</p> <p>The tests pointed in 1) are not HSM tests (they even do not need hsm feature) but they test:<br/> 1) layout lock<br/> 2) layout generation number<br/> The tests use the restripe of empty files</p> <p>Hi Jc, thank you for clarifying this. Since layout lock is a part of HSM, I will implement them anyway <img class="emoticon" src="https://jira.whamcloud.com/images/icons/emoticons/wink.png" height="16" width="16" align="absmiddle" alt="" border="0"/></p> Development Rank 1|hzvf7z: Rank (Obsolete) 6111