[ https://issues.apache.org/jira/browse/HDFS-6663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14129432#comment-14129432 ]
Hadoop QA commented on HDFS-6663: --------------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12667862/HDFS-6663-3.patch against trunk revision b02a4b4. {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 2 new or modified test files. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 javadoc{color}. There were no new javadoc warning messages. {color:green}+1 eclipse:eclipse{color}. The patch built with eclipse:eclipse. {color:green}+1 findbugs{color}. The patch does not introduce any new Findbugs (version 2.0.3) warnings. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:red}-1 core tests{color}. The patch failed these unit tests in hadoop-hdfs-project/hadoop-hdfs: org.apache.hadoop.hdfs.server.namenode.ha.TestPipelinesFailover org.apache.hadoop.hdfs.server.datanode.TestNNHandlesBlockReportPerStorage {color:green}+1 contrib tests{color}. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/7989//testReport/ Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/7989//console This message is automatically generated. > Admin command to track file and locations from block id > ------------------------------------------------------- > > Key: HDFS-6663 > URL: https://issues.apache.org/jira/browse/HDFS-6663 > Project: Hadoop HDFS > Issue Type: New Feature > Affects Versions: 2.5.0 > Reporter: Kihwal Lee > Assignee: Chen He > Attachments: HDFS-6663-2.patch, HDFS-6663-3.patch, HDFS-6663-3.patch, > HDFS-6663-WIP.patch, HDFS-6663.patch > > > A dfsadmin command that allows finding out the file and the locations given a > block number will be very useful in debugging production issues. It may be > possible to add this feature to Fsck, instead of creating a new command. -- This message was sent by Atlassian JIRA (v6.3.4#6332)