After an application creates a new hardlink on an NTFS volume, NTFS reports that both hardlinks exist, but Everything only indexes the original path. The second path does not appear until a Force Rebuild is performed.
Environment
- Windows 11 Pro 24H2 (Build 26100.6584)
- Everything 1.4.1.1032 x64
- NTFS volume with USN Journal enabled
- "Load recent changes from USN Journal" enabled
- "Monitor changes" enabled
How I observed the issue
I consistently observe this behavior when Sonarr imports media using its "Use Hardlinks instead of Copy" option.
Steps observed
- A file already exists on an NTFS volume.
- A second hardlink is created to that file.
- confirms that both hardlinks exist.
Code: Select all
fsutil hardlink list "<path>" - Explorer can access both hardlink paths.
- Everything only displays the original path until a Force Rebuild is performed.
Everything should immediately show both paths.
Actual
Everything only shows the original path. The newly created hardlink is not indexed until a Force Rebuild is performed. After the Force Rebuild, the second hardlink immediately appears without any additional filesystem activity.
Verification
- Explorer can access both hardlink paths.
- confirms both hardlinks exist before a Force Rebuild.
Code: Select all
fsutil hardlink list - After a Force Rebuild, Everything immediately displays both paths.