Uploaded image for project: 'Hadoop HDFS'
  1. Hadoop HDFS
  2. HDFS-1845

symlink comes up as directory after namenode restart

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 0.22.0, 0.23.0
    • Fix Version/s: 0.22.0, 0.23.0
    • Component/s: None
    • Labels:
      None
    • Hadoop Flags:
      Reviewed

      Description

      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.

        Attachments

        1. HDFS-1845-apache.patch
          4 kB
          John George
        2. HDFS-1845-apache-2.patch
          4 kB
          John George
        3. HDFS-1845-apache-3.patch
          3 kB
          John George
        4. hdfs-1845-branch22-1.patch
          6 kB
          Eli Collins
        5. HDFS-1845-2.patch
          4 kB
          John George

          Activity

            People

            • Assignee:
              johnvijoe John George
              Reporter:
              johnvijoe John George
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: