[LU-9548] No debug info from lctl set_param debug=+lfsck shows up with lfsck dry-run

• Type: Bug
• Resolution: Unresolved
• Priority: Trivial
• Affects Version/s: Lustre 2.8.0, Lustre 2.9.0, Lustre 2.10.0
• Environment: Any server that runs lfsck in dry-run mode.
• Severity: 3
• Assignee: nasf (Inactive)
• Reporter: James A Simmons

Description

While running lfsck in dry-run mode on our servers we set lctl set_param debug=+lfsck in order to collect debug data to see what files will be impacted by a real lfsck run. The debug logs has zero lfsck debug tracing. This doesn't seem to be correct behavior. We would like to know what repairs would be done before a real lfsck run.

Issue Links

• is related to: LU-9187 LFSCK needs to handle parameter "failout" and "dryrun" properly