Question/Verify Functionality - Repeating Drive Entries in Debug Logs

Found a bug in "Everything"? report it here
Post Reply
Mrantala
Posts: 10
Joined: Sun Mar 03, 2019 5:12 pm

Question/Verify Functionality - Repeating Drive Entries in Debug Logs

Post by Mrantala »

Hello -
While triaging what turned out to be my own configuration issue, I noticed sections in the debug logs where there same Drive Letters were logged along with varying GUIDs (I believe that's what they are). I believe these entries might be a part of an Index Rebuild ? That what I was mostly doing at the time. Anyways, these entries I'm sure are correct if this is meant to include historical mappings as well (I do a lot of cloning new drives which means a lot of drive swapping). Obviously only entry per drive letter is valid at any time.

I just wanted to make you aware of these, so you can determine if there is an underlying issue or not. Would this have a performance impact ? Or other related issues ? I realize this could very well be caused by some clean up that I could be doing periodically, that I'm not. If that's the case, whether that's deleting a file or possibly cleaning up some old registry entries, if you could let me know what steps should be and I can get a task set up to run that cleanup for me.

Thanks !

Code: Select all

2021-11-05 02:49:37.628: VOLUME \\?\Volume{GUID1} A:  1 0 0 0 0 1 3
2021-11-05 02:49:37.628: VOLUME \\?\Volume{GUID2} A:  1 0 0 0 0 1 3
2021-11-05 02:49:37.628: VOLUME \\?\Volume{GUID3} A:  1 0 1 0 1 1 3
2021-11-05 02:49:37.628: VOLUME \\?\Volume{GUID4} A:  1 0 0 0 0 1 3
2021-11-05 02:49:37.628: VOLUME \\ASUS4\USB21 A:  1 0 0 0 0 4 4
2021-11-05 02:49:37.628: VOLUME \\?\Volume{GUID2} B:  1 1 0 0 0 1 3
2021-11-05 02:49:37.628: VOLUME \\ASUS4\USB21 B:  1 1 0 0 0 4 4
2021-11-05 02:49:37.628: VOLUME \\ASUS4\USB22 B:  1 1 0 0 0 4 4
2021-11-05 02:49:37.628: VOLUME \\?\Volume{GUID5} C:  1 0 1 0 1 1 3
2021-11-05 02:49:37.628: VOLUME \\?\Volume{GUID2} D:  1 0 0 0 0 1 3
2021-11-05 02:49:37.628: VOLUME \\?\Volume{GUID6} D:  1 0 0 0 0 1 3
2021-11-05 02:49:37.628: VOLUME \\?\Volume{GUID7} D:  1 0 0 0 0 1 3
2021-11-05 02:49:37.628: VOLUME \\?\Volume{GUID8} D:  1 0 0 0 0 1 3
2021-11-05 02:49:37.628: VOLUME \\?\Volume{GUID1} E:  0 0 1 0 1 1 3
2021-11-05 02:49:37.628: VOLUME \\?\Volume{GUID9} E:  1 0 0 0 0 1 2
2021-11-05 02:49:37.628: VOLUME \\?\Volume{GUID10} E:  1 0 0 0 0 1 3
2021-11-05 02:49:37.628: VOLUME \\?\Volume{GUID6} E:  1 0 0 0 0 1 3
2021-11-05 02:49:37.628: VOLUME \\?\Volume{GUID11} E:  1 0 0 0 0 1 3
2021-11-05 02:49:37.628: VOLUME \\?\Volume{GUID7} E:  1 0 0 0 0 1 3
2021-11-05 02:49:37.628: VOLUME \\?\Volume{GUID8} E:  1 0 0 0 0 1 3
2021-11-05 02:49:37.628: VOLUME \\?\Volume{GUID12} E:  1 0 0 0 0 1 3
2021-11-05 02:49:37.628: VOLUME \\ASUS4\USB22 E:  0 0 0 0 0 4 4
2021-11-05 02:49:37.628: VOLUME \\Asus4\usb1 E:  0 0 0 0 0 4 4
2021-11-05 02:49:37.628: VOLUME \\?\Volume{GUID13} F:  1 0 0 0 0 1 2
2021-11-05 02:49:37.628: VOLUME \\?\Volume{GUID10} F:  0 0 0 0 0 1 2
2021-11-05 02:49:37.628: VOLUME \\?\Volume{GUID6} F:  1 0 0 0 0 1 2
2021-11-05 02:49:37.628: VOLUME \\.\G: G:  1 0 0 0 0 1 3
Last edited by void on Mon Nov 08, 2021 7:26 am, edited 2 times in total.
Reason: removed GUIDs and code formatting
void
Developer
Posts: 16680
Joined: Fri Oct 16, 2009 11:31 pm

Re: Question/Verify Functionality - Repeating Drive Entries in Debug Logs

Post by void »

These are volume GUIDs.
I just wanted to make you aware of these, so you can determine if there is an underlying issue or not. Would this have a performance impact ? Or other related issues ? I realize this could very well be caused by some clean up that I could be doing periodically, that I'm not. If that's the case, whether that's deleting a file or possibly cleaning up some old registry entries, if you could let me know what steps should be and I can get a task set up to run that cleanup for me.
Unlikely to cause issues or performance loss.
Everything identifies a volume by the volume-guid, mount path and root path.
Everything will remember settings for each volume forever.
You may have a few volumes with GUIDs and paths that no longer exist, these will be marked as 'not found'.
I don't recommend changing the registry to delete any old GUIDs.
Everything will not access a volume that is not included or not found.


Consider disabling automatically include volumes in Everything:
  • In Everything, from the Tools menu, click Options.
  • Click the NTFS tab on the left.
  • Uncheck Automatically include new fixed volumes.
  • Uncheck Automatically include new removable volumes.
  • Uncheck Automatically remove offline volumes.
  • Click OK.

To manually remove offline volumes from your index:
  • In Everything, from the Tools menu, click Options.
  • Click the NTFS tab on the left.
  • Select an offline volume.
  • Click Remove.
  • Click OK.


The current debug log format for VOLUME is:

VOLUME <volume-guid> <mount-path> <root-path> <included> <excluded> <include-in-list> <user-added> <found> <everything-type> <drive-type>



Consider resetting your Everything NTFS volume list:
  • Completely exit Everything (File -> Exit)
  • Open your %APPDATA%\Everything\Everything.ini
  • Change the following lines:
    ntfs_volume_guids=\\?\Volume{GUID1},\\?\Volume{GUID2},\\?\Volume{GUID3}
    ntfs_volume_paths=c:,d:,e:
    ntfs_volume_roots=,,,
    to:
    ntfs_volume_guids=
    ntfs_volume_paths=
    ntfs_volume_roots=
  • Save changes and restart Everything.

ntfs_volume_guids
ntfs_volume_paths
ntfs_volume_roots
Post Reply