[
https://issues.apache.org/jira/browse/HDFS-6488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14346097#comment-14346097
]
Hadoop QA commented on HDFS-6488:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12702216/HDFS-6488.003.patch
against trunk revision e17e5ba.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{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 hadoop-hdfs-project/hadoop-hdfs-nfs:
org.apache.hadoop.hdfs.server.namenode.TestFileTruncate
The test build failed in
hadoop-hdfs-project/hadoop-hdfs-nfs
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/9712//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/9712//console
This message is automatically generated.
> HDFS superuser unable to access user's Trash files using NFSv3 mount
> --------------------------------------------------------------------
>
> Key: HDFS-6488
> URL: https://issues.apache.org/jira/browse/HDFS-6488
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: nfs
> Affects Versions: 2.3.0
> Reporter: Stephen Chu
> Assignee: Brandon Li
> Attachments: HDFS-6488.001.patch, HDFS-6488.002.patch,
> HDFS-6488.003.patch
>
>
> As hdfs superuseruser on the NFS mount, I cannot cd or ls the
> /user/schu/.Trash directory:
> {code}
> bash-4.1$ cd .Trash/
> bash: cd: .Trash/: Permission denied
> bash-4.1$ ls -la
> total 2
> drwxr-xr-x 4 schu 2584148964 128 Jan 7 10:42 .
> drwxr-xr-x 4 hdfs 2584148964 128 Jan 6 16:59 ..
> drwx------ 2 schu 2584148964 64 Jan 7 10:45 .Trash
> drwxr-xr-x 2 hdfs hdfs 64 Jan 7 10:42 tt
> bash-4.1$ ls .Trash
> ls: cannot open directory .Trash: Permission denied
> bash-4.1$
> {code}
> When using FsShell as hdfs superuser, I have superuser permissions to schu's
> .Trash contents:
> {code}
> bash-4.1$ hdfs dfs -ls -R /user/schu/.Trash
> drwx------ - schu supergroup 0 2014-01-07 10:48
> /user/schu/.Trash/Current
> drwx------ - schu supergroup 0 2014-01-07 10:48
> /user/schu/.Trash/Current/user
> drwx------ - schu supergroup 0 2014-01-07 10:48
> /user/schu/.Trash/Current/user/schu
> -rw-r--r-- 1 schu supergroup 4 2014-01-07 10:48
> /user/schu/.Trash/Current/user/schu/tf1
> {code}
> The NFSv3 logs don't produce any error when superuser tries to access schu
> Trash contents. However, for other permission errors (e.g. schu tries to
> delete a directory owned by hdfs), there will be a permission error in the
> logs.
> I think this is not specific to the .Trash directory perhaps.
> I created a /user/schu/dir1 which has the same permissions as .Trash (700).
> When I try cd'ing into the directory from the NFSv3 mount as hdfs superuser,
> I get the same permission denied.
> {code}
> [schu@hdfs-nfs ~]$ hdfs dfs -ls
> Found 4 items
> drwx------ - schu supergroup 0 2014-01-07 10:57 .Trash
> drwx------ - schu supergroup 0 2014-01-07 11:05 dir1
> -rw-r--r-- 1 schu supergroup 4 2014-01-07 11:05 tf1
> drwxr-xr-x - hdfs hdfs 0 2014-01-07 10:42 tt
> bash-4.1$ whoami
> hdfs
> bash-4.1$ pwd
> /hdfs_nfs_mount/user/schu
> bash-4.1$ cd dir1
> bash: cd: dir1: Permission denied
> bash-4.1$
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
