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

DNE directories not connected to REMOTE_PARENT_DIR

XMLWordPrintable

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

      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.

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

              Created:
              Updated: