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

• Status: Open
• Project: Lustre
• Affects Version/s: Lustre 2.8.0, Lustre 2.9.0, Lustre 2.10.0
• Type: Bug
• Priority: Trivial
• Reporter: James A Simmons
• Assignee: nasf (Inactive)
• Resolution: Unresolved

Environment

Any server that runs lfsck in dry-run mode.

• Severity: 3

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 "fail...

Comments

[Peter Jones]

Fan Yong

Could you please advise with this one?

Thanks

Peter

[James A Simmons]

Does a tool exist that can create errors at the OSD level so lfsck can be tested?

[nasf (Inactive)]

In theory, if there are inconsistent items detected by LFSCK, then "debug=+lfsck" will show related LFSCK actions, in spite of dryrun mode or not, unless the log is overwritten. To verify that, we can inject some failure stub as sanity-lfsck does. For example, sanity-lfsck test_14 will simulate dangling LOV EA reference case.

[nasf (Inactive)]

James,

Have you tried the LFSCK with some failure injection to simulate the inconsistent cases? Is there still no logs with dryrun mode for that?

Thanks!

[nasf (Inactive)]

simmonsja,

Any further feedback for this ticket?

[James A Simmons]

Sorry I haven't got around to looking into this. Please keep the ticket open for now. I will talk to our admins about what they are looking for exactly.