[LU-4870] LFSCK3: Race between layout LFSCK and metadata migration Created: 08/Apr/14  Updated: 04/Feb/15  Resolved: 04/Feb/15

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

Type: Bug Priority: Critical
Reporter: nasf (Inactive) Assignee: nasf (Inactive)
Resolution: Fixed Votes: 0
Labels: MB

Severity: 3
Rank (Obsolete): 13463

 Description   

According to current metadata migration implementation, before the old MDT-object is removed, both the new MDT-object and old MDT-object will reference the same LOV layout. Then if the layout LFSCK finds the new MDT-object by race, it will regard related OST-object(s) as multiple referenced case, and will try to create new OST-object(s) for the new MDT-object.



 Comments   
Comment by Gerrit Updater [ 24/Dec/14 ]

Fan Yong (fan.yong@intel.com) uploaded a new patch: http://review.whamcloud.com/13182
Subject: LU-4870 lfsck: lock old MDT-object in migrating
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 42f33938070b9e282d4408114c6aa6c49af35394

Comment by Gerrit Updater [ 04/Feb/15 ]

Oleg Drokin (oleg.drokin@intel.com) merged in patch http://review.whamcloud.com/13182/
Subject: LU-4870 lfsck: lock old MDT-object in migrating
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: 19ae9b3605bd41348b2bd64accc50a34eaaa35a1

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