[
https://issues.apache.org/jira/browse/HADOOP-6080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12725696#action_12725696
]
Jakob Homan commented on HADOOP-6080:
-------------------------------------
bq. Should we consider excluding trash for files deleted from /tmp (ie make
-skipTrash implicit when deleting from /tmp.)?
I'm not a fan of special cases for certain directories, even for /tmp, and
particularly when we're already straying away from the posix world with the
trash feature. Minimizing surprise seems a good goal, and I'd be very
surprised if I were accustomed to explicitly skipping the trash when I want and
discovering something I had expected to be trashed had been helpfully nuked by
the system.
> 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.
