[Invalid] 702: All Files Are Being Listed Twice

[therube]

NOTHING TO SEE HERE, EXCEPT FOR USER ERROR

-------

ALL of the files on my (local) W: drive are showing, twice, duplicated.
(Happen to be seeing it now, don't believe it was showing like that yesterday?)

Could it be the drive went to sleep, & on awakening ...?


Otherwise my (local) X: drive has been suspect (bad) for a long time now, (fairly) regularly getting "delayed write" type error messages.

When this occurs, it has also affected Everything (1.3.4), causing Everything to rescan all my drives.


I didn't see anything of note with -debug (not that I'm sure what I should be noting ).

[therube]

Everything 1.3.4 displays things correctly.

[therube]

Just some junk from MyEventViewer:

Code: Select all

17224	System	Warning	10/01/2015 12:12:52 PM	Ftdisk	2	57		RUBENXP43	40	284	The system failed to flush data to the transaction log. Corruption may occur.  	

17223	System	Error	10/01/2015 12:12:34 PM	PlugPlayManager	0	12		RUBENXP43	4	292	The device 'ST3400633A' (IDE\DiskST3400633A______________________________3.AAH___\5&160661fe&0&0.1.0) disappeared from the system without first being prepared for removal.  	

17222	System	Warning	10/01/2015 12:12:24 PM	Disk	0	51		RUBENXP43	144	284	An error was detected on device \Device\Harddisk0\D during a paging operation.  	

ST3400633A is my X: drive.
W: (along with C: E: L: M: & O:) are partitions on a different physical disk.

[therube]

Ah ... what I didn't realize...

Long ago I had started a different -instance of Everything, looking at a NAS drive.
That instance (turns out) had been hidden in my System Tray for a long time now.

Yesterday, before I put in 702, I "quit" Everything (but not my NAS instance), then:

.everything -uninstall-service
.copied 702 over
.everything -install-service

So I was (unknowingly) running two versions of Everything, & possibly the Service change & second instance of Everything has some bearing ... or not?

[therube]

Cleaned that part up...

move location of everything.db from %APPDATA% to C:\Everything\
Quit all Everything
uninstall Service
install Service

Fire up 702, & the situation persists.


Force Rebuild & still the same.


I've (had) enabled:

Index file size
Index folder size
Index date modified
Fast size sort


Win XP SP3

[therube]

A new (clean, so all settings at defaults) instance of Everything works.

everything.exe -instance 702702

(Maybe I'll keep it open & see what it looks like later...)

[void]

If the issue does occur again, please check if the W: drive is listed twice in Tools -> Options -> NTFS.

Please check for other strange volumes listed as a GUID volume in Tools -> Options -> NTFS.
For example: \\?\volume{xxx}. Maybe the OS is seeing the drive as a completely new volume..

[therube]

> if the W: drive is listed twice in Tools -> Options -> NTFS.

No.

> check for other strange volumes listed as a GUID volume in Tools -> Options -> NTFS.

Prior to it scrolling off from -debug, the listing of the GUID's look OK, drive letter/unique ID for each.


Oh, forgot to mention, I also have an A: drive that shows up - under NTFS.
It's shown as "Removable Disk (A:)".
Now I have no physical floppy,
Though I do have a particular Flash drive that presents itself as both an A: drive & some other (drive letter).
And to the OS [XP] (from what I'm recalling), A: is treated as if it were a floppy (at the time, quite a while ago, could be used to install BIOS updates or similar) with the remainder of the drive (separate drive letter) being treated as a "normal" USB flash drive.
And I assume I've got A: drive enabled in the BIOS - just been that way, for ages.

Code: Select all

add volume: path: A: guid: \\?\Volume{0d6168aa-91d0-11de-8117-0019664ae8cf}
add volume: path: C: guid: \\?\Volume{80b65e57-1ead-11dd-a4f0-806d6172696f}
add volume: path: E: guid: \\?\Volume{80b65e61-1ead-11dd-a4f0-806d6172696f}
add volume: path: L: guid: \\?\Volume{80b65e59-1ead-11dd-a4f0-806d6172696f}
add volume: path: M: guid: \\?\Volume{80b65e5a-1ead-11dd-a4f0-806d6172696f}
add volume: path: O: guid: \\?\Volume{80b65e5b-1ead-11dd-a4f0-806d6172696f}
add volume: path: W: guid: \\?\Volume{80b65e5c-1ead-11dd-a4f0-806d6172696f}
add volume: path: X: guid: \\?\Volume{80b65e5d-1ead-11dd-a4f0-806d6172696f}

A: is shown as a "drive type 2" (all the others are "3").

Code: Select all

volume \\?\Volume{0d6168aa-91d0-11de-8117-0019664ae8cf}: drive type 2

[therube]

Cleaned that part up...

By that I meant that I closed ALL instances of Everything, removed the service, copied in 702, started the service, & then started Everything.

At that point, using the same "instance" (in this case, "default" if you will, IOW, not a "named" instance) of Everything ...

Fire up 702, & the situation persists.
Force Rebuild & still the same.

That's again with my "default" (non-named instance) of Everything.

A new (clean, so all settings at defaults) instance of Everything works.

It was not until I did that, that W: displayed correctly.


(I'll see what 703 does in a bit...)

[therube]

Comparing .ini's:

I was going to say ... BUT I DON'T HAVE TO.

AH, DUMY!

Code: Select all

folders="W:\\"

I must have set that up a bit ago, disabling W: in NTFS, but when I put in 702 in, it must have picked it (W:) up, automatically, hence the duplicates.

DUMY!
Sorry for the spam.