[LU-4895] LFSCK should not create empty OST objects for danging layout references by default

• Type: Technical task
• Resolution: Fixed
• Priority: Blocker
• Fix Version/s: Lustre 2.6.0
• Affects Version/s: Lustre 2.6.0
• Assignee: nasf (Inactive)
• Reporter: Andreas Dilger

Description

Per discussion today, LFSCK phase 2 should not create empty OST objects by default for MDT LOV layouts that reference missing OST objects. By default LFSCK should log an error (see LU-4610) and leave the LOV layout referencing the missing OST object (read/write/stat to the object should continue to return an error).

The administrator can specify an option to delete files with dangling links, or create empty objects to fix the dangling reference. Otherwise, it should leave the dangling reference unfixed.

There should be a generic mechanism for specifying different repair options, including a way of specifying defaults for all of the repair options in a file.

Issue Links

• is related to: LU-5110 Interop 2.5.1<->2.6 failure on test suite sanity-scrub test_15: Failed to start OI scrub on mds1