[ https://issues.apache.org/jira/browse/HDFS-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tsz Wo (Nicholas), SZE resolved HDFS-4767. ------------------------------------------ Resolution: Fixed I have committed this. Thanks, Jing! > directory is not snapshottable after clrQuota > --------------------------------------------- > > Key: HDFS-4767 > URL: https://issues.apache.org/jira/browse/HDFS-4767 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: namenode > Reporter: Ramya Sunil > Assignee: Jing Zhao > Fix For: Snapshot (HDFS-2802) > > Attachments: HDFS-4767.001.patch > > > 1. hadoop dfs -mkdir /user/foo/hdfs-snapshots > 2. hadoop dfsadmin -setQuota 1 /user/foo/hdfs-snapshots > 3. hadoop dfsadmin -allowSnapshot /user/foo/hdfs-snapshots > Allowing snaphot on /user/foo/hdfs-snapshots succeeded > 4. hadoop dfs -createSnapshot /user/foo/hdfs-snapshots s1 > createSnapshot: org.apache.hadoop.hdfs.protocol.NSQuotaExceededException: The > NameSpace quota (directories and files) is exceeded: quota=1 file count=2 > 5. hadoop dfsadmin -clrQuota /user/foo/hdfs-snapshots > 6. hadoop dfs -createSnapshot /user/foo/hdfs-snapshots s1 > createSnapshot: > org.apache.hadoop.hdfs.server.namenode.snapshot.SnapshotException: Directory > is not a snapshottable directory: /user/foo/hdfs-snapshots > Step 6 should have succeeded since the directory was already snapshottable(in > step 3) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira