Missing files - db not being updated ?

[joebrug]

Currently running 1.5.0.1335..

Have had some users report lately that they cannot see files, when other users can. There are no permissions involved here that would be the cause. I've witnessed the same thing. The only fix, is to close Everything, delete their %localappdata%\everything\*.db file and then re-launch Everything. This of course causes the database to be rebuilt and the "missing files" now appear for the user.

Whats strange is it just appears to be random files. It's not like its missing the newest files or anything. What might cause this? If it matters, we're using the Network Index.. have just over 5,000,000 files.

Happy to provide whatever might help

[void]

v1336 fixes a major issue with excluding files/folder from a network index.

Are any of the users exclude files/folders from Tools -> Options -> Exclude?

Omit results enabled under Index -> Enable result omissions?
Any enabled search options shown in the bottom right of the status bar?

[joebrug]

Will update just in case.
No, users don't have Exclude settings (although the server side excludes a couple of directories)
No, no omissions.
No search options are set.

It's like it "missed" files at some point.

[void]

Thank you for the information.

I assume these clients with missing files are detecting new changes.
Please let me know if they are not picking up recent changes.

Are they just missing certain folders?
or is it random files?

Could you please compare the statistics between a bad client and a good client:

• In Everything, from Tools menu, under the Debug submenu, click Statistics.
• Your Network Indexes are listed at the bottom.
• Please compare the Date indexed, remap ID and Journal ID.
  -Did the bad clients reindex at some stage? do the remap IDs and Journal IDs match the good clients?

Does forcing a rebuild pickup the missing files from Tools -> Options -> Indexes -> Force Rebuild?

[joebrug]

Its random files. The remap/index ID's seem to match regardless of number of files found. and yes, Force Rebuild results in more files found.

**User who had about 300 less items (according to bottom corner) than I did before rebuild**

Network Index
Host: fileserver2
Include only:
Mount:
Index number: 0
Date indexed: 12/28/2022 12:53 PM
Out of date: No
Online: Yes
Disk device index:
Multithreaded: Separate device thread
Folder count: 95
File count: 5,195,583
Remap ID: A
Journal ID: B
Next journal item ID: 109035

**My computer before Force Build**

Network Index
Host: fileserver2
Include only:
Mount:
Index number: 0
Date indexed: 1/22/2023 8:13 AM
Out of date: No
Online: Yes
Disk device index:
Multithreaded: Separate device thread
Folder count: 84
File count: 5,195,894
Remap ID: A
Journal ID: B
Next journal item ID: 109040

[void]

Thank you for the information.

Everything is getting out of sync.
I'm looking into possible reasons this might have occurred.

There might be an issue with changes not being processed when exiting Everything.
(Everything's updating the next journal ID without processing the events)
I haven't been able to produce the issue yet, I'll keep looking..

It could be the remapping on the server side causing trouble.
Please let me know if the issue persists with 1337a+

The matching Remap IDs and Journal IDs is expected.

The higher folder count on the out of sync client is odd.
You aren't indexing many folders, perhaps the next time this occurs, please take note of the folders that are out of sync.
You can search for folders only with: folder:
The folder names not updating might be a clue.