InitialSyncFileMover must handle symlinks at top level of destination directory

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 5.2.0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • Replication 2021-11-15
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently, InitialSyncFileMover assumes all existing files are regular files or directories; if one is a symlink we get an invariant. We sometimes create a symlink to put the WiredTiger journal files on another device. This means we must support some of the files to delete containing a symlink at the top level of their path. We must preserve that symlink, so files with the same relative path from the sync source go into the symlink destination directory.

            Assignee:
            Matthew Russotto (Inactive)
            Reporter:
            Matthew Russotto (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: