Uploaded image for project: 'Lustre'
  1. Lustre
  2. LU-15383

DNE directories not connected to REMOTE_PARENT_DIR

Details

    • Bug
    • Resolution: Unresolved
    • Critical
    • None
    • None
    • None
    • 3
    • 9223372036854775807

    Description

      Running e2fsck on an MDT with a large number of striped directories shows a large number of disconnected directory entries. On several different systems this is showing a large number of errors during e2fsck, resulting in tens or hundreds of thousands of entries that need to be connected to list+found:

      Unconnected directory inode 2102494 (/REMOTE_PARENT_DIR/???)
Connect to /lost+found? yes
Unconnected directory inode 2102510 (/REMOTE_PARENT_DIR/???)
Connect to /lost+found? yes
Unconnected directory inode 2102514 (/REMOTE_PARENT_DIR/???)
Connect to /lost+found? yes

      This doesn't appear to be caused by filesystem errors, as it has been seen repeatedly, so it is more likely to be a bug in the code (eg. rename doesn't connect striped directories properly, maybe if the rename source was on a remote MDT and the target is on the local MDT, or the reverse, or during "lfs migrate -m" or similar.

      Attachments

        Issue Links

          Clones

          Bug - A problem which impairs or prevents the functions of the product. LU-15330 ext2fs_get_pathname() very slow for large directory

          • Major - Major loss of function.
          • Open
          is related to

          Bug - A problem which impairs or prevents the functions of the product. LU-4876 LFSCK remove entry from /REMOTE_PARENT_DIR if MDT-object name reside on the same MDT after migration

          • Major - Major loss of function.
          • Open
          is related to

          Bug - A problem which impairs or prevents the functions of the product. LU-15388 Wrong dotdot FID parameter for osd_add_dot_dotdot()

          • Major - Major loss of function.
          • Resolved

          Improvement - An improvement or enhancement to an existing feature or task. LU-10329 DNE3: REMOTE_PARENT_DIR scalability

          • Critical - Crashes, loss of data, severe memory leak.
          • Open

          Activity

            [LU-15383] DNE directories not connected to REMOTE_PARENT_DIR
            adilger Andreas Dilger added a comment - - edited

            This might be related to LU-15388, since REMOTE_PARENT_DIR entries have the wrong ".." entry, so updates to that directory will be incorrect.

            adilger Andreas Dilger added a comment - - edited This might be related to LU-15388 , since REMOTE_PARENT_DIR entries have the wrong " .. " entry, so updates to that directory will be incorrect.
            laisiyao Lai Siyao added a comment -

            The test result shows this only happens in sanity 300p, which tests striped directory with -ENOSPC.

            laisiyao Lai Siyao added a comment - The test result shows this only happens in sanity 300p, which tests striped directory with -ENOSPC.
            gerrit Gerrit Updater added a comment -

            "Lai Siyao <lai.siyao@whamcloud.com>" uploaded a new patch: https://review.whamcloud.com/45961
            Subject: LU-15383 osd-ldiskfs: check .. upon object destroy
            Project: fs/lustre-release
            Branch: master
            Current Patch Set: 1
            Commit: aacc3718e81314c4157874dfbf438a8b696bbf56

            gerrit Gerrit Updater added a comment - "Lai Siyao <lai.siyao@whamcloud.com>" uploaded a new patch: https://review.whamcloud.com/45961 Subject: LU-15383 osd-ldiskfs: check .. upon object destroy Project: fs/lustre-release Branch: master Current Patch Set: 1 Commit: aacc3718e81314c4157874dfbf438a8b696bbf56
            adilger Andreas Dilger added a comment -

            I don't know if that will help. The ".." FID is not checked by e2fsck, so there must still be some other inconsistency at the ldiskfs level that is causing e2fsck to report a problem.

            adilger Andreas Dilger added a comment - I don't know if that will help. The " .. " FID is not checked by e2fsck, so there must still be some other inconsistency at the ldiskfs level that is causing e2fsck to report a problem.
            laisiyao Lai Siyao added a comment - - edited

            It looks LU-15388 explained this, and the patch there can fix this issue.

            laisiyao Lai Siyao added a comment - - edited It looks LU-15388 explained this, and the patch there can fix this issue.

            People

              laisiyao Lai Siyao
              adilger Andreas Dilger
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated: