[LU-4553] LFSCK 5: LFSCK behaviour if an OST is permanently unavailable

• Type: Improvement
• Resolution: Unresolved
• Priority: Major
• Affects Version/s: Lustre 2.6.0
• Assignee: WC Triage
• Reporter: Andreas Dilger

Description

We had a discussion during the 2.6 testing concall about what the behaviour of LFSCK is, or should be, if there an OST that is permanently unavailable?

If the administrator has permanently marked the OST inactive, will LFSCK ever be able to complete?

Will it be able to detect and report objects that are on the failed OST? Is there an option to delete such files?

Will it create new objects on a different OST?

If there are no files referencing objects on the inactive OST (e.g. if administrator has previously run "lfs getstripe -O {OST}" or LFSCK to find and delete such files) will it be possible for LFSCK to complete?

Issue Links

• is related to: LU-1738 lfs find cannot find files in OST that died, whilst lfs getstripe can
• is related to: LU-1267 LFSCK II: MDT-OST consistency check/repair