Return-Path: 
 <hdfs-issues-return-156418-apmail-hadoop-hdfs-issues-archive=hadoop.apache.org@hadoop.apache.org>
X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org
Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 097FE1862B
	for <apmail-hadoop-hdfs-issues-archive@minotaur.apache.org>;
 Sun, 27 Mar 2016 08:14:26 +0000 (UTC)
Received: (qmail 78890 invoked by uid 500); 27 Mar 2016 08:14:25 -0000
Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org
Received: (qmail 78831 invoked by uid 500); 27 Mar 2016 08:14:25 -0000
Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:hdfs-issues-help@hadoop.apache.org>
List-Unsubscribe: <mailto:hdfs-issues-unsubscribe@hadoop.apache.org>
List-Post: <mailto:hdfs-issues@hadoop.apache.org>
List-Id: <hdfs-issues.hadoop.apache.org>
Reply-To: hdfs-issues@hadoop.apache.org
Delivered-To: mailing list hdfs-issues@hadoop.apache.org
Received: (qmail 78812 invoked by uid 99); 27 Mar 2016 08:14:25 -0000
Received: from arcas.apache.org (HELO arcas) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 27 Mar 2016 08:14:25 +0000
Received: from arcas.apache.org (localhost [127.0.0.1])
	by arcas (Postfix) with ESMTP id 9C2DC2C14F6
	for <hdfs-issues@hadoop.apache.org>; Sun, 27 Mar 2016 08:14:25 +0000 (UTC)
Date: Sun, 27 Mar 2016 08:14:25 +0000 (UTC)
From: "Lin Yiqun (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12953483.1458874814000.59828.1459066465636@Atlassian.JIRA>
In-Reply-To: <JIRA.12953483.1458874814000@Atlassian.JIRA>
References: <JIRA.12953483.1458874814000@Atlassian.JIRA>
 <JIRA.12953483.1458874814177@arcas>
Subject: [jira] [Commented] (HDFS-10213) there is a corrupt/missing block
 report, but fsck result is HEALTHY
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


    [ https://issues.apache.org/jira/browse/HDFS-10213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15213388#comment-15213388 ] 

Lin Yiqun commented on HDFS-10213:
----------------------------------

Hi, [~wyukawa], can you use fsck {{[-list-corruptfileblocks}} to check whether the result has expected corrupt/missing block or not. There are two different logic to check the corrupt/missing block in cmd {{fsck <path> --list-corruptfileblocks}} and just {{fsck <path>}}. I think the fsck cmd with param {{-list-corruptfileblocks}} would be accurate. And maybe we can adjust the logic of checking corrupt/missing block in fsck <path> the same to cmd with param {{-list-corruptfileblocks}}.

> there is a corrupt/missing block report, but fsck result is HEALTHY
> -------------------------------------------------------------------
>
>                 Key: HDFS-10213
>                 URL: https://issues.apache.org/jira/browse/HDFS-10213
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: fs
>    Affects Versions: 2.7.1
>         Environment: HDP2.4.0
> CentOS6
> JDK1.8
>            Reporter: Wataru Yukawa
>
> I monitor HDFS to check http://namenode.host:port/jmx
> Sometimes, there is a corrupt/missing block report, but fsck result is HEALTHY.
> https://gyazo.com/00988be63b6b1e910994ae26e8519b4d
> It's weird, I am confused...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)