What is the Current Status of How E. Handles Hard Links?

General discussion related to "Everything".
Post Reply
TTTTII
Posts: 10
Joined: Mon Aug 08, 2016 11:58 pm

What is the Current Status of How E. Handles Hard Links?

Post by TTTTII » Thu Jun 08, 2017 1:06 am

Precisely, how does Everything handle hard links? I've read what I could find in the forums, but many posts are quite old.

I do use quite a few hard links in my workflow, so I'd appreciate an exact answer on this - or some help finding a reference that I missed.

Does it change its behavior if USN Journal is not used? It seems that renaming one affects updating?

Any chance we'll be able to do an Everything search that specifically seeks hard links?

Also, if applicable, where you are headed with this?

***

And how about symbolic links and junctions? Are symbolic links handled differently if they refer to a file versus a folder? Or hop volumes? USN Journal used or not?

My apologies if this information is available clearly elsewhere, and also for personally having more of a practical understanding of their use rather than an extremely precise understanding on a file system level.

My thanks in advance.

void
Site Admin
Posts: 4805
Joined: Fri Oct 16, 2009 11:31 pm

Re: What is the Current Status of How E. Handles Hard Links?

Post by void » Thu Jun 08, 2017 1:44 am

Precisely, how does Everything handle hard links?
Everything 1.3 only indexes the first instance of a hardlink.
Everything 1.4 indexes all long filename hardlinks from the MFT.

There are some limitations with Everything 1.4:
When a change is made to a hard link, the size, date modified, date created and attributes of only the first hard link instance is updated.

For example, if you have two hard-linked files:
a.txt and b.txt, if you modify a.txt, Everything will only receive an update notification for one of the files, which one depends on the first hard link entry in the MFT, so it is possible Everything will only update b.txt

This is a limitation with the USN Journal. The filename in a USN Change Journal record is generally the first hard link instance.
What I have on my TODO list is to use the FRN from the USN Change Journal record and lookup all the hard links, of course there's a minor performance hit in doing so.

To update all hard links you will need to force a rebuild from Tools -> Options -> Indexes -> Force rebuild.

Everything does not follow junctions automatically.
Junctions to NTFS volumes can be added manually.
Junctions to non-NTFS volumes are not supported, you will need to use folder indexing for these.

Folder indexing will follow junctions.
And how about symbolic links and junctions?
Currently they are treated the same, that is Everything does not follow the junction or symbolic link.
You can setup Everything to follow either of these manually.

http://www.voidtools.com/support/everyt ... imitations

TTTTII
Posts: 10
Joined: Mon Aug 08, 2016 11:58 pm

Re: What is the Current Status of How E. Handles Hard Links?

Post by TTTTII » Tue Jun 13, 2017 3:32 pm

Thank you - very much - for taking the time to answer my question.

Post Reply