Indexing GVFS on REFS drive hangs Everything

[ezillinger_msft]

I have an extremely large git repo using the Git Virtual File System on an REFS drive that locks up Everything when it tries to index it. I've attached a screenshot of the debug console:

image.png (65.32 KiB) Viewed 2673 times

Is there anything else I can do to help debug this?

[void]

Thank you for the issue report ezillinger_msft,

I will look into the issue, i wonder why Everything is successfully getting a file id of 0xffffffffffffffffffffffffffffffff ..

Does a chkdsk return any errors?
-Please make a backup of anything important before running chkdsk.



For now, please try indexing as a folder index under Tools -> Options -> Folders.
Uncheck Include in database for your Refs volume under Tools -> Options -> ReFS.

[ezillinger_msft]

Thanks for looking into this!

chkdsk doesn't work with REFS but running Repair-Volume from pwsh doesn't report any corruption.

It seems like nothing gets indexed at all if I remove the REFS drive from the DB and add my repo as a folder:

Code: Select all

UPDATE NOW check D:\os D:\os
UPDATE NOW D:\os
update folder start D:\os
scanning D:\os...
next update at 27/11 17:24
scan completed in 0.000253 seconds
scan completed in 0.000396 seconds
rescan update db
leave folder update
new results 0

[NotNull]

You are running Everything *as administartor* (elevated) according to the debug log ("IsAdmin 1").
Most of these virtual filesystems run in userspace ( = as the currently logged in user). Don't know about GVFS.
Ar you certain your elevated account has access to the GVFS?

Try running Everything as user:
Under Options => General:
- disable Run as Administrator
- Enable Everything Service

When running as administrator, Everythings titlebar will show Administrator

[void]

I haven't had much luck getting GVFS going here, I need an Azure DevOps account..

Does the issue occur with Everything 1.5?



Everything uses OpenFileById and GetFileInformationByHandleEx with FileIdExtdDirectoryInfo to scan ReFS volumes.

I am not sure why the GetFileInformationByHandleEx API with FileIdExtdDirectoryInfo returns an invalid file ID.



I have made an Everything build that ignores 0xffffffffffffffffffffffffffffffff file IDs:

Everything-1.5.0.1402a.x64-GVFS1.zip

Please see if this version helps.
I suspect there's one or two folders being scanned, but nothing else.

To install:
Please install Everything 1.5 first.
Exit Everything 1.5 (File -> Exit)
Stop the Everything Service:
From the Start menu, search for:

services

Click Services.
In Service, right click Everything Service and click Stop. (can be done as a standard user)
Replace your C:\Program Files\Everything 1.5a\Everything.exe with the one from the zip above.
Restart Everything.



This version also adds the current ReFS folder being scanned to the verbose debug console.
To show the verbose debug console:
In Everything 1.5, from the Tools menu, under the Debug submenu, check Verbose
From the Tools menu, under the Debug submenu, check Console.
Look for the following lines:

Scan 0xXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX...

See if Everything is actually scanning valid folder ids.



If Tools -> Options -> Folders doesn't work with Everything 1.4, then I would assume indexing GVFS is not possible with Everything.
Can you access GVFS volume with a command prompt or power shell?

[ezillinger_msft]

I just tried the vanilla Everything 1.5 release and it works great with my GVFS directory!

I turned on the Admin mode in 1.4 to try to debug my problem. It doesn't work with or without admin. Both powershell and cmd prompt have no problems accessing GVFS.