Volume C stopped being indexed

[void]

Thank you for the service logs.

I am looking into the issue.



To rebuild just one drive:

In Everything, type in the following search and press ENTER:
/reindex c:

where c: is the drive to reindex.

[Thy Grand Voidinesss]

[...]
To rebuild just one drive:

In Everything, type in the following search and press ENTER:
/reindex c:

where c: is the drive to reindex.

An option to rebuild just one volume should be available after choosing lets say

Tools > Options... > Indexes > NTFS > Local NTFS volumes > CONTEXT MENU OF A DRIVE > Advanced > Force Rebuild This Volume

[void]

Everything 1.5.0.1361a adds an option to rebuild a specific volume from Tools -> Options -> NTFS.

For example, to reindex your C: drive:

• In Everything 1.5, from the Tools menu, click Options.
• Click the NTFS tab on the left.
• Select C:.
• Right click C: and click Reindex.
• Click OK.

Thanks again for the suggestion.

[Thy Grand Voidinesss]

Do you want me to rebuild my volume C and thus wait for the next occurrence of it not being indexed anymore once more - or should I wait out just a little longer before rebuilding it, as any time now you will update Everything with some new debugging additions?

[void]

I have on my TODO list to dump the Everything Service Monitoring state when starting debug logging.

Once this is done I'll send you an email in hopes we can catch the issue.

[void]

Everything 1.5.0.1362a will now log the Everything service state when starting service debug logging.

The next time you notice Everything has stopped monitoring your C: drive, could you please:

• In Everything, hold down Shift, from the Tools menu, under the Debug submenu, check Service Verbose.
• In Everything, hold down Shift, from the Tools menu, under the Debug submenu, click Start Service Debug Logging.
• In Everything, hold down Shift, from the Tools menu, under the Debug submenu, click Stop Service Debug Logging.
• Please send your C:\Windows\Temp\Everything Service Debug Log-1.5a.txt to support@voidtools.com

[Thy Grand Voidinesss]

I downloaded version 1.5.0.1363a (x64) Portable, replaced my old 1359a with it and was about to start debugging my still not re-indexed manually C drive with it - but I noticed that the issue is one again gone: i.e. my system drive is being updated immediately and thus (I suppose) it is up to date now

But if this problem comes back I will once again write down debugging logs an send them to you

[Thy Grand Voidinesss]

In the meantime: as pointed out by me at the end of this discussion viewtopic.php?p=61944#p61944, maybe what is triggering such stopping of indexing is me using this BAT script

Code: Select all

@echo off

taskkill /im Everything.exe
timeout /t 1 >nul
taskkill /im Everything.exe /t /f

net stop "Everything (1.5a)"

?

I can go days without a need for running it even once it - but there are also hours when I [like when mingling with Options] use it multiple times - and so maybe too many too often make it probable or something in my INI files to become broken?

[void]

Please avoid terminating Everything and the Everything Service.
You'll lose all changes to your settings and database.

If you must terminate Everything, please try removing the

net stop "Everything (1.5a)"

line.



It can take several minutes to save your database to disk.
Please create a mini crash dump if you find Everything is not responding on shutdown.

[Thy Grand Voidinesss]

And once again my volume C has stopped being indexed; a few weeks ago. Then, a couple of days ago, I have upgraded Everything to version 1.5.0.1371a x64 Portable- but it did not fix itself

And so: are you ready for a new set of logs from me?

[void]

Yes, please send the logs to support@voidtools.com

[Thy Grand Voidinesss]

I have just sent you yet another instance of

C:\Windows\Temp\Everything Service Debug Log-1.5a.txt

[void]

Thank you for the debug logs.

Everything is not handling incomplete IO errors correctly and is not handling stale USN Journals correctly.

Could you please see if the issue persists with Everything 1.5.0.1372a.
Everything 1.5.0.1372a addresses both of these issues which can cause Everything to stop monitoring your C: drive.

[Thy Grand Voidinesss]

1372a still does monitor my volume C - should I rescan it and report back?

[void]

No need to rescan, just report back if Everything stops indexing your C: drive or stops detecting changes on your C: drive.

Thanks for testing.

[Thy Grand Voidinesss]

As I said: the new version does not detect new files

It also does not notice deletion of already indexed ones

[void]

Could you please send some more debug output:

• In Everything, hold down Shift, from the Tools menu, under the Debug submenu, check Service Verbose.
• In Everything, hold down Shift, from the Tools menu, under the Debug submenu, click Start Service Debug Logging.
• Create a new folder C:\EverythingTest
• Delete this folder.
• Wait for at least one minute to let the logger catch any monitoring errors.
• In Everything, hold down Shift, from the Tools menu, under the Debug submenu, click Stop Service Debug Logging.
• Please send your C:\Windows\Temp\Everything Service Debug Log-1.5a.txt to support@voidtools.com

Could you also do the same for the client side logs:

• In Everything, from the Tools menu, under the Debug submenu, check Verbose.
• In Everything, from the Tools menu, under the Debug submenu, click Start Debug Logging.
• Create a new folder C:\EverythingTest
• Delete this folder.
• Wait for at least one minute to let the logger catch any monitoring errors.
• In Everything, from the Tools menu, under the Debug submenu, click Stop Debug Logging.
• Please send your %TEMP%\Everything Debug Log-1.5a.txt to support@voidtools.com

[Thy Grand Voidinesss]

I just did

[void]

Thank you for the logs.

I see Everything is regathering the free disk size for your root folders every second.

This might prevent Everything from updating.

Could you please try removing Free Disk Size from Tools -> Options -> Properties and see if the issue persists.

[void]

Ah, I am 99% sure it's from enabling Tools -> Options -> Advanced -> monitor_thread_mode_background

Please set this option to false.

When this option is enabled, Everything will only monitor your drives when they are idle.

Your C: will likely never be idle.

[Thy Grand Voidinesss]

[...]
Could you please try removing Free Disk Size from Tools -> Options -> Properties and see if the issue persists.

There had to be a reason why I added it - and most likely there has to be some topic on this forum in which I was instructed to use this option, but I just failed at finding it

For now I will leave that one as it is


As for this one

Ah, I am 99% sure it's from enabling Tools -> Options -> Advanced -> monitor_thread_mode_background

Please set this option to false.

When this option is enabled, Everything will only monitor your drives when they are idle.

Your C: will likely never be idle.

if this is true then it would affect also many other users right? And if yes then

Code: Select all

monitor_thread_mode_background

should be split into

Code: Select all

monitor_thread_mode_background_for_non-system_drives

and

Code: Select all

monitor_thread_mode_background_for_the_system_drive

[being by default set to false] to prevent that issue from happening, right?

I have turned it off but it seems that I also must re-index volume C, as new items are still not showing up. If you will tell me now to rebuild I will and then report back when indexing stops once again or after months if it will finally not occur for the n-th time

[void]

monitor_thread_mode_background comes with a warning.

Enabling can severely reduce the update performance of Everything.

I will likely remove monitor_thread_mode_background as it causes more issues than it helps.

There's only one monitoring thread.
I will consider a system and non-system thread.



The default value is: false.
Please set to false (the default value)



You will need to restart Everything after changing this setting.
No need to rebuild.

[Thy Grand Voidinesss]

I closed it including that monitoring process and after reopening double checked if

Code: Select all

monitor_thread_mode_background

was still set to false - and yet new items from C are still not showing up. So I need to index it once more, right?

[void]

You are running Everything in portable mode.

The Everything Service will be pulling this setting too.

Please exit Everything (File -> Exit)
Stop the Everything Service (Ctrl + Shift + ESC -> Task Manager -> Services -> Right click Everything -> Stop Service)
Restart Everything.

See if Everything is now picking up changes to your C: drive.

[Thy Grand Voidinesss]

You are running Everything in portable mode.

The Everything Service will be pulling this setting too.
[...]

As I said I already did close

[...]
it including that monitoring process
[...]

but as it turns out it was not true as my method for it has stopped working and I did not bother to check if it is still running in the Task Manager [viewtopic.php?p=66995#p66995]

But now I did make sure [i.e. double checked] if all EXE files of Everything were closed before re-opening of it - and yet I still do not get update of items

[Thy Grand Voidinesss]

As I was still having problem with that closing issue I decided to investigate it further: viewtopic.php?p=67406#p67406

And now after it has been bluntly removed [i.e. not uninstalled but simply deleted] my Everything has immediately started to notice changes on my volume C. And as I was still waiting for an answer from you and thus did not perform reindexing - then this was just a coincidence [i.e. some time before something else had triggered Everything to once more properly monitor my volume C] or it was precisely that removal of installed 1.4.1.1022 x64 that has fixed it once more

All in all a time can tell if 1.5 x64 portable will continue to work properly from now [i.e. without a presence of second installed old version on my system]

[Thy Grand Voidinesss]

[...]
or it was precisely that removal of installed 1.4.1.1022 x64 that has fixed it once more

So far indexing of my volume C holds up; although it has been only a 1.5 of month

I have also restored my Windows 10 from an image file [for the purpose of creating a new updated image of my operating system] that still had on it the 1.4 version installed. Unfortunately the dates of its installation was shown as 2023 04 26 while the initial post in this topic reporting the issue is from 2023 04 29 - so it is inconclusive i.e. 3 days between these 2 events is not enough to provide high enough probability for the 1.4 version running along being the culprit. I mean: it might have been and I also might have reported it immediately - but it also quite possible that it took me several days or even weeks notice the lack of indexing plus few days to actually find time for report it on the forum

And so once again

[...]
a time can tell if 1.5 x64 portable will continue to work properly from now [i.e. without a presence of second installed old version on my system]

But if it does hold up, I could then indulge in installing again the 1.4 again to see, if indexing will be yet again halted [but this time on purpose]