Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-dev@hadoop.apache.org
Date: Thu, 31 Jan 2013 00:09:13 +0000 (UTC)
From: "Brandon Li (JIRA)" <jira@apache.org>
To: hdfs-dev@hadoop.apache.org
Message-ID: <JIRA.12616895.1353396189721.219083.1359590953060@arcas>
In-Reply-To: <JIRA.12616895.1353396189721@arcas>
References: <JIRA.12616895.1353396189721@arcas>
Subject: [jira] [Resolved] (HDFS-4212) NameNode can't differentiate between
 a never-created block and a block which is really missing
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HDFS-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brandon Li resolved HDFS-4212.
------------------------------

    Resolution: Duplicate
    
> NameNode can't differentiate between a never-created block and a block which is really missing
> ----------------------------------------------------------------------------------------------
>
>                 Key: HDFS-4212
>                 URL: https://issues.apache.org/jira/browse/HDFS-4212
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>    Affects Versions: 1.2.0, 3.0.0
>            Reporter: Brandon Li
>            Assignee: Brandon Li
>         Attachments: hdfs-4212-junit-test.patch
>
>
> In one test case, NameNode allocated a block and then was killed before the client got the addBlock response. 
> After NameNode restarted, the block which was never created was considered as a missing block and FSCK would report the file is corrupted.
> The problem seems to be that, NameNode can't differentiate between a never-created block and a block which is really missing.   

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira