[ 
https://issues.apache.org/jira/browse/HADOOP-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12595052#action_12595052
 ] 

Steve Loughran commented on HADOOP-3363:
----------------------------------------

stack trace. The two classes at the root are mine

Caused by: org.apache.hadoop.dfs.InconsistentFSStateException: Directory 
/tmp/tempdir22787 is in an inconsistent state: /tmp/tempdir22787/image does not 
exist.
at org.apache.hadoop.dfs.FSImage.isConversionNeeded(FSImage.java:480)
at 
org.apache.hadoop.dfs.Storage$StorageDirectory.analyzeStorage(Storage.java:283)
at org.apache.hadoop.dfs.FSImage.recoverTransitionRead(FSImage.java:148)
at org.apache.hadoop.dfs.FSDirectory.loadFSImage(FSDirectory.java:79)
at org.apache.hadoop.dfs.FSNamesystem.initialize(FSNamesystem.java:254)
at org.apache.hadoop.dfs.FSNamesystem.(FSNamesystem.java:235)
at org.apache.hadoop.dfs.NameNode.initialize(NameNode.java:131)
at org.apache.hadoop.dfs.NameNode.(NameNode.java:176)
at org.apache.hadoop.dfs.NameNode.(NameNode.java:162)
at org.apache.hadoop.dfs.ExtNameNode.(ExtNameNode.java:61)
at org.apache.hadoop.dfs.ExtNameNode.createNameNode(ExtNameNode.java:44)
at 
org.smartfrog.services.hadoop.components.namenode.NamenodeImpl.sfStart(NamenodeImpl.java:73)

> 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.

Reply via email to