Disabled scanning but still scans

[Stretto]

I have a rather large drive that doesn't change and I've disable scanning of the drive after the main scan. Yet about once a week of not being used Everything still scans the large drive taking around 25 minutes to scan the drive for changes then it crashes.

I removed all drives from Indexes and simply added the drive as a folder and selected "never scan" so I could disable scanning and yet it does nothing. It seems that it is stuck on rescanning once a week even though I have it set to never scan.

[therube]

(Aside from the actual problem, see if adding the

-read-only

switch to the Everything.exe command line helps?
[That would only be of benefit if you didn't want any drives to be updated.])

[Stretto]

(Aside from the actual problem, see if adding the

-read-only

switch to the Everything.exe command line helps?
[That would only be of benefit if you didn't want any drives to be updated.])

That causes nothing to be loaded(0 objects).

[void]

Everything might be performing a full reindex.

Could you please enable debug logging:

• In Everything, type in the following search and press ENTER:
  /debug_log=1
• If successful you should see debug_log=1 in the status bar for a few seconds.
• Type in the following search and press ENTER:
  /restart
  ---Everything will restart with debug logging enabled.
• The next time you notice Everything rescanning, please
  Send your %TEMP%\Everything Debug Log.txt to support@voidtools.com
  -or-
  Check the debug log for the following line:
  rebuild: <rebuild reason>
  What is the <rebuild reason>?

Debug logs can grow very large.
To disable debug logging:

• In Everything, type in the following search and press ENTER:
  /debug_log=0
• If successful you should see debug_log=1 in the status bar for a few seconds.
• Type in the following search and press ENTER:
  /restart

[Stretto]

Everything might be performing a full reindex.

Yeah, I think this is what was happening. I was using a rather old database and since I use it on a ram drive(I copy it to it once for maximum performance) it would keep trying to update it. Maybe I changed a setting or something in Everything that caused it to see the database as out of sync. I can't be sure any of that was it but so far things are working as intended. So either it is checking the data of the database(it was about a year old) or some settings are not matching and so it keeps updating even with never scan. Probably should give a warning dialog that the database must be updated when it updates it and possibly a reason why(e.g., settings changed or it's over a year old or whatever it might be).

[void]

Everything loads the entire database into RAM.

Copying the database to a RAM drive is only going to hurt performance.


If you still want to use a RAM drive you will need to copy the updated database back to the physical disk occasionally.
However, Everything does not save the database to disk until you exit Everything.

Please try the following to update your database on disk:
Everything.exe -update
---this will block until the database is completely written to disk.
Copy the Everything.db back to the physical disk.



The database is just a cache of your volumes, if it is out of date, or a setting has changed, Everything will rebuild the database.
In your case, the database is not being saved to disk correctly, so it is always pulling an out of date index and rebuilding.

Check the debug logs for more details about the rebuild.

Everything 1.5 shows this information in Tools -> Debug -> Statistics -> Build.

I will consider showing a warning to the user about a rebuild, thanks for the suggestion.