[LU-13374] open-close operation can lead to loss of file time set performed in the middle Created: 19/Mar/20  Updated: 17/Jan/24

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

Type: Bug Priority: Major
Reporter: Vitaly Fertman Assignee: WC Triage
Resolution: Unresolved Votes: 0
Labels: None

Attachments: Text File test1.patch    
Issue Links:
Related
is related to LU-12026 verify that MDS stores atime/mtime/ct... Resolved
Rank (Obsolete): 9223372036854775807

 Description   

the original request in LU-12026 was to update *time as a part of LSOM update, i.e. to be stored in LSOM ea, but implemented as a regular time update on close, what is obviously wrong because it breaks set-in-past functionality (and in general due to the reasons we have LSOM but not SOM) - close always sends *time but does not bother accurately re-gather them from servers, while the local cache could be already stale. in other words this will not work:
1. client1 open
2. client2 set-in-past
3. client1 close

the reproducer is attached:

— set-in-past on opened file
File: '/mnt/lustre/f26c.sanityn'
Modify: 2020-03-19 22:31:05.000000000 +0300
File: '/mnt/lustre2/f26c.sanityn'
Modify: 2020-03-19 22:31:05.000000000 +0300

— set-in-past on closed file
File: '/mnt/lustre/f26c.sanityn'
Modify: 2000-12-31 14:12:59.000000000 +0300
File: '/mnt/lustre2/f26c.sanityn'
Modify: 2000-12-31 14:12:59.000000000 +0300


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