Mailing-List: contact core-user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-user@hadoop.apache.org
Received-SPF: pass (athena.apache.org: domain of fossist@gmail.com designates
 209.85.221.110 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=nl2o57XyuTEHAl61B19aMMxafmMurbS4rlQUGOCbX3o/MUhRyCJodJAbLO6oa1pQVJ
         VhRr+o9k0UcYarye0SzSggR4mUkPqmzGDrbRB5k72mGFOLOd26ND2AZDpB/2Cv0d0+1y
         6zCByEoNW+Lt/xBV9dk5HBpdN3q1wN5DahEi8=
MIME-Version: 1.0
In-Reply-To: <45f85f70905061214t6eaa54dfl47a7d7bdb0c9a24d@mail.gmail.com>
References: <3f8297b20905061140o49941e35jd9462168c29aad49@mail.gmail.com>
	 <45f85f70905061214t6eaa54dfl47a7d7bdb0c9a24d@mail.gmail.com>
Date: Thu, 7 May 2009 00:56:10 +0530
Message-ID: <3f8297b20905061226o37bf904dr98b68737f292b66a@mail.gmail.com>
Subject: Re: Folders and files still present after format
From: Foss User <fossist@gmail.com>
To: core-user@hadoop.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

On Thu, May 7, 2009 at 12:44 AM, Todd Lipcon <todd@cloudera.com> wrote:
> On Wed, May 6, 2009 at 11:40 AM, Foss User <fossist@gmail.com> wrote:
>
>> Today I formatted the namenode while the namenode and jobtracker was
>> up. I found that I was still able to browse the file system using the
>> command: bin/hadoop dfs -lsr /
>>
>> Then, I stopped the namenode and jobtracker and did a format again. I
>> started the namenode and jobtracker. I could still browse the file
>> system. Is this an expected behavior or a problem?
>>
>> I was formatting using the command: bin/hadoop namenode -format
>>
>> I was running this command on the namenode machine.
>>
>
> Were you running the format command as the same user that runs the namenode?
> With a default configuration, the dfs.name.dir has the user name included in
> it, so running that command as your user account won't affect the cluster if
> the cluster namenode is running as a "hadoop" account, for example.
>
> -Todd
>

Yes, as far as I remember but I am not absolutely sure. From your
reply, I understand what I experienced (may be due to my fault) is not
an expected behavior. So, if I face the same error again I would like
to provide more information to this list. What are the logs that I
should be uploading here for analysis if I see this again?