[
https://issues.apache.org/jira/browse/HADOOP-6203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12749630#action_12749630
]
Suresh Srinivas commented on HADOOP-6203:
-----------------------------------------
# The bug description talks about indicating that there was quota related
problem while performing rm. That still is not captured with the new change.
Also since the existing code just captures IOException from
{{trashTmp.moveToTrash()}}, it not setup to capture quota issue.
# FSShell.delete() - This probably exists in the previous version of the code
also. What happens if {{trashTmp.moveToTrash()}} returns -1 when skipTrash flag
is true?
> Improve error message when moving to trash fails due to quota issue
> -------------------------------------------------------------------
>
> Key: HADOOP-6203
> URL: https://issues.apache.org/jira/browse/HADOOP-6203
> Project: Hadoop Common
> Issue Type: Improvement
> Components: fs
> Reporter: Jakob Homan
> Assignee: Boris Shkolnik
> Attachments: HADOOP-6203.patch, HADOOP-6203.patch
>
>
> HADOOP-6080 provided an option for deleting files even when overquota, but
> the error message that's returned in this situation is unhelpful and doesn't
> suggest skipTrash as a remediation:
> {noformat}$ hdfs -rmr /foo/bar/bat/boo
> rmr: Failed to move to trash:
> hdfs://cluster/foo/bar/bat/boo{noformat}
> In this situation, the error message should say there was a quote problem and
> suggest -skipTrash.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
