Index file size causes file size corruption

[SuperDude]

If I check the box by "Index file size" (enable), it causes Everything to show bizarre file sizes, as seen in this screenshot:



Unchecking the box returns Everything's sizes back to normal.

[SuperDude]

Update: Unchecking all options, including "Index file size" is still causing Everything to display some file sizes in the petabytes range. Some files are displayed with corruption in their file names (in the file list). In these cases, there is no information displayed for any of the columns (just blank where there should be size, dates, path, etc). However, if I downgrade to Everything 1.3.4.686fix3 (x64), all of these problems disappear.

[therube]

How many files do you have, total?

> Some files are displayed with corruption in their file names

Anything "odd" with the particular files &/or paths?
(And no, I don't know what odd might be.)

[SuperDude]

All of the corrupted entries are on my USB 3.0 Western Digital 3 TB external hard drive, so that's interesting. I ran Scandisk on that drive, it came up clean. Hard Disk Sentinel's diagnostics also shows no problems. HD Tune Pro v5.50 also comes up clean.

I don't understand why the problem goes away if I use the previous version of Everything (version 1.40.688). Maybe the drive being 3TB is causing a problem? It would be interesting to see if anyone else is having problems with very large drives...

[void]

Thanks for the bug report.

It looks like the size is the files FRN. This should not be happening..
Are dates also corrupt?
Are you using the Everything Service?

Could you please send some information about your external drive?

From a command prompt what is displayed after running the following commands?

Code: Select all

fsutil fsinfo volumeinfo d:
fsutil fsinfo ntfsinfo d:

where d: is your external USB drive.

[SuperDude]

The drive in question is a Western Digital My Book 3TB USB 3.0 external hard drive. Here it is on Amazon:

http://www.amazon.com/Book-USB-Hard-Dri ... hard+drive

I've checked its health using the Windows disk checker, Hard Disk Sentinel, and HD Tune Pro. All returned good results. The dates are not corrupted. Here is a screenshot of what it looks like: http://i.imgur.com/G3T4PXs.jpg

What is file FRN?

fsutil fsinfo volumeinfo F:

Code: Select all

NTFS Volume Serial Number :       0x54d8d96ad8d94abe
NTFS Version   :                  3.1
LFS Version    :                  2.0
Number Sectors :                  0x000000002ba9f2ff
Total Clusters :                  0x000000002ba9f2ff
Free Clusters  :                  0x000000000f1b9c8e
Total Reserved :                  0x0000000000002df0
Bytes Per Sector  :               4096
Bytes Per Physical Sector :       4096
Bytes Per Cluster :               4096
Bytes Per FileRecord Segment    : 4096
Clusters Per FileRecord Segment : 1
Mft Valid Data Length :           0x000000000ea00000
Mft Start Lcn  :                  0x00000000000c0000
Mft2 Start Lcn :                  0x0000000015d4f97f
Mft Zone Start :                  0x00000000000cea00
Mft Zone End   :                  0x00000000000d2500
Resource Manager Identifier :     96E276B8-F4E7-11E3-A5CF-F46D04D2D892

fsutil fsinfo ntfsinfo F:

Code: Select all

NTFS Volume Serial Number :       0x54d8d96ad8d94abe
NTFS Version   :                  3.1
LFS Version    :                  2.0
Number Sectors :                  0x000000002ba9f2ff
Total Clusters :                  0x000000002ba9f2ff
Free Clusters  :                  0x000000000f1b9c8e
Total Reserved :                  0x0000000000002df0
Bytes Per Sector  :               4096
Bytes Per Physical Sector :       4096
Bytes Per Cluster :               4096
Bytes Per FileRecord Segment    : 4096
Clusters Per FileRecord Segment : 1
Mft Valid Data Length :           0x000000000ea00000
Mft Start Lcn  :                  0x00000000000c0000
Mft2 Start Lcn :                  0x0000000015d4f97f
Mft Zone Start :                  0x00000000000cea00
Mft Zone End   :                  0x00000000000d2500
Resource Manager Identifier :     96E276B8-F4E7-11E3-A5CF-F46D04D2D892

[void]

Thanks for the fsutil output.
There's nothing out of the ordinary here.

Is "Everything Service" checked in Tools -> Options -> General?

What is file FRN?

File Reference Number. Its the unique identifier for a file.
The size is definitely showing a FRN instead of the size. I'm looking into the issue..

[Devil505]

I seem to have exactly the same problem with file sizes and filenames being corrupted with the latest beta (the latest stable works fine).
The problems seem to happen regardless of using "admin mode" or "everything service".
The filename corruption doesn't seem to coincide with any specific characters - you can identify corrupted filenames in the search result by 0 byte filesize (using filesize indexing) or empty filesize (without indexing).

C:\Windows\system32>fsutil fsinfo volumeinfo v:
Volume Name : USB T3.0 N Toshiba
Volume Serial Number : 0xd8961ce3
Max Component Length : 255
File System Name : NTFS
Supports Case-sensitive filenames
Preserves Case of filenames
Supports Unicode in filenames
Preserves & Enforces ACL's
Supports file-based Compression
Supports Disk Quotas
Supports Sparse files
Supports Reparse Points
Supports Object Identifiers
Supports Encrypted File System
Supports Named Streams
Supports Transactions
Supports Hard Links
Supports Extended Attributes
Supports Open By FileID
Supports USN Journal

C:\Windows\system32>fsutil fsinfo ntfsinfo v:
NTFS Volume Serial Number : 0x32d8965bd8961ce3
Version : 3.1
Number Sectors : 0x0000000023a991ff
Total Clusters : 0x0000000023a991ff
Free Clusters : 0x000000000046327a
Total Reserved : 0x0000000000088780
Bytes Per Sector : 4096
Bytes Per Physical Sector : 4096
Bytes Per Cluster : 4096
Bytes Per FileRecord Segment : 4096
Clusters Per FileRecord Segment : 1
Mft Valid Data Length : 0x00000003be300000
Mft Start Lcn : 0x00000000000c0000
Mft2 Start Lcn : 0x0000000000000002
Mft Zone Start : 0x000000001e948660
Mft Zone End : 0x000000001e954e80
RM Identifier: C80F8B54-785D-11E3-8723-028037EC0200

[void]

Thanks for the fsutil output.

This issue looks related to advanced formatted drives.
I am working on a fix.

[void]

Does Everything 1.4.0.705b fix the issue?

[SuperDude]

YES! Thank you so much for fixing this! I'm sending a donation to you in a few minutes.

[void]

Glad to hear it's fixed.

Thanks for your support.