hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "dhruba borthakur (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-4945) Add BlockTool to query file and its block info
Date Wed, 31 Dec 2008 17:45:44 GMT

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

View raw message