[ https://issues.apache.org/jira/browse/HADOOP-9929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13771573#comment-13771573 ]
Hadoop QA commented on HADOOP-9929: ----------------------------------- {color:green}+1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12603965/HADOOP-9929.002.patch against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 1 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}. The javadoc tool did not generate any 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 1.3.9) warnings. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:green}+1 core tests{color}. The patch passed unit tests in hadoop-common-project/hadoop-common hadoop-hdfs-project/hadoop-hdfs. {color:green}+1 contrib tests{color}. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/3110//testReport/ Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/3110//console This message is automatically generated. > Insufficient permissions for a path reported as file not found > -------------------------------------------------------------- > > Key: HADOOP-9929 > URL: https://issues.apache.org/jira/browse/HADOOP-9929 > Project: Hadoop Common > Issue Type: Bug > Components: fs > Affects Versions: 2.3.0 > Reporter: Jason Lowe > Assignee: Colin Patrick McCabe > Fix For: 2.3.0 > > Attachments: HADOOP-9929.001.patch, HADOOP-9929.002.patch > > > Using "hadoop fs -ls" to list a path where the permissions of a parent > directory are insufficient ends up reporting "no such file or directory" on > the full path rather than reporting the permission issue. For example: > {noformat} > $ hadoop fs -ls /user/abc/tests/data > ls: `/user/abc/tests/data': No such file or directory > $ hadoop fs -ls /user/abc > ls: Permission denied: user=somebody, access=READ_EXECUTE, > inode="/user/abc":abc:hdfs:drwx------ > {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira