[LU-8808] Concurrent update during file restore can lead to disordered changelog sequence Created: 07/Nov/16  Updated: 26/Mar/17  Resolved: 26/Mar/17

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

Type: Bug Priority: Minor
Reporter: Bruno Faccini (Inactive) Assignee: Bruno Faccini (Inactive)
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Related
Severity: 3
Rank (Obsolete): 9223372036854775807

 Description   

In hsm_cdt_request_completed(), upon restore completion, layout lock is returned before associated ChangeLog entry has been created.
This allows for a timing window where concurrent file updater can take control and create its own ChangeLog out of order (before restore ChangeLog).
This can puzzle, ChangeLog readers (like RobinHood), and have them think of a wrong file state.

 Comments   
Comment by Gerrit Updater [ 07/Nov/16 ]

Faccini Bruno (bruno.faccini@intel.com) uploaded a new patch: http://review.whamcloud.com/23638
Subject: LU-8808 mdt: avoid out of order ChangeLog during restore
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: eadf8006d336433f80c65223b419210a665fffd8

Comment by Gerrit Updater [ 26/Mar/17 ]

Oleg Drokin (oleg.drokin@intel.com) merged in patch https://review.whamcloud.com/23638/
Subject: LU-8808 mdt: avoid out of order ChangeLog during restore
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: 17ab869d3a37607dbfb2ca8d85ac3549c539f148

Comment by Peter Jones [ 26/Mar/17 ]

Lanced for 2.10

Generated at Sat Feb 10 02:20:43 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.