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.