[LU-1525] Submit HSM client side to 2.3 release Created: 15/Jun/12  Updated: 29/May/17  Resolved: 29/May/17

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Minor
Reporter: Jinshan Xiong (Inactive) Assignee: Jinshan Xiong (Inactive)
Resolution: Won't Do Votes: 0
Labels: None

Rank (Obsolete): 6111

 Description   

This is a track ticket to submit patch 1874, 2025 and 2026 to 2.3 release.

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.



 Comments   
Comment by Jinshan Xiong (Inactive) [ 09/Jul/12 ]

A memo of test cases will be needed to make sure HSM code is working:

1. JC: http://review.whamcloud.com/#patch,sidebyside,897,12,lustre/tests/sanity.sh
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
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

Please update this ticket if you think of more test cases, thanks.

Comment by jacques-charles lafoucriere [ 10/Jul/12 ]

The tests pointed in 1) are not HSM tests (they even do not need hsm feature) but they test:
1) layout lock
2) layout generation number
The tests use the restripe of empty files

Comment by Jinshan Xiong (Inactive) [ 10/Jul/12 ]

Hi Jc, thank you for clarifying this. Since layout lock is a part of HSM, I will implement them anyway

Generated at Sat Feb 10 01:17:24 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.