Return-Path: X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D1C4B1010B for ; Mon, 10 Jun 2013 17:52:23 +0000 (UTC) Received: (qmail 36925 invoked by uid 500); 10 Jun 2013 17:52:23 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 36889 invoked by uid 500); 10 Jun 2013 17:52:23 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 36676 invoked by uid 99); 10 Jun 2013 17:52:23 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Jun 2013 17:52:23 +0000 Date: Mon, 10 Jun 2013 17:52:22 +0000 (UTC) From: "Daryn Sharp (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HDFS-4897) Moving/copying a directory does not include the directory's quota settings MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HDFS-4897?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D13679= 680#comment-13679680 ]=20 Daryn Sharp commented on HDFS-4897: ----------------------------------- I wouldn't expect a move to drop the quotas, but it does stand to reason th= at copy shouldn't transfer the quota - at least by default. Perhaps the = =E2=80=93p option could be extended, but one difficulty is that neither Fil= eSystem nor AbstractFileSystem expose quota operations. =20 > Moving/copying a directory does not include the directory's quota setting= s > -------------------------------------------------------------------------= - > > 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 or moved, its quotas s= ettings 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/a= tm > 100 91 none inf 7= 2 3338 /user/atm > [04:21:51] atm@simon:~/src/apache/hadoop.git$ sudo -u hdfs -E `which hado= op` fs -cp /user/atm /user/atm-copy > [04:22:00] atm@simon:~/src/apache/hadoop.git$ hadoop fs -count -q /user/a= tm-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. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrato= rs For more information on JIRA, see: http://www.atlassian.com/software/jira