[
https://issues.apache.org/jira/browse/HADOOP-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12595329#action_12595329
]
Doug Cutting commented on HADOOP-3363:
--------------------------------------
Okay, that makes sense. We should add a unit test that checks that when a
NameNode is started in a non-existant or unformatted directory that a "not
formatted" exception is thrown.
> 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
> Priority: Trivial
>
> 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.
