[
https://issues.apache.org/jira/browse/HDFS-1845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13021630#comment-13021630
]
John George commented on HDFS-1845:
-----------------------------------
[exec]
[exec] BUILD SUCCESSFUL
[exec] Total time: 49 seconds
[exec]
[exec]
[exec]
[exec]
[exec] -1 overall.
[exec]
[exec] +1 @author. The patch does not contain any @author tags.
[exec]
[exec] +1 tests included. The patch appears to include 3 new or
modified tests.
[exec]
[exec] +1 javadoc. The javadoc tool did not generate any warning
messages.
[exec]
[exec] +1 javac. The applied patch does not increase the total number
of javac compiler warnings.
[exec]
[exec] +1 findbugs. The patch does not introduce any new Findbugs
(version 1.3.9) warnings.
[exec]
[exec] -1 release audit. The applied patch generated 1 release audit
warnings (more than the trunk's current 0 warnings).
[exec]
[exec] +1 system test framework. The patch passed system test
framework compile.
[exec]
[exec]
[exec]
The release audit was failing even with an empty patch. So, I dont think it is
this patch that caused it.
> symlink comes up as directory after namenode restart
> ----------------------------------------------------
>
> Key: HDFS-1845
> URL: https://issues.apache.org/jira/browse/HDFS-1845
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 0.22.0
> Reporter: John George
> Assignee: John George
> Fix For: 0.22.0
>
> Attachments: HDFS-1845-apache.patch
>
>
> When a symlink is first created, it get added to EditLogs. When namenode is
> restarted, it reads from this editlog and represents a symlink correctly and
> saves this information to its image. If the namenode is restarted again, it
> reads its from this FSImage, but thinks that a symlink is a directory. This
> is because it uses "Block[] blocks" to determine if an INode is a directory,
> a file, or symlink. Since both a directory and a symlink has blocks as null,
> it thinks that a symlink is a directory.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
