[ 
https://issues.apache.org/jira/browse/HADOOP-4368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12668235#action_12668235
 ] 

Craig Macdonald commented on HADOOP-4368:
-----------------------------------------


Here's what I propose:

 * getCapacityTotal(), getCapacityUsed(), getCapacityRemaining() remain in 
FSNamesystem, but implement these using the return from getStats(). 

 * I don't known JMX, but I think deprecating and ultimately removing the above 
getCapacity*() methods in favour of getStats() would make the use of the 
relevant statistics more difficult?

 * Other changes to DistributedFileSystem and DFSClient remain as in your 
original review.

> Superuser privileges required to do "df"
> ----------------------------------------
>
>                 Key: HADOOP-4368
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4368
>             Project: Hadoop Core
>          Issue Type: Wish
>          Components: dfs, libhdfs
>    Affects Versions: 0.18.1
>            Reporter: Brian Bockelman
>            Assignee: Craig Macdonald
>            Priority: Minor
>         Attachments: fuse_statfs.patch, fuse_statfs_trunk.patch, 
> hadoop4368.fsstatus.patch, hadoop4368.fsstatus.v2.patch, 
> hadoop4368.fsstatus.v3.patch, hadoop4368.fsstatus.v4.patch, 
> hadoop4368.fsstatus.v5.patch
>
>   Original Estimate: 0.17h
>  Remaining Estimate: 0.17h
>
> super user privileges are required in DFS in order to get the file system 
> statistics (FSNamesystem.java, getStats method).  This means that when HDFS 
> is mounted via fuse-dfs as a non-root user, "df" is going to return 
> 16exabytes total and 0 free instead of the correct amount.
> As far as I can tell, there's no need to require super user privileges to see 
> the file system size (and historically in Unix, this is not required).
> To fix this, simply comment out the privilege check in the getStats method.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to