Return-Path: X-Original-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0173F10845 for ; Thu, 5 Sep 2013 02:04:56 +0000 (UTC) Received: (qmail 23552 invoked by uid 500); 5 Sep 2013 02:04:55 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 23523 invoked by uid 500); 5 Sep 2013 02:04:55 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-issues@hadoop.apache.org Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 23511 invoked by uid 99); 5 Sep 2013 02:04:55 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Sep 2013 02:04:55 +0000 Date: Thu, 5 Sep 2013 02:04:55 +0000 (UTC) From: "Colin Patrick McCabe (JIRA)" To: common-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HADOOP-9929) Insufficient permissions for a path reported as file not found MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HADOOP-9929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758678#comment-13758678 ] Colin Patrick McCabe commented on HADOOP-9929: ---------------------------------------------- ok, that was a bad example since it would succeed. (Wish I could edit comments!) The point is that something like /*/foo would fail since it would try to recurse into the /secret subdirectory. > 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.1.0-beta, 2.0.4-alpha > Reporter: Jason Lowe > Assignee: Colin Patrick McCabe > Attachments: HADOOP-9929.001.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