Hi! I've been using Everything for a while now and really like this simple yet powerful tool. I made an account and this thread because I have an issue that I would like being looked at.
I use the portable version as I don't use Everything every day and I open it a few times a week when I need to look for something. Problem is, some of the time at launch I get the dreaded "Indexing properties" loading bar and as I index a mechanical hard drive, it takes quite a lot of time to finish. This cannot be paused, cancelled or given lower priority as far as I know. What's weird is, I understand that some files might have been added, deleted or changed since last launch but Everything reindexes ALL of the files which seems strange and not efficient at all. I mean, the database is already there with 99.9% of the correct properties data (I at most modify 1000 out of 300000 files), why is this so?
Just in case you need some data, the db weighs 1.13GB. I index many video file properties like Frame Rate, Total Bitrate, length, width, Height and Aspect Ratio. The last rebuild reason of course is: Out of date NTFS volume D: is available
Is there a way to just check what changed and index properties of those files only? Reading all the files properties takes a lot of time and the disk is very busy for a long while. I understand I might be an edge case as I have many properties that I use but still, rereading files that have not been modified in years seems like a waste, the database has already all the properties on hand.
Cheers and thanks for a great tool.
Everything reindexing all the file properties for no apparent reason
Re: Everything reindexing all the file properties for no apparent reason
Thank you for your feedback Xan,
If this journal is filled while Everything is not running, Everything will have to reindex.
Please check the last rebuild reason under Tools -> Debug -> Statistics -> Build -> Last Rebuild Reason
(Out of date NTFS found == too many changes occurred while Everything was not running)
Please try increasing your Maximum USN Journal size:
-or-
keep Everything running in the background.
Everything will reindex your drive as it's basically seen as a new drive.
I am going to be rewriting Everything 1.5 to prevent property reindexing.
There's no way I can support the current versions.
It's going to take a long time so please bear with me..
Property indexing can be paused under Index menu -> Pause property indexing.This cannot be paused
Tools -> Options -> Advanced -> load_indexed_property_priorityor given lower priority
Everything will use the NTFS USN Journal to keep your index up-to-date.I understand that some files might have been added, deleted or changed since last launch but Everything reindexes ALL of the files which seems strange and not efficient at all.
If this journal is filled while Everything is not running, Everything will have to reindex.
Please check the last rebuild reason under Tools -> Debug -> Statistics -> Build -> Last Rebuild Reason
(Out of date NTFS found == too many changes occurred while Everything was not running)
Please try increasing your Maximum USN Journal size:
- In Everything 1.5, from the Tools menu, click Options.
- Click the NTFS tab on the left.
- For each NTFS volume:
- Change Maximum size to: 262144 KB.
- Click OK.
-or-
keep Everything running in the background.
Everything will try to keep your indexed properties, but they are all flagged as dirty.I mean, the database is already there with 99.9% of the correct properties data (I at most modify 1000 out of 300000 files), why is this so?
Everything will reindex your drive as it's basically seen as a new drive.
I am going to be rewriting Everything 1.5 to prevent property reindexing.
There's no way I can support the current versions.
It's going to take a long time so please bear with me..
Re: Everything reindexing all the file properties for no apparent reason
Hey! Thanks for the reply. I will try your suggestions. I found out about pausing just after posting and felt silly. The priority thing its useful.
Thanks a lot for the time and the journal tip, I'll report back if anything worthwhile comes up.
My first post had the rebuild reason and yes, it is Out of date NTFS.Please check the last rebuild reason under Tools -> Debug -> Statistics -> Build -> Last Rebuild Reason
(Out of date NTFS found == too many changes occurred while Everything was not running)
I will! It was at 32768 Kb so the extra size will probably help.Please try increasing your Maximum USN Journal size:
I'm thinking about setting it up, but the extra overhead for mechanical disks (The everything database is on a mech disk too) and keeping up with all the file changes (Very useful too, see what file was modified in real time) was a little too much. I'm happy if I know it won't reindex all the files.keep Everything running in the background.
Don't ever worry about it! You need to bear with us users, lol.It's going to take a long time so please bear with me..
Thanks a lot for the time and the journal tip, I'll report back if anything worthwhile comes up.
Re: Everything reindexing all the file properties for no apparent reason
Just to update about this. Increasing the journal size solved all the reindexing issues. Things work beautifully now. Thanks again for the help!
Re: Everything reindexing all the file properties for no apparent reason
Everything 1.5.0.1401a rewrites property indexing.
Everything will now remember index properties when doing a reindex.
Properties are now kept when moving a volume to a new drive letter.
Properties are now kept when too many changes have occurred.
Adding a new property to your index will now only index that property.
The database has changed in 1401a.
Previous versions required a full reindex on a database change.
1401a also adds database migration support so the full reindex is not required.
You might see a couple seconds delay to migrate your database when running 1401a for the first time.
-If you change back to 1400a or earlier a full reindex will be required.
Everything will now remember index properties when doing a reindex.
Properties are now kept when moving a volume to a new drive letter.
Properties are now kept when too many changes have occurred.
Adding a new property to your index will now only index that property.
The database has changed in 1401a.
Previous versions required a full reindex on a database change.
1401a also adds database migration support so the full reindex is not required.
You might see a couple seconds delay to migrate your database when running 1401a for the first time.
-If you change back to 1400a or earlier a full reindex will be required.
Re: Everything reindexing all the file properties for no apparent reason
After starting 1401 I get this message:
Restarted, database rebuilds, all is OK.
Went back to 1400, tried it again. It is reproducible.
I don't need it fixed, but I thought you would be interested,
Went back to 1400, tried it again. It is reproducible.
I don't need it fixed, but I thought you would be interested,
Re: Everything reindexing all the file properties for no apparent reason
Thank you for testing 1.5.0.1401a froggie,
Everything is not migrating the extension fast sort database.
I will have a fix soon.
Everything is not migrating the extension fast sort database.
I will have a fix soon.
Re: Everything reindexing all the file properties for no apparent reason
Everything 1.5.0.1402a will now migrate the extension fast sort database.