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

Jakob Homan commented on HADOOP-6080:
-------------------------------------

Updated patches are good to go on all commons unit tests for trunk and all 
tests for v20.  Test-patch is fine except the incorrect javac warnings, which 
are not related.
{noformat}     [exec] -1 overall.  
     [exec] 
     [exec]     +1 @author.  The patch does not contain any @author tags.
     [exec] 
     [exec]     +1 tests included.  The patch appears to include 3 new or 
modified tests.
     [exec] 
     [exec]     +1 javadoc.  The javadoc tool did not generate any warning 
messages.
     [exec] 
     [exec]     -1 javac.  The applied patch generated 64 javac compiler 
warnings (more than the trunk's current 124 warnings).
     [exec] 
     [exec]     +1 findbugs.  The patch does not introduce any new Findbugs 
warnings.
     [exec] 
     [exec]     +1 release audit.  The applied patch does not increase the 
total number of release audit warnings.{noformat}

> Handling of  Trash with quota
> -----------------------------
>
>                 Key: HADOOP-6080
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6080
>             Project: Hadoop Common
>          Issue Type: New Feature
>          Components: fs
>            Reporter: Koji Noguchi
>            Assignee: Jakob Homan
>         Attachments: HADOOP-6080-v20.patch, HADOOP-6080.patch, 
> javac_warnings_diff.txt
>
>
> Currently with quota turned on, user cannot call '-rmr' on large directory 
> that causes over quota.
> {noformat}
> [knoguchi src]$ hadoop dfs -rmr /tmp/net2
> rmr: Failed to move to trash: hdfs://abc.def.com/tmp/net2
> [knoguchi src]$ hadoop dfs -mv /tmp/net2 /user/knoguchi/.Trash/Current
> mv: org.apache.hadoop.hdfs.protocol.QuotaExceededException: The quota of 
> /user/knoguchi is exceeded: namespace
> quota=37500 file count=37757, diskspace quota=-1 diskspace=1991250043353
> {noformat}
> Besides from error message being unfriendly, how should this be handled?

-- 
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