Corpus of Everything index consist of more than a million duplicates of two files

[springfeld]

Hi,

I found nearly nothing with Everything, because my Everythings index corpus on my personal computer consists of two files:

"C:\Users\udosj\OneDrive\Dokumente\Berufsausbildung\Berufsschule\Fächer\Schulblöcke\16 IPv6, VPN, WLAN, VoIP\IP-Telefonie\„Voice over Internet Protocol“ VoIP.mmap" (984081 entries)
"C:\Users\udosj\source\repos\RssBandit\docs\BanditHelp\en\!SkinSubFolder!" (207863 entries)

First one is a mind map file not in active use but stored within in my onedrive. Second one is a source file of my RSS Feed Reader just used to compile the software once. So active usage/file table blockage seems not the problem.

Everythings build is 1.4.1.1022 (x64).

Started with /debug option and found several hints. Can provide via PM.

How can i help to identify the problem?

Kind regards,

Udo

[therube]

Not really sure what you're saying/asking... (& I know nothing of onedrive).


Though,

Tools | Options | Indexes | Exclude -> Enable exclude list

, then enter those two folders might be a start?

[void]

The Everything database has been filled with zeroes.

Please try a fresh reindex:

• Exit Everything (File -> Exit)
• In Windows Explorer, type in the following address and press ENTER:
  %LOCALAPPDATA%\Everything
• Delete your Everything.db
• Restart Everything.

[Stryp]

The Everything database has been filled with zeroes.

Please try a fresh reindex:

• Exit Everything (File -> Exit)
• In Windows Explorer, type in the following address and press ENTER:
  %LOCALAPPDATA%\Everything
• Delete your Everything.db
• Restart Everything.

This has been frequently happening to me, too. Usually once every two weeks or so, I notice it. In my case, I exported the corrupt .esu and it's 3.4 million lines of the same file. Can I help with diagnosing this issue somehow? I have turned on debug logging, if I notice it, is there a way to trace it back to when the file list got corrupted and why?

[void]

This issue occurs when the Everything.db is filled with zeroes.
This can happen when buffers are not flushed to disk.

If you have another drive, please try changing your Everything database location to a different drive:

• In Everything, from the Tools menu, click Options.
• Click the Indexes tab on the left.
• Change the Database location to another drive.
  For example:
  D:\Everything
• Click OK.

Please make sure Windows is shutting down gracefully.

Please try Everything 1.5.
Everything 1.5 has a backup.db and CRC checks to prevent corruption.

I have turned on debug logging, if I notice it, is there a way to trace it back to when the file list got corrupted and why?

Not for Everything 1.4 unfortunately.
An Everything.db filled with zeroes is a valid db.
Everything 1.5 will log CRC check failures.