[ https://issues.apache.org/jira/browse/HDFS-7281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ming Ma updated HDFS-7281: -------------------------- Release Note: The patch improves the reporting around missing blocks and corrupted blocks. 1. A block is missing if and only if all DNs of its expected replicas are dead. 2. A block is corrupted if and only if all its available replicas are corrupted. So if a block has 3 replicas; one of the DN is dead, the other two replicas are corrupted; it will be marked as corrupted. 3. A new line is added to fsck output to display the corrupt block size per file. 4. A new line is added to fsck output to display the number of missing blocks in the summary section. > Missing block is marked as corrupted block > ------------------------------------------ > > Key: HDFS-7281 > URL: https://issues.apache.org/jira/browse/HDFS-7281 > Project: Hadoop HDFS > Issue Type: Bug > Reporter: Ming Ma > Assignee: Ming Ma > Labels: supportability > Attachments: HDFS-7281-2.patch, HDFS-7281-3.patch, HDFS-7281-4.patch, > HDFS-7281.patch > > > In the situation where the block lost all its replicas, fsck shows the block > is missing as well as corrupted. Perhaps it is better not to mark the block > corrupted in this case. The reason it is marked as corrupted is > numCorruptNodes == numNodes == 0 in the following code. > {noformat} > BlockManager > final boolean isCorrupt = numCorruptNodes == numNodes; > {noformat} > Would like to clarify if it is the intent to mark missing block as corrupted > or it is just a bug. -- This message was sent by Atlassian JIRA (v6.3.4#6332)