searching network drive - not finding deep nested files

[dwilbank]

Admittedly, the drive is huge.

Is there a max-depth setting for the indexing that I could change?
Or is there a hard limit to how much can be indexed, so that deeply nested simply will not be reached?

Thanks

[therube]

How deep?
(In any case, I wouldn't think that should matter.)

Can Windows see it?

Is the file a hardlink?

Any filtering going on that may be causing the item to not turn up?
Typo & or are you misinterpreting the name (the characters in the name) as something that it is not?
(The last two catch me - fairly often.)


What version of Everything?

[void]

How are you indexing the drive?
eg: Tools -> Options -> NTFS or Tools -> Options -> Folders?


If you are using folder indexing:
You are limited to a full path depth of 32,000 characters.


If you are using NTFS indexing:
There's no real limits for NTFS indexing.

NTFS indexing does not follow folder junctions.
Is the missing folder a folder junction?

There could be a damaged folder which is orphaned.

Please try forcing a rebuild:

• In Everything, from the Tools menu, click Options.
• Click the Indexes tab on the left.
• Click Force Rebuild.
• Click OK.

If the folder is still missing, please check your drive for errors:

• Please backup anything important on your drive before checking it for errors.
• In Windows Explorer, right click your drive and click Properties.
• Click the Tools tab.
• Click Check now...
• Click Start
• If prompted to schedule a scan on the next restart, click Yes.

[dwilbank]

It's an 8 PB Network drive mounted on my machine.
So the only way I can index it is as a folder, right?

Not sure what that 32000 character depth means.
The longest file path is probably only 100-200 characters.

While I force a rebuild, I'd like to confirm that it's even possible to index a drive this large.
The Buffer Size info box says 'Network drives are limited to 64k'
Could the sheer number of files be the problem? Indexing just stops?

And would using the Include only files: box what I need to get around that?
just a semicolon delimited list of the file extensions I expect to find?

[therube]

To confirm, you are saying "PB" (rather then TB), so 1024 TB (* 8) or so?

[dwilbank]

yep - PB

[NotNull]

It's an 8 PB Network drive mounted on my machine.
So the only way I can index it is as a folder, right?

Right!
(menu:Tools => Options => Indexes => Folders)

Not sure what that 32000 character depth means.
The longest file path is probably only 100-200 characters.

32000 is the length of the full filename including path, so 200 should not be an issue ..

While I force a rebuild, I'd like to confirm that it's even possible to index a drive this large.
The Buffer Size info box says 'Network drives are limited to 64k'
Could the sheer number of files be the problem? Indexing just stops?

Everything uses approximately 100MB RAM per 1 million files. Make sure you are running the 64-bit version of Everything as the 32-bit version is limited to 2GB.


I guess you are now indexing either \\server\share or a driveletter mapped to this share.
My suggestion would be to test with a subfolder (like \\servre\share\subfolder1\subfolder2 or X:\subfolder1\subfolder2) to see if that gets indexed successfully.

In the end, you might want to split the share in multiple subfolders to index. This gives the possibility to give each a separate update schedule.
(instead of updating a 8PB share all at once)


FWIW: Everything 1.5 processes updates in the background, so Everything is still usable when updating.

[void]

To exclude folders by depth, please try creating a folder exclude filter:

• In Everything, from the Tools menu, click Options.
• Click the Exclude tab on the left.
• Click Add filter....
• Set the filter to:
  \\server\share\*\*\*
  where the trailing *\*\* will determine the minimum depth to exclude.
• Click OK.
• Click OK.