Return-Path: Delivered-To: apmail-hadoop-core-dev-archive@www.apache.org Received: (qmail 39274 invoked from network); 4 Jun 2009 22:59:21 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 4 Jun 2009 22:59:21 -0000 Received: (qmail 68066 invoked by uid 500); 4 Jun 2009 22:59:32 -0000 Delivered-To: apmail-hadoop-core-dev-archive@hadoop.apache.org Received: (qmail 67984 invoked by uid 500); 4 Jun 2009 22:59:32 -0000 Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: core-dev@hadoop.apache.org Delivered-To: mailing list core-dev@hadoop.apache.org Received: (qmail 67964 invoked by uid 99); 4 Jun 2009 22:59:32 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Jun 2009 22:59:32 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Jun 2009 22:59:28 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 9C7B9234C004 for ; Thu, 4 Jun 2009 15:59:07 -0700 (PDT) Message-ID: <1162475448.1244156347636.JavaMail.jira@brutus> Date: Thu, 4 Jun 2009 15:59:07 -0700 (PDT) From: "Hadoop QA (JIRA)" To: core-dev@hadoop.apache.org Subject: [jira] Commented: (HADOOP-5862) Namespace quota exceeded message unclear In-Reply-To: <727332119.1242620865536.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HADOOP-5862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12716448#action_12716448 ] Hadoop QA commented on HADOOP-5862: ----------------------------------- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12409707/HADOOP-5862.patch against trunk revision 781816. +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 13 new or modified tests. -1 patch. The patch command could not apply the patch. Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/463/console This message is automatically generated. > Namespace quota exceeded message unclear > ---------------------------------------- > > Key: HADOOP-5862 > URL: https://issues.apache.org/jira/browse/HADOOP-5862 > Project: Hadoop Core > Issue Type: Bug > Components: dfs > Affects Versions: 0.18.0 > Reporter: eric baldeschwieler > Assignee: Boris Shkolnik > Fix For: 0.20.1 > > Attachments: HADOOP-5862.patch, HADOOP-5862.patch, HADOOP-5862.patch > > > We seem to return one generic message when either a namespace or diskspace quota is exceeded. We should be clearer. The error should state which quota is exceeded and only report statistics on the exceeded quota. > Further namespace quota is probably not clear to most users. We should probably have explanatory text such as: "you have exceeded the maximum allowed number of files". Maybe we should even rename the quota to number of files quota? > Finally, the error below would be clearer if it read: > Quota exceeded for directory '/user/ciyaliao'. > By not using the word "directory" it is not clear in this case if the issue is with a user or a directory. > ------ AN EXAMPLE ----- > > Hi, > > > > I encountered an error: > > > > put: org.apache.hadoop.hdfs.protocol.QuotaExceededException: The quota of > > /user/x is exceeded: namespace quota=200000 file count=200001, > > diskspace quota=-1 diskspace=-44221467605496 > > > > It apparently complains that dfs quota is exceeded. But I only use around > > 200GB disk space. From the error message, what kind of quota did I actually > > exceed? How do I check my usage of this type of quota? > > > > Thanks, > > x -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.