You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Lei Yang (Jira)" <ji...@apache.org> on 2022/10/28 22:18:00 UTC

[jira] [Created] (HDFS-16828) Fsck doesn't count orphaned missing blocks.

Lei Yang created HDFS-16828:
-------------------------------

             Summary: Fsck doesn't count orphaned missing blocks.
                 Key: HDFS-16828
                 URL: https://issues.apache.org/jira/browse/HDFS-16828
             Project: Hadoop HDFS
          Issue Type: Bug
            Reporter: Lei Yang


Fsck use corrputedFIles.size instead of blockManager.getMissinngBlockCount() to get missing blocks. This creates inconsistency with metasave.

In the case where orphaned block is present, metasave and fsck show different result:

metasave shows:

 
{code:java}
Metasave: Blocks currently missing: 1
[orphaned]: blk_106452613228_105447711565 MISSING (replicas: l: 0 d: 0 c: 0 e: 0){code}
 

but fsck -list-corruptfileblocks  shows different count:
{noformat}
The filesystem under path '/' has 0 CORRUPT files
{noformat}
 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org