Skip to content

TarWriter on Windows Server treats File Deduplication reparse point flag as symbolic links #82949

@billfreist

Description

@billfreist

if ((attributes & FileAttributes.ReparsePoint) != 0)

As seen in the snippet above, the Tar Entry gets mistaken for a symlink if the reparse point flag is set, but it doesn't verify if the file/directory is actually a symlink/junction. Windows Server with file deduplication enabled, or even OneDrive synced files, can set the Reparse point flag, but utilizes entirely different reparse tags.

IO_REPARSE_TAG_DEDUP is used for deduplication, whereas IO_REPARSE_TAG_MOUNT_POINT & IO_REPARSE_TAG_SYMLINK are used for junctions and symlinks.

Metadata

Metadata

Assignees

Labels

area-System.Formats.Tarbugin-prThere is an active PR which will close this issue when it is merged

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions