hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lin Yiqun (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-10213) there is a corrupt/missing block report, but fsck result is HEALTHY
Date Sun, 27 Mar 2016 08:14:25 GMT

    [ 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)

Mime
View raw message