You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "lohit vijayarenu (JIRA)" <ji...@apache.org> on 2008/04/09 00:31:24 UTC

[jira] Updated: (HADOOP-2905) fsck -move triggers NPE in namenode

     [ https://issues.apache.org/jira/browse/HADOOP-2905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

lohit vijayarenu updated HADOOP-2905:
-------------------------------------

    Attachment: HADOOP_2905.patch

DFSClient#mkdirs(String) was passing null FSPermission. Fixed it to use the correct mkdirs() which creates a default FSPermission. This fixes the call to mkdir which no longer passes null FSPermission so have not included any testcase. 

> fsck -move triggers NPE in namenode
> -----------------------------------
>
>                 Key: HADOOP-2905
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2905
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: dfs
>    Affects Versions: 0.16.0
>         Environment: hadoop-0.16 with dfs permissions disabled
>            Reporter: Michael Bieniosek
>         Attachments: HADOOP_2905.patch
>
>
> If I run hadoop fsck / -move, then the fsck fails to move any corrupt files.  In the namenode logs, I see this error message repeated 3 times:
> 2008-02-26 21:19:07,500 INFO org.apache.hadoop.ipc.Server: IPC Server handler 5 on 10000, call mkdirs(/lost+found, null) from x.x.x.135:60819: error: java.io.IOException: java.lang.NullPointerException
> java.io.IOException: java.lang.NullPointerException
>         at org.apache.hadoop.dfs.INode.setPermission(INode.java:123)
>         at org.apache.hadoop.dfs.INode.setPermissionStatus(INode.java:86)
>         at org.apache.hadoop.dfs.INode.<init>(INode.java:79)
>         at org.apache.hadoop.dfs.INodeDirectory.<init>(INode.java:319)
>         at org.apache.hadoop.dfs.FSDirectory.mkdirs(FSDirectory.java:633)
>         at org.apache.hadoop.dfs.FSNamesystem.mkdirsInternal(FSNamesystem.java:1569)
>         at org.apache.hadoop.dfs.FSNamesystem.mkdirs(FSNamesystem.java:1544)
>         at org.apache.hadoop.dfs.NameNode.mkdirs(NameNode.java:420)
>         at sun.reflect.GeneratedMethodAccessor14.invoke(Unknown Source)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
>         at java.lang.reflect.Method.invoke(Unknown Source)
>         at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:409)
>         at org.apache.hadoop.ipc.Server$Handler.run(Server.java:910)
> 2008-02-26 21:19:07,503 WARN org.apache.hadoop.dfs.NameNode: Cannot initialize /lost+found .

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.