[HDFS-10826] Correctly report missing EC blocks in FSCK

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.0.0-alpha2
• Component/s: erasure-coding
• Hadoop Flags: Reviewed
• Assignee: Takanobu Asanuma
• Reporter: Takanobu Asanuma
• Created: 01/Sep/16 10:27
• Updated: 02/Oct/19 17:14
• Resolved: 06/Oct/16 22:08

Description

For RS-6-3, when there is one ec block group and
1) 0~3 out of 9 internal blocks are missing, the result of fsck is HEALTY.
2) 4~8 out of 9 internal blocks are missing, the result of fsck is HEALTY.

Erasure Coded Block Groups:
 Total size:    536870912 B
 Total files:   1
 Total block groups (validated):        1 (avg. block group size 536870912 B)
  ********************************
  UNRECOVERABLE BLOCK GROUPS:   1 (100.0 %)
  ********************************
 Minimally erasure-coded block groups:  0 (0.0 %)
 Over-erasure-coded block groups:       0 (0.0 %)
 Under-erasure-coded block groups:      1 (100.0 %)
 Unsatisfactory placement block groups: 0 (0.0 %)
 Default ecPolicy:              RS-DEFAULT-6-3-64k
 Average block group size:      5.0
 Missing block groups:          0
 Corrupt block groups:          0
 Missing internal blocks:       4 (44.444443 %)
FSCK ended at Wed Aug 31 13:42:05 JST 2016 in 4 milliseconds

The filesystem under path '/' is HEALTHY

3) 9 out of 9 internal blocks are missing, the result of fsck is CRITICAL. (Because it is regarded as a missing block group.)

In case 2), the result should be CRITICAL since the ec block group is unrecoverable.