[ https://issues.apache.org/jira/browse/HDFS-1845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John George updated HDFS-1845: ------------------------------ Attachment: HDFS-1845-2.patch Attaching Yahoo! specific patch for the bug. $ ant test-core -Dtestcase=TestCheckpoint .. .. checkfailure: BUILD SUCCESSFUL Total time: 37 seconds > 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, 0.23.0 > Reporter: John George > Assignee: John George > Fix For: 0.22.0, 0.23.0 > > Attachments: HDFS-1845-2.patch, HDFS-1845-apache-2.patch, > HDFS-1845-apache-3.patch, HDFS-1845-apache.patch, hdfs-1845-branch22-1.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