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