Mailing-List: contact hdfs-user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-user@hadoop.apache.org
Received-SPF: pass (athena.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=mlogiciels.com; h=content-type
	:mime-version:subject:from:in-reply-to:date
	:content-transfer-encoding:message-id:references:to; q=dns; s=
	mlogiciels.com; b=QI6LkHegEwfE6XDvWkEsUn6sZ8HxSjpwtpyWvtPfvBn2Rt
	1VS2vPZkIKzSd6cILmQZraMYRfBY7DZ2uoRV7yS+zA8QlOcbzHykyIRX8yupc76k
	KRowdDXk9mIt0V8b5Mcr4e83lrPG9/j3FIJTxqn5QG68w4KlA7Okn+botblh8=
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1081)
Subject: Re: NameNode crash - cannot start dfs - need help
From: Matthew LeMieux <mdl@mlogiciels.com>
In-Reply-To: <78495444-4EC2-49B0-AC9F-C6C0258BD64C@linkedin.com>
Date: Tue, 5 Oct 2010 10:14:21 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <97C05097-71C6-4552-B3A2-C3AD366B9F29@mlogiciels.com>
References: <BCCFEB17-8464-466B-BD54-125764974AD5@mlogiciels.com>
 <78495444-4EC2-49B0-AC9F-C6C0258BD64C@linkedin.com>
To: hdfs-user@hadoop.apache.org

No second copy.  There will be from now on, but that doesn't get me out =
of the current hole.=20

I'm not too concerned with recent edits.  I'd be much happier losing =
recent edits if I could just get the thing to start!

So, the question is, how do I tell the name node to just start up no =
matter what?

-Matthew

On Oct 5, 2010, at 9:10 AM, Allen Wittenauer wrote:

>=20
> On Oct 5, 2010, at 8:16 AM, Matthew LeMieux wrote:
>=20
>> The namenode on an otherwise very stable HDFS cluster crashed =
recently.  The filesystem filled up on the name node, which I assume is =
what caused the crash.    The problem has been fixed, but I cannot get =
the namenode to restart.  I am using version CDH3b2  =
(hadoop-0.20.2+320).=20
>=20
>=20
> No 2nd copy of the edits file/another entry in dfs.name.dir?
>=20
>=20