There is still no important function NTFS FILE ID + Directory NTFS File ID

[Debugger]

I asked many years ago for additional information about:

Code: Select all

NTFS File ID
Directory NTFS File ID

It still does not have this important function.
I tested outdated versions from Microsoft, but it does not work with Unicode and does not save full paths. Although it saves a lot of information very quickly.
Can this be implemented in the Everything tool?


Example:
Q:\Небесном Египте Яко\IMG_001.JPG
Ntfs File ID:2773915
Directory NTFS File ID:2755065



Application of this function:
Quickly finding a problem file detected by CHKDSK and quick recovery of a file or files without having to make a full backup, eg if the disk contains too much data.
If the file is valid, you can copy the file to another partition and then delete it from the original location. Fast, easy.

[NotNull]

Don't know if I understood correctly, but the function you mention is already implemented in Everything. Are you on an older version?

Let's say the problematic file is "C:\WINDOWS\System32\chkdsk.exe" (that would be really ironic )

On my system, it's File ID is 0x00000000000000000006000000051309
You can find the File ID by issuing this command:

Code: Select all

fsutil file queryfileid c:\WINDOWS\System32\chkdsk.exe

Now, in the Everything search bar, type this query:

Code: Select all

C: frn:0x00000000000000000006000000051309

And you get the matching filename (including complete path).
You need to include the driveletter, because it is very well possible that a file on D: (or any other local disk) has the same FileID.


Another simple way to find the filename:

Code: Select all

fsutil file queryfilenamebyid C:\ 0x00000000000000000006000000051309

[Debugger]

CHKDSK only shows simple file id

Everything even in the latest version does not have such a feature.
Pointless.
0x00000000000000000006000000051309
This is not a real simple ID (only number)
Give a very bad and not practical solution.. Your suggestion is useless. How do I automatically save a million folder names, subfolders, millions PATHs, or ID filenames?

[NotNull]

Pointless

very bad

not practical

useless

Well, that was the last time I ever tried to help you (and yes, I do have a solution).
Man, are you unfriendly and grumpy ....

[Debugger]

That's my personality nature, what can you do
If I have only the file ID (example: 190) or directory file id (example: 192), how should I know what file it is and what is the path?

[Stamimail]

That's my personality nature, what can you do

I know many people that have changed their "personality nature".
Maybe here is not the place to talk about it, but you need to know that it's changeable.

[void]

Everything does not index "file index" (FRN) information.

However, there is a frn: search command which will search for files with the matching FRN on all NTFS and ReFS volumes.
It is not the fastest, as Everything will need to lookup the filename from the FRN.

For example, search for:
frn:0x00000000000000000006000000051309

You can use decimal or hexadecimal (prefix with 0x) FRN values.

Everything does not display FRN information in the result list yet, this will be available in Everything 1.5.

[NotNull]

@void: Windows uses next to the FRN (also called File ID) another ID to address a file. Confusingly, this is sometimes called File ID, too.
(as poster was talking about File ID's, I was assuming the FRN)

The " short ID" is the ID that CHKDSK reports.
This second ID is a shorter number. You can get the FRN from that, but that's hard.
The other way around is a little simpler: strip the higher bits, which leaves you with 0x51309 (or 332553 decimal) for my CHKDSK.exe.

2017-12-30 00_24_00-Microsoft Edge.png (17.07 KiB) Viewed 55602 times

( ID2FILE is something I wrote. It accepts "Short ID's" as well as FRN's as parameter)

The usage of the "short ID" is very uncommon.

[void]

I've added to my TODO list: support short file IDs.
I also have on my TODO list: look up all hardlinks for frn:

[Debugger]

CHKDSK always shows only short and easy IDs [0-9] VERBOSE /v.
0x00000 bla bla are some weird and not practical in identifying many files.

[therube]

Linux DIR.EXE can list what it calls, "inode", which is the decimal representation of frn's hex version.

Code: Select all

C:\BIN\UNIX>dir.exe --inode e:/windows/system32/chkdsk.exe
281474976747397 e:/windows/system32/chkdsk.exe

C:\BIN\UNIX>es frn:281474976747397
X:\+o._e-fat-e-ccc-ruben2002-2\040700\TRAIN_X_7.jpg
M:\MUSIC\_from_USR\STACYs DELL\Sublime\05 April 29, 1992 (Miami).mp3
E:\Windows\SysWOW64\chkdsk.exe
H:\WINDOWS\Windows XP\XP\DELL OEM\I386\LANG\SVGAFIX.FO_
C:\Windows\winsxs\Backup\x86_microsoft-windows-x..rtificateenrollment_31bf3856ad364e35_6.1.7601.
17514_none_f59e20ddece8f922_certenroll.dll_d6e4c532

DIR.EXE can be found within coreutils-5.3.0-bin.zip.