[LU-16159] remove update llog files after recovery abort

• Type: Bug
• Resolution: Fixed
• Priority: Minor
• Fix Version/s: Lustre 2.16.0
• Labels: llog recovery
• Severity: 2
• Assignee: Lai Siyao
• Reporter: Lai Siyao

Description

Once recovery is aborted, the existing update logs should be removed, because they are used for recovery only, and if it's corrupt, or inaccessible, if they are kept there after recovery abort, the next recovery will meet with the same issue again, besides, the log file size may become large, retrieving them in recovery may lead to recovery timeout.

Besides this, in LOD device initialization, it should do some sanity check for all update logs on it, if the log file is not accessible (e.g. OI mapping mismatch, which may lead to recovery timeout too), delete the log file FID from update catalog (do not delete this file at the moment because it's inaccessible) so that the log file is not visible to others.

Issue Links

• is related to: LU-16398 ost-pools: FAIL: remove sub-test dirs failed
• is related to: LU-17365 steady LOD update llog connection
• is related to: LU-16336 LFSCK should fix inconsistencies caused by recovery abort
• is related to: LU-15934 client refused mount with -EAGAIN because of missing MDT-MDT llog connection
• is related to: LU-16335 "lfs rm_entry" failed to remove broken directories