Failure to update indexes

If you are experiencing problems with "Everything", post here for assistance.
Post Reply
gunrunnerjohn
Posts: 21
Joined: Fri Oct 02, 2009 7:35 pm

Failure to update indexes

Post by gunrunnerjohn » Fri Oct 02, 2009 7:46 pm

I am running the current version of Everything (1.2.1.371), for the most part it's slick as snot. I have one small issue that I see now, it appears it's not updating the indexes reliably. I deleted a folder and some other files a few days ago, they still appear in the Everything search. I know it's supposed to automatically index, and I see it running in Task Manager, is there something I'm missing?

I also note that it seems to get confused when you have the system sleep, perhaps this is related? Here's the last few entries in the error log. Could that be why it's not automatically updating?

9/30/2009 3:02:07 AM: Everything 1.2.1.371: .\src\db.cpp(18912): db::watch_for_next_update(): DeviceIoControl(): 6: Failed to ready notify for drive H:.
9/30/2009 3:02:10 AM: Everything 1.2.1.371: .\src\db.cpp(18912): db::watch_for_next_update(): DeviceIoControl(): 6: Failed to ready notify for drive D:.
9/30/2009 3:02:10 AM: Everything 1.2.1.371: .\src\db.cpp(18912): db::watch_for_next_update(): DeviceIoControl(): 6: Failed to ready notify for drive D:.
9/30/2009 3:02:11 AM: Everything 1.2.1.371: .\src\db.cpp(18912): db::watch_for_next_update(): DeviceIoControl(): 6: Failed to ready notify for drive D:.
9/30/2009 3:02:14 AM: Everything 1.2.1.371: .\src\db.cpp(18912): db::watch_for_next_update(): DeviceIoControl(): 6: Failed to ready notify for drive F:.
9/30/2009 3:02:15 AM: Everything 1.2.1.371: .\src\db.cpp(18912): db::watch_for_next_update(): DeviceIoControl(): 6: Failed to ready notify for drive G:.
9/30/2009 3:02:16 AM: Everything 1.2.1.371: .\src\db.cpp(18912): db::watch_for_next_update(): DeviceIoControl(): 6: Failed to ready notify for drive E:.

David
Site Admin
Posts: 430
Joined: Tue Mar 17, 2009 1:42 am

Re: Failure to update indexes

Post by David » Fri Oct 02, 2009 11:34 pm

I am aware of the issue and it has been fixed for the next release of "Everything".

It is caused by old update events firing when a monitor is not ready.
For example, putting the computer to sleep.

The problem causes the monitors to stop.

Restart "Everything" to restart the monitors.
You can optionally disable the monitors or try increasing the USN Journal maximum size to at least 32,768 KB for each NTFS volume.

Please try replacing your Everything.exe with the latest alpha:
http://www.voidtools.com/Everything-1.2.1.426a.zip

gunrunnerjohn
Posts: 21
Joined: Fri Oct 02, 2009 7:35 pm

Re: Failure to update indexes

Post by gunrunnerjohn » Fri Oct 02, 2009 11:54 pm

I presume I copy the alpha to the Everything folder. Do I have to rename it Everything to get it to start automatically?

David
Site Admin
Posts: 430
Joined: Tue Mar 17, 2009 1:42 am

Re: Failure to update indexes

Post by David » Sat Oct 03, 2009 12:11 am

Yes, sorry, please try replacing your Everything.exe with the latest alpha.

gunrunnerjohn
Posts: 21
Joined: Fri Oct 02, 2009 7:35 pm

Re: Failure to update indexes

Post by gunrunnerjohn » Sat Oct 03, 2009 12:14 am

OK, I increased those USN Journal values to 32768 and the Allocation Data to 4096, which were the values that originally came up for my boot volume. I also copied the alpha in and renamed it and started it. It appears to have some new options, I guess I'll have to figure those out.

I also notice that it correctly formats a whole disk search default, something I forgot to mention, I guess I don't have to now! :D

Post Reply