[LU-3454] open (O_TRUNC) and truncate(0) on a released file must not trig a restore Created: 11/Jun/13  Updated: 05/Aug/20  Resolved: 30/Aug/13

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

Type: New Feature Priority: Blocker
Reporter: CEA Assignee: Jinshan Xiong (Inactive)
Resolution: Duplicate Votes: 0
Labels: HSM, MB

Issue Links:
Duplicate
is duplicated by LU-3817 Fix sanity-hsm test 58: "Truncate 0 o... Resolved
Related
is related to LU-3817 Fix sanity-hsm test 58: "Truncate 0 o... Resolved
is related to LU-3818 Fix sanity-hsm test 59: "Truncate != ... Closed
is related to LU-3608 HSM Master Ticket for 2.5 Landings Resolved
Rank (Obsolete): 8635

 Description   

HSM restore is triggered on data access, to avoid useless restore, it is better to remove released state at open(O_TRUNC) or truncate(0).
For truncate(size != 0) a full restore must be done first (a partial one can be done in a futur patch).

 Comments   
Comment by Peter Jones [ 12/Jun/13 ]

Jinshan

I understand that you are assisting with HSM-related work

Peter

Comment by Jinshan Xiong (Inactive) [ 23/Aug/13 ]

I;m working on this issue.

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