[LU-14365] ROOT LMA scrub

• Status: Open
• Project: Lustre
• Type: Bug
• Priority: Minor
• Reporter: Lai Siyao
• Assignee: Lai Siyao
• Resolution: Unresolved
• Severity: 3

Description

LFSCK always trust FID in LMA more than FID in directory entry and FID in linkea, but it may be corrupt, or it's an IGIF(upgraded from 1.8), while the FID in child's link}}EA or "{{.." FID is the correct FID. Currently such inconsistency can only be fixed manually, however for special objects like ROOT, it should be able to be repaird automatically. This can be achieved by checking special object LMA during the early mount-time scan, and checking if the subdirectories under ROOT/ have a trusted.link entry matching fid_is_root(), or all have the same ".." FID, in which case the LMA FID is wrong (probably an IGIF FID) and should be fixed to use [FID_SEQ_ROOT:FID_OID_ROOT:0x0], rather than the IGIF FID.

Issue Links

• is duplicated by: LU-14367 ROOT LMA scrub
• is duplicated by: LU-14368 ROOT LMA scrub
• is duplicated by: LU-14369 ROOT LMA scrub

Comments

[Andreas Dilger]

Note, in addition to the fix you described here, it may also be possible to avoid the problem of an IGIF FID in the first place if OI Scrub checks a child directory for its ".." FID and uses that instead of generating an IGIF FID if it finds a directory without any lma xattr.

[Gerrit Updater]

Lai Siyao ([e-mail]) uploaded a new patch: https://review.whamcloud.com/41329
Subject: LU-14365 mdt: lfs mkdir should return -EEXIST if exists
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 50dc0eacf35fab67bed33b6adcb586fb29f796ce