Return-Path: 
 <core-dev-return-58695-apmail-hadoop-core-dev-archive=hadoop.apache.org@hadoop.apache.org>
Delivered-To: apmail-hadoop-core-dev-archive@www.apache.org
Received: (qmail 20619 invoked from network); 31 Dec 2008 17:46:13 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 31 Dec 2008 17:46:13 -0000
Received: (qmail 10330 invoked by uid 500); 31 Dec 2008 17:46:07 -0000
Delivered-To: apmail-hadoop-core-dev-archive@hadoop.apache.org
Received: (qmail 10283 invoked by uid 500); 31 Dec 2008 17:46:07 -0000
Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:core-dev-help@hadoop.apache.org>
List-Unsubscribe: <mailto:core-dev-unsubscribe@hadoop.apache.org>
List-Post: <mailto:core-dev@hadoop.apache.org>
List-Id: <core-dev.hadoop.apache.org>
Reply-To: core-dev@hadoop.apache.org
Delivered-To: mailing list core-dev@hadoop.apache.org
Received: (qmail 10272 invoked by uid 99); 31 Dec 2008 17:46:07 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 31 Dec 2008 09:46:07 -0800
X-ASF-Spam-Status: No, hits=-2000.0 required=10.0
	tests=ALL_TRUSTED
X-Spam-Check-By: apache.org
Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 31 Dec 2008 17:46:05 +0000
Received: from brutus (localhost [127.0.0.1])
	by brutus.apache.org (Postfix) with ESMTP id 72F6A234C4AF
	for <core-dev@hadoop.apache.org>; Wed, 31 Dec 2008 09:45:44 -0800 (PST)
Message-ID: <920507206.1230745544469.JavaMail.jira@brutus>
Date: Wed, 31 Dec 2008 09:45:44 -0800 (PST)
From: "dhruba borthakur (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-4945) Add BlockTool to query file and its
 block info
In-Reply-To: <1847605947.1230178844431.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org


    [ https://issues.apache.org/jira/browse/HADOOP-4945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12660106#action_12660106 ] 

dhruba borthakur commented on HADOOP-4945:
------------------------------------------

Hello zhangwei, thanks for looking into whether the "mode2" functionality be incorporated into fsck itself (without making the fsck code much more complicated).

> Add BlockTool to query file and its block info
> ----------------------------------------------
>
>                 Key: HADOOP-4945
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4945
>             Project: Hadoop Core
>          Issue Type: New Feature
>    Affects Versions: site
>            Reporter: zhangwei
>             Fix For: site
>
>         Attachments: HADOOP-4945.patch
>
>
> The fsck can get the file's block detail,but when you want see which file or datanode the block belongs to ,it will be helpless.
> The BlockTool will be  helpfull in developing,for example when you happened to these message :
> 2008-12-25 12:12:10,049 WARN  dfs.DataNode (DataNode.java:readBlock(901)) - Got exception while serving blk_28622148 to /10.7
> 3.4.101:
> java.io.IOException: Block blk_28622148 is not valid.
>         at org.apache.hadoop.dfs.FSDataset.getBlockFile(FSDataset.java:541)
>         at org.apache.hadoop.dfs.DataNode$BlockSender.<init>(DataNode.java:1090)
>         at org.apache.hadoop.dfs.DataNode$DataXceiver.readBlock(DataNode.java:882)
>         at org.apache.hadoop.dfs.DataNode$DataXceiver.run(DataNode.java:840)
>         at java.lang.Thread.run(Thread.java:595)
> the Blocktool may help you to get the location,it can get the file name and which datanodes hold the block. 
> Also it can get the file or directory 's block details too.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.