[
https://issues.apache.org/jira/browse/HADOOP-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Shvachko updated HADOOP-3363:
----------------------------------------
Attachment: NotFormatted.patch
Yes the message is confusing. It should just say the name-node is not formatted.
The problem here is that FSImage demands the old image directory to exist even
if the storage directory is not formatted.
This patch fixes the problem.
I also add verification that the message contains words "not formatted" in the
exception thrown in the appropriate case.
HADOOP-2797 removed everything related to the pre-crc versions, and now we do
not need to support pre-upgrade
versions and therefore don't need to check for conversions. I'll file a jira to
remove this code.
> HDFS throws a InconsistentFSStateException when the name node starts up on a
> directory that isnt formatted
> ----------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-3363
> URL: https://issues.apache.org/jira/browse/HADOOP-3363
> Project: Hadoop Core
> Issue Type: Bug
> Affects Versions: 0.16.3
> Environment: namenode deployed on java1.6/ubuntu8.04 in a SmartFrog
> managed JVM
> Reporter: Steve Loughran
> Assignee: Konstantin Shvachko
> Priority: Blocker
> Fix For: 0.18.0
>
> Attachments: NotFormatted.patch
>
>
> I deploy a namenode with directories that exist but are empty, an
> InconsistentFSStateException is thrown instead of the FS entering the
> unformatted state -the check for upgrade state fails when there is no file
> system there at all.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
