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 C23B910E58 for ; Fri, 17 Apr 2015 11:36:05 +0000 (UTC) Received: (qmail 58939 invoked by uid 500); 17 Apr 2015 11:36:00 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 58896 invoked by uid 500); 17 Apr 2015 11:36:00 -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 58875 invoked by uid 99); 17 Apr 2015 11:36:00 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Apr 2015 11:36:00 +0000 Date: Fri, 17 Apr 2015 11:36:00 +0000 (UTC) From: "Hudson (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HDFS-8153) Error Message points to wrong parent directory in case of path component name length error MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HDFS-8153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14499681#comment-14499681 ] Hudson commented on HDFS-8153: ------------------------------ FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #157 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk-Java8/157/]) HDFS-8153. Error Message points to wrong parent directory in case of path component name length error. Contributed by Anu Engineer. (jitendra: rev 369ddc67bdaf61cca3f2f766ab504e2932f6fb72) * hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt * hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestFsLimits.java * hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSDirectory.java > Error Message points to wrong parent directory in case of path component name length error > ------------------------------------------------------------------------------------------ > > Key: HDFS-8153 > URL: https://issues.apache.org/jira/browse/HDFS-8153 > Project: Hadoop HDFS > Issue Type: Bug > Components: namenode > Affects Versions: 2.5.2 > Reporter: Anu Engineer > Assignee: Anu Engineer > Fix For: 2.7.1 > > Attachments: hdfs-8153.001.patch > > > If the name component length is greater than the permitted length, the error message points to wrong parent directory for mkdir and touchz. > Here are examples where the parent directory name is in error message. In this example dfs.namenode.fs-limits.max-component-length is set to 19. > {code} > hdfs dfs -mkdir /user/hrt_qa/FileNameLength/really_big_name_dir01 > mkdir: The maximum path component name limit of really_big_name_dir01 in directory /user/hrt_qa/ is exceeded: limit=19 length=21 > {code} > The expected value for the directory was _/user/hrt_qa/FileNameLength_. The same behavior is observed for touchz > {code} > hdfs dfs -touchz /user/hrt_qa/FileNameLength/really_big_name_0004 > touchz: The maximum path component name limit of really_big_name_0004 in directory /user/hrt_qa/ is exceeded: limit=19 length=20 > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)