Return-Path: X-Original-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 543DA106E7 for ; Wed, 26 Mar 2014 05:58:41 +0000 (UTC) Received: (qmail 23460 invoked by uid 500); 26 Mar 2014 05:58:33 -0000 Delivered-To: apmail-hadoop-hdfs-user-archive@hadoop.apache.org Received: (qmail 23080 invoked by uid 500); 26 Mar 2014 05:58:33 -0000 Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hadoop.apache.org Delivered-To: mailing list user@hadoop.apache.org Received: (qmail 23070 invoked by uid 99); 26 Mar 2014 05:58:32 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Mar 2014 05:58:32 +0000 X-ASF-Spam-Status: No, hits=2.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_REPLY,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of ung3210@gmail.com designates 209.85.160.42 as permitted sender) Received: from [209.85.160.42] (HELO mail-pb0-f42.google.com) (209.85.160.42) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Mar 2014 05:58:28 +0000 Received: by mail-pb0-f42.google.com with SMTP id rr13so1476401pbb.29 for ; Tue, 25 Mar 2014 22:58:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=YuI9KackcUaL10Nc98HjEq5d9k4PXN+mTGGFoD0kDkk=; b=eIQFO05clRhDsQBeYEhbixvDTrLhiCuAywhQllpRVed8TyUfgB2+VA69ZD5JFpQUxJ l1CFRFnN8G58AWJHDZdai/LGvXEbddzcLJ2CkdtENkKuoya0Q4tsZsaLRtACVGkq+PP7 xYin2wmAQpffV9s8q6jRY9OQVYcyGVHEfS+UZFVbLEySOMIjT0lzMyS8ZMe0Pu/foall x6GzgpXauLfTHLeTYew2G4dA/IWa15l+wAjK3o7cJqDKy1gsfJDnxqigf2yq21+Gv/bR L7mUBDaiMNWi5FKj784TQbhIgh0EJUxwwP4H/SSecqDw0fSXcBieAaeLd95NgdOQMR/r tu7g== MIME-Version: 1.0 X-Received: by 10.67.22.100 with SMTP id hr4mr2320121pad.112.1395813488415; Tue, 25 Mar 2014 22:58:08 -0700 (PDT) Received: by 10.68.59.162 with HTTP; Tue, 25 Mar 2014 22:58:08 -0700 (PDT) In-Reply-To: <8AD4EE147886274A8B495D6AF407DF694B1E723D@szxeml510-mbx.china.huawei.com> References: <8AD4EE147886274A8B495D6AF407DF694B1E712B@szxeml510-mbx.china.huawei.com> <8AD4EE147886274A8B495D6AF407DF694B1E723D@szxeml510-mbx.china.huawei.com> Date: Wed, 26 Mar 2014 13:58:08 +0800 Message-ID: Subject: Re: namenode could not start From: haihong lu To: user Content-Type: multipart/alternative; boundary=047d7b5dadd026599904f57c27d0 X-Virus-Checked: Checked by ClamAV on apache.org --047d7b5dadd026599904f57c27d0 Content-Type: text/plain; charset=ISO-8859-1 Yes.But the issue has been fixed, thanks for help. in myscript, i used "hdfs namenode -format" instead of "hdfs namenode format" On Wed, Mar 26, 2014 at 12:33 PM, Brahma Reddy Battula < brahmareddy.battula@huawei.com> wrote: > are you getting same exception..? If do format and then start-dfs.sh.. > > > > are you using the same config..? I mean, while formatting the namenodeand while starting.. > > > > can you please check or paste the configurations,exceptions in namenodelog and format log.. > > > > and hope you are formatting and starting with same user.. > > > > > > > > > > Thanks & Regards > > > > Brahma Reddy Battula > > > ------------------------------ > *From:* haihong lu [ung3210@gmail.com] > *Sent:* Wednesday, March 26, 2014 7:04 AM > *To:* user > > *Subject:* Re: namenode could not start > > /home/hadoop/mydata/hdfs/namenode should be created when executed > start-dfs.sh. i had formatted namenode before doing start-dfs.sh, but no > effect. > > > On Tue, Mar 25, 2014 at 6:39 PM, Brahma Reddy Battula < > brahmareddy.battula@huawei.com> wrote: > >> Please format the namenode and then do start-dfs.. >> >> >> >> >> >> *Command for namenode format:* >> >> >> >> hdfs namenode -format >> >> >> >> >> >> >> >> Thanks & Regards >> >> >> >> Brahma Reddy Battula >> >> >> ------------------------------ >> *From:* Azuryy Yu [azuryyyu@gmail.com] >> *Sent:* Tuesday, March 25, 2014 2:39 PM >> *To:* user@hadoop.apache.org >> *Subject:* Re: namenode could not start >> >> Are you sure /home/hadoop/mydata/hdfs/namenode exists and has a >> right permission? >> >> >> On Tue, Mar 25, 2014 at 4:51 PM, haihong lu wrote: >> >>> Dear all: >>> >>> I had a problem that the namenode could not start when i ran >>> start-dfs.sh . Show the message as below: >>> >>> FATAL org.apache.hadoop.hdfs.server.namenode.NameNode: Exception in >>> namenode join >>> org.apache.hadoop.hdfs.server.common.InconsistentFSStateException: >>> Directory /home/hadoop/mydata/hdfs/namenode is in an inconsistent state: >>> storage directory does not exist or is not accessible. >>> at >>> org.apache.hadoop.hdfs.server.namenode.FSImage.recoverStorageDirs(FSImage.java:292) >>> at >>> org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:200) >>> at >>> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFSImage(FSNamesystem.java:787) >>> at >>> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:568) >>> at >>> org.apache.hadoop.hdfs.server.namenode.NameNode.loadNamesystem(NameNode.java:443) >>> at >>> org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:491) >>> at >>> org.apache.hadoop.hdfs.server.namenode.NameNode.(NameNode.java:684) >>> at >>> org.apache.hadoop.hdfs.server.namenode.NameNode.(NameNode.java:669) >>> at >>> org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1254) >>> at >>> org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1320) >>> >>> Thank for any help >>> >>> >> > --047d7b5dadd026599904f57c27d0 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Yes.But the issue has been fixed, thanks for help.
in myscript, i used "hdfs namenode -format" instead of= "hdfs namenode format"

<= br>
On Wed, Mar 26, 2014 at 12:33 PM, Brahma Reddy B= attula <brahmareddy.battula@huawei.com> wrote:<= br>

are you getting same exception..? If do format and then start-dfs.sh<= /a>..

=A0

are you using the same config..? I mean, while formatting the=A0n= amenode and while starting..

=A0

can you please check or paste the=A0configurations,exceptions in= =A0namenode log and format log..

=A0

and hope you are formatting and starting with same user..

=A0

=A0

=A0

=A0

Thanks & Regards

=A0

Brahma Reddy Battula

=A0

Fro= m: haihong lu [u= ng3210@gmail.com]
Sent: Wednesday, March 26, 2014 7:04 AM
To: user

Subject: Re: namenode could not start

=A0=A0/home/hadoop/mydata/hdfs/namenode should be created when executed start-dfs= .sh. i had formatted namenode before doing start-dfs.sh, but no effect.


On Tue, Mar 25, 2014 at 6:39 PM, Brahma Reddy Ba= ttula <bra= hmareddy.battula@huawei.com> wrote:

Please format the=A0namenode and then do start-dfs..

=A0

=A0

Command for=A0namenode format:

=A0

hdfs=A0namenode -format

=A0

=A0

=A0

Thanks & Regards

=A0

Brahma Reddy Battula

=A0

Fro= m: Azuryy Yu [a= zuryyyu@gmail.com]
Sent: Tuesday, March 25, 2014 2:39 PM
To: user= @hadoop.apache.org
Subject: Re: namenode could not start

Are you sure=A0=A0/home/hadoop/mydata/hdfs/namenode exists and has a right permis= sion?


On Tue, Mar 25, 2014 at 4:51 PM, haihong lu <ung3210@gmail.co= m> wrote:
Dear all:

I had a problem that the namenode could not start when i ran start-dfs.sh .= Show the message as below:

FATAL org.apache.hadoop.hdfs.server.namenode.NameNode: Exception in namenod= e join
org.apache.hadoop.hdfs.server.common.InconsistentFSStateException: Director= y /home/hadoop/mydata/hdfs/namenode is in an inconsistent state: storage di= rectory does not exist or is not accessible.
=A0=A0=A0=A0=A0=A0=A0 at org.apache.hadoop.hdfs.server.namenode.FSImage.rec= overStorageDirs(FSImage.java:292)
=A0=A0=A0=A0=A0=A0=A0 at org.apache.hadoop.hdfs.server.namenode.FSImage.rec= overTransitionRead(FSImage.java:200)
=A0=A0=A0=A0=A0=A0=A0 at org.apache.hadoop.hdfs.server.namenode.FSNamesyste= m.loadFSImage(FSNamesystem.java:787)
=A0=A0=A0=A0=A0=A0=A0 at org.apache.hadoop.hdfs.server.namenode.FSNamesyste= m.loadFromDisk(FSNamesystem.java:568)
=A0=A0=A0=A0=A0=A0=A0 at org.apache.hadoop.hdfs.server.namenode.NameNode.lo= adNamesystem(NameNode.java:443)
=A0=A0=A0=A0=A0=A0=A0 at org.apache.hadoop.hdfs.server.namenode.NameNode.in= itialize(NameNode.java:491)
=A0=A0=A0=A0=A0=A0=A0 at org.apache.hadoop.hdfs.server.namenode.NameNode.&l= t;init>(NameNode.java:684)
=A0=A0=A0=A0=A0=A0=A0 at org.apache.hadoop.hdfs.server.namenode.NameNode.&l= t;init>(NameNode.java:669)
=A0=A0=A0=A0=A0=A0=A0 at org.apache.hadoop.hdfs.server.namenode.NameNode.cr= eateNameNode(NameNode.java:1254)
=A0=A0=A0=A0=A0=A0=A0 at org.apache.hadoop.hdfs.server.namenode.NameNode.ma= in(NameNode.java:1320)

Thank for any help




--047d7b5dadd026599904f57c27d0--