You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Stephen Chu (JIRA)" <ji...@apache.org> on 2013/06/10 20:00:24 UTC
[jira] [Updated] (HDFS-4897) Copying a directory does not include
the directory's quota settings
[ https://issues.apache.org/jira/browse/HDFS-4897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephen Chu updated HDFS-4897:
------------------------------
Description:
[~atm] and I found that when a directory is copied, its quotas settings aren't included.
{code}
[04:21:33] atm@simon:~/src/apache/hadoop.git$ hadoop fs -ls /user
Found 2 items
drwxr-xr-x - atm atm 0 2013-06-07 16:17 /user/atm
drwx------ - hdfs supergroup 0 2013-06-07 16:21 /user/hdfs
[04:21:44] atm@simon:~/src/apache/hadoop.git$ hadoop fs -count -q /user/atm
100 91 none inf 7 2 3338 /user/atm
[04:21:51] atm@simon:~/src/apache/hadoop.git$ sudo -u hdfs -E `which hadoop` fs -cp /user/atm /user/atm-copy
[04:22:00] atm@simon:~/src/apache/hadoop.git$ hadoop fs -count -q /user/atm-copy
none inf none inf 6 1 3338 /user/atm-copy
{code}
This also means that a user will not retain quotas settings when the user takes snapshots and restores a subtree using snapshots because we use copy (not allowed to move snapshots).
was:
[~atm] and I found that when a directory is copied or moved, its quotas settings aren't included.
{code}
[04:21:33] atm@simon:~/src/apache/hadoop.git$ hadoop fs -ls /user
Found 2 items
drwxr-xr-x - atm atm 0 2013-06-07 16:17 /user/atm
drwx------ - hdfs supergroup 0 2013-06-07 16:21 /user/hdfs
[04:21:44] atm@simon:~/src/apache/hadoop.git$ hadoop fs -count -q /user/atm
100 91 none inf 7 2 3338 /user/atm
[04:21:51] atm@simon:~/src/apache/hadoop.git$ sudo -u hdfs -E `which hadoop` fs -cp /user/atm /user/atm-copy
[04:22:00] atm@simon:~/src/apache/hadoop.git$ hadoop fs -count -q /user/atm-copy
none inf none inf 6 1 3338 /user/atm-copy
{code}
This also means that a user will not retain quotas settings when the user takes snapshots and backs up a subtree using snapshots.
Summary: Copying a directory does not include the directory's quota settings (was: Moving/copying a directory does not include the directory's quota settings)
Sorry, I made a mistake in the initial filing. _hdfs dfs -mv_ will retain the quotas settings, but not _-cp_. This still means that when we want to restore a subtree using snapshots, we won't be able to retain quotas settings because we can't use move.
> Copying a directory does not include the directory's quota settings
> -------------------------------------------------------------------
>
> Key: HDFS-4897
> URL: https://issues.apache.org/jira/browse/HDFS-4897
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 3.0.0
> Reporter: Stephen Chu
> Labels: quota
>
> [~atm] and I found that when a directory is copied, its quotas settings aren't included.
> {code}
> [04:21:33] atm@simon:~/src/apache/hadoop.git$ hadoop fs -ls /user
> Found 2 items
> drwxr-xr-x - atm atm 0 2013-06-07 16:17 /user/atm
> drwx------ - hdfs supergroup 0 2013-06-07 16:21 /user/hdfs
> [04:21:44] atm@simon:~/src/apache/hadoop.git$ hadoop fs -count -q /user/atm
> 100 91 none inf 7 2 3338 /user/atm
> [04:21:51] atm@simon:~/src/apache/hadoop.git$ sudo -u hdfs -E `which hadoop` fs -cp /user/atm /user/atm-copy
> [04:22:00] atm@simon:~/src/apache/hadoop.git$ hadoop fs -count -q /user/atm-copy
> none inf none inf 6 1 3338 /user/atm-copy
> {code}
> This also means that a user will not retain quotas settings when the user takes snapshots and restores a subtree using snapshots because we use copy (not allowed to move snapshots).
--
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