[LU-5029] LFSCK 5: The OST will use new FID sequence when detect inconsistent LAST_ID file Created: 08/May/14  Updated: 30/Jan/22

Status: In Progress
Project: Lustre
Component/s: None
Affects Version/s: Lustre 2.6.0
Fix Version/s: None

Type: Improvement Priority: Minor
Reporter: nasf (Inactive) Assignee: nasf (Inactive)
Resolution: Unresolved Votes: 0
Labels: None

Severity: 3
Rank (Obsolete): 13910

 Description   

Currently, it is the LFSCK on the OST to rebuild the LAST_ID file if found related inconsistency. And during the LFSCK rebuilding the LAST_ID files, the OST device will become read-only to avoid more damage caused by some FID allocation against the bad LAST_ID file. Such method can work, but it may be not the best, because for a large device, the LFSCK may last some long time to scan the whole device. Instead, if the OST can use new FID sequence, then it can guarantee that the new allocated FID will be valid. It will simplify not only the LFSCK on the OST but also the MDT-OST recovery.


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