Details
-
Bug
-
Resolution: Cannot Reproduce
-
Minor
-
None
-
Lustre 2.9.0
-
None
-
Soak cluster, tip of master with one patch
-
3
-
9223372036854775807
Description
We did a clean reboot of the entire cluster and restarted, after the first MDS failover we had a very long lfsck session > 1000 seconds
2016-10-19 12:16:18,529:fsmgmt.fsmgmt:INFO lfsck still in progress for soaked-MDT0000 after 945s
2016-10-19 12:27:01,370:fsmgmt.fsmgmt:ERROR lfsck found errors lola-8/soaked-MDT0000: lf_repaired: 0
2016-10-19 12:27:01,370:fsmgmt.fsmgmt:ERROR lfsck found errors lola-8/soaked-MDT0000: repaired_dangling: 0
2016-10-19 12:27:01,370:fsmgmt.fsmgmt:ERROR lfsck found errors lola-8/soaked-MDT0000: repaired_unmatched_pair: 0
2016-10-19 12:27:01,370:fsmgmt.fsmgmt:ERROR lfsck found errors lola-8/soaked-MDT0000: repaired_multiple_referenced: 0
2016-10-19 12:27:01,371:fsmgmt.fsmgmt:ERROR lfsck found errors lola-8/soaked-MDT0000: repaired_orphan: 0
2016-10-19 12:27:01,371:fsmgmt.fsmgmt:ERROR lfsck found errors lola-8/soaked-MDT0000: repaired_inconsistent_owner: 164693
2016-10-19 12:27:01,371:fsmgmt.fsmgmt:ERROR lfsck found errors lola-8/soaked-MDT0000: repaired_others: 0
Does the value for 'repaired_inconsistent_owner:' indicate the number of errors? Seems rather a lot, if so.