You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Andrew Wang (JIRA)" <ji...@apache.org> on 2014/08/01 19:15:41 UTC
[jira] [Updated] (HADOOP-10902) Deletion of directories with
snapshots will not output reason for trash move failure
[ https://issues.apache.org/jira/browse/HADOOP-10902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Wang updated HADOOP-10902:
---------------------------------
Resolution: Fixed
Fix Version/s: 2.6.0
Status: Resolved (was: Patch Available)
Merged to trunk and branch-2, thanks Stephen!
> Deletion of directories with snapshots will not output reason for trash move failure
> ------------------------------------------------------------------------------------
>
> Key: HADOOP-10902
> URL: https://issues.apache.org/jira/browse/HADOOP-10902
> Project: Hadoop Common
> Issue Type: Improvement
> Affects Versions: 2.4.0
> Reporter: Stephen Chu
> Assignee: Stephen Chu
> Priority: Minor
> Fix For: 2.6.0
>
> Attachments: HADOOP-10902.1.patch
>
>
> When using trash-enabled FsShell to delete a directory that has snapshots, we se an error message saying "Failed to move to trash" but no explanation.
> {code}
> [hdfs@schu-enc2 ~]$ hdfs dfs -rm -r snap
> 2014-07-28 05:45:29,527 INFO [main] fs.TrashPolicyDefault (TrashPolicyDefault.java:initialize(92)) - Namenode trash configuration: Deletion interval = 1440 minutes, Emptier interval = 0 minutes.
> rm: Failed to move to trash: hdfs://schu-enc2.vpc.com:8020/user/hdfs/snap. Consider using -skipTrash option
> {code}
> If we use -skipTrash, then we'll get the explanation: "rm: The directory /user/hdfs/snap cannot be deleted since /user/hdfs/snap is snapshottable and already has snapshots"
> It'd be an improvement to make it clear that dirs with snapshots cannot be deleted when we're using the trash.
--
This message was sent by Atlassian JIRA
(v6.2#6252)