[
https://issues.apache.org/jira/browse/HDFS-5888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13894823#comment-13894823
]
Colin Patrick McCabe commented on HDFS-5888:
--------------------------------------------
I don't see what this has to do with the globber. The globber can resolve the
root inode just fine.
In fact, there's a unit test for this in {{TestGlobPaths}}:
{code}
Path root = new Path(USER_DIR);
status = fs.globStatus(root);
checkStatus(status, root);
{code}
The problem is not on the client side. I ran a "chmod /" and traced it back
all the way to the {{FSNamesystem}}, which seems to be calling
{{FSDirectory#setPermission}} on src=(empty string). Then
{{FSDirectory#unprotectedSetPermission}} locates the root inode and calls
{{INode#setPermission}} on it. For some reason, that doesn't work / take
effect.
There seems to be a more general problem where modifying the root inode fails.
I can't change the owner or group, for example. The INode stuff has been
modified a lot over the last few releases. The inclusion of snapshots, the
Feature work, and probably some other stuff I'm forgetting. I think someone
needs to go in there and do a deep dive to fix this.
By the way, I verified that I could chmod / chown snapshottable directories. I
was a little concerned about that after looking at this problem. But the issue
seems to be specific to root.
> Cannot chmod / with new Globber.
> --------------------------------
>
> Key: HDFS-5888
> URL: https://issues.apache.org/jira/browse/HDFS-5888
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 2.3.0
> Reporter: Andrew Wang
> Assignee: Andrew Wang
>
> Due to some changes in the new Globber code, we can no longer chmod "/". We
> should support this.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
