1.4.0.703b: Pathname corruption with non-text chars

[Jerry]

I just started using 1.4x and WOW! David has really sped up the scanning -- by an order of magnitude at least! And I'm talking 25 attached drives, 2.2 million names, 50 terabytes total. But I am seeing very frequent corruption in the file and folder names appearing in the result list. There's no pattern that I can discern yet, but the affected names are reproducible and reappear even after I delete the Everything.db file. Below are examples of some corrupted names. Another weird thing is that the same name will be corrupted from one drive, but not corrupted from another, mirrored drive -- paths identical except for drive letter. The affected paths are long, but total length is always less than 255, and the bad character appears at various positions in the total pathname.

O in Organ replaced by Unicode box-drawing char (U+2514):

Code: Select all

Hindemith - Organ Sonatas Nos. 1-3; Distler - 4 Spielstücke from Op. 18 No. 1; Kropfreiter - Toccata Francese (Peter Hurford, ??rgan)

S in SACD replaced by non-printing char:

Code: Select all

Copland - Billy The Kid ~ Suite & Waltz; Rodeo, suite; Grofé- Grand Canyon Suite (Morton Gould & His Orchestra; Living Stereo ??ACD, 3-ch 24bit 96khz)

Space between Coro Lirico replaced by non-printing char:

Code: Select all

Petrassi - Divertimento in C; Partita; Quattro inni sacri; Coro di morti ~ Madrigale dramattico (Putelli, Malvestio, Nuvo Coro??Lirico Sinfonico Romano Orchestra Sinfonica di Roma; Franceso La Vecchia)

[therube]

Does the diacritics setting make any difference, search Match Diacritics?
How about Fast ASCII, Options | General | Search?

[Jerry]

Does the diacritics setting make any difference, search Match Diacritics?
How about Fast ASCII, Options | General | Search?

No effect after changing those settings and repeating search. And the problem also appears in paths that don't contain any diacritics at all.

[void]

I'm aware of the issue and am working on a fix.

Does the issue occur if you disable size indexing from Tools -> Options -> NTFS?

[Jerry]

Does the issue occur if you disable size indexing from Tools -> Options -> NTFS?

Yes, problem is still there if I disable size indexing. In the first corrupted name, a different box-drawing character now appears, but in the same position as before.

[SuperDude]

I still have name corruption as well. I'm also still getting incorrect file sizes for some files, as seen here:

http://i.imgur.com/RZ93zGK.jpg

and here:

http://i.imgur.com/lQJTU22.jpg (as you can see, there is nothing showing under Size, Date Modified, and Date Created)

* These corruptions occur if Index File Size is enabled or not.

* These name/size corruptions only appear for files that are on my 3 TB Western Digital USB 3.0 external hard drive.
None of my other drives have these problems.

[therube]

(Link to your earlier post, Index file size causes file size corruption.)

[void]

This issue should be fixed in "Everything" version 1.4.0.705b

[Jerry]

I am still seeing the name corruption, exactly as before, with 1.4.0.705b. None of the extra indexing options are checked.

[therube]

(I'm thinking your issue & superdude's are dfiferent, & what was fixed in 705 was superdude's?)

[void]

705b has fixed name corruption for some users, I'm still looking into the issue..

[Jerry]

UPDATE: 705b fixed my naming corruption problem after all. I had been running a different version of the Everything service from another installation area and that was causing me not to see the fix.