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

Search Discussions

  • Steve Loughran (JIRA) at May 7, 2008 at 9:46 pm
    [ 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.
  • Doug Cutting (JIRA) at May 7, 2008 at 11:12 pm
    [ https://issues.apache.org/jira/browse/HADOOP-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12595083#action_12595083 ]

    Doug Cutting commented on HADOOP-3363:
    --------------------------------------

    I'm not sure what you expect here. The filesystem has not yet been formatted, right? If so, attempting to start a namenode should fail--we don't auto-format filesystems. Are you proposing that the exception should be clearer?
    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.
  • Steve Loughran (JIRA) at May 8, 2008 at 10:03 am
    [ https://issues.apache.org/jira/browse/HADOOP-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12595180#action_12595180 ]

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

    I certainly expect the operation to fail, but it shouldnt be with a 'you havent upgraded' message.

    Looking at the code in analyzeStorage(), there is a check for an unformatted filesystem later, which then returns a StorageState.NOT_FORMATTED response to FSImage.recoverTransitionRead(), which then chooses its actions based on filesystem state. Only it isnt getting a chance to apply its policy when not formatted, because the exception is being thrown and forcing it off on a different path.
    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.
  • Doug Cutting (JIRA) at May 8, 2008 at 4:41 pm
    [ 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.
  • Robert Chansler (JIRA) at Jun 9, 2008 at 5:30 pm
    [ https://issues.apache.org/jira/browse/HADOOP-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

    Robert Chansler updated HADOOP-3363:
    ------------------------------------

    Priority: Blocker (was: Trivial)
    Fix Version/s: 0.18.0
    Assignee: Konstantin Shvachko
    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


    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.
  • Konstantin Shvachko (JIRA) at Jun 12, 2008 at 2:03 am
    [ 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.
  • Konstantin Shvachko (JIRA) at Jun 12, 2008 at 2:05 am
    [ https://issues.apache.org/jira/browse/HADOOP-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

    Konstantin Shvachko updated HADOOP-3363:
    ----------------------------------------

    Status: Patch Available (was: Open)
    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.
  • Hadoop QA (JIRA) at Jun 12, 2008 at 7:52 am
    [ https://issues.apache.org/jira/browse/HADOOP-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12604438#action_12604438 ]

    Hadoop QA commented on HADOOP-3363:
    -----------------------------------

    +1 overall. Here are the results of testing the latest attachment
    http://issues.apache.org/jira/secure/attachment/12383886/NotFormatted.patch
    against trunk revision 666620.

    +1 @author. The patch does not contain any @author tags.

    +1 tests included. The patch appears to include 3 new or modified tests.

    +1 javadoc. The javadoc tool did not generate any warning messages.

    +1 javac. The applied patch does not increase the total number of javac compiler warnings.

    +1 findbugs. The patch does not introduce any new Findbugs warnings.

    +1 release audit. The applied patch does not increase the total number of release audit warnings.

    +1 core tests. The patch passed core unit tests.

    +1 contrib tests. The patch passed contrib unit tests.

    Test results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2647/testReport/
    Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2647/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
    Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2647/artifact/trunk/build/test/checkstyle-errors.html
    Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2647/console

    This message is automatically generated.
    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.
  • Lohit Vijayarenu (JIRA) at Jun 13, 2008 at 8:58 pm
    [ https://issues.apache.org/jira/browse/HADOOP-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

    Lohit Vijayarenu updated HADOOP-3363:
    -------------------------------------

    Hadoop Flags: [Reviewed]

    +1 Looks good
    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.
  • Konstantin Shvachko (JIRA) at Jun 16, 2008 at 7:16 pm
    [ https://issues.apache.org/jira/browse/HADOOP-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

    Konstantin Shvachko updated HADOOP-3363:
    ----------------------------------------

    Resolution: Fixed
    Status: Resolved (was: Patch Available)

    I just committed this.
    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.
  • Hudson (JIRA) at Jun 16, 2008 at 10:40 pm
    [ https://issues.apache.org/jira/browse/HADOOP-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12605430#action_12605430 ]

    Hudson commented on HADOOP-3363:
    --------------------------------

    Integrated in Hadoop-trunk #520 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-trunk/520/])
    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.

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupcommon-dev @
categorieshadoop
postedMay 7, '08 at 9:44p
activeJun 16, '08 at 10:40p
posts12
users1
websitehadoop.apache.org...
irc#hadoop

1 user in discussion

Hudson (JIRA): 12 posts

People

Translate

site design / logo © 2022 Grokbase