V1.3.2.644 continually scans/rebuilds database

[nmc]

Hi, just updated from 1.3.1.636b to 1.3.2.644b. The latest version seems to continually scan and rebuild the database.

The service is installed. It seems to happen regardless of whether there are folders being scanned on a remote machine.

Builds in between 636b and 644b crash (duplicate folder bug?).

I've tried uninstalling/reinstalling. There's no db to delete as it never gets around to writing one.

What should I try next?

[void]

Thanks for the bug report.

Could you please send some debug output when Everything is continually rebuilding?

[nmc]

Here's the debug log (attached).
I can post some more if I can capture more (it scrolls past pretty quickly, and makes it hard to select & copy).

In this log, Everything is scanning only the local C: and D: drives (same hard disk, different partitions).

[void]

Thanks for the debug output.

The service is posting 'out of date' events.

Does the problem occur if you run Everything as administrator without the service?
If so what is displayed in the debug console?

You can stop the service from Start -> Control Panel -> Administrative Tools -> Services.
Find the Everything service, right click and click Stop.

[nmc]

Thanks David.

Running everything as admin, and with the service stopped produces the same rescanning behaviour.
Debug log 2 attached.

If I don't run it as admin (with the service still stopped), I:
i) get a status bar message stating "querying USN change journal" for local drives C:, D:, and R: (forgot about the last one before, it's the recovery partition).
ii) after that, I see icons for C:, D:, and R:, and no other files.

[void]

Thanks for the debug output...

Very strange, failure to create the USN Journal with no error code returned from the NTFS driver.
the R: drive is the problem drive. This might have something to do with the fact that it is a recovery volume.

I will improve Everything so the continuous scanning doesn't occur in the next release.
When there is a failure like this, only the drive letters will show in the result list.

From an administrative command prompt, what is displayed by running the following commands:

Code: Select all

fsutil fsinfo volumeinfo R:
fsutil fsinfo ntfsinfo R:
fsutil usn createjournal m=32768 a=4096 R:

To stop Everything indexing the R: drive:

• In Everything, from the Tools menu, click options.
• Click the NTFS tab.
• Select the R: drive.
• Uncheck Include in database.
• Click OK.

[nmc]

Here's the output of the fsutil commands:

Volume Name : Recovery
Volume Serial Number :
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



---------
NTFS Volume Serial Number :
Version : 3.1
Number Sectors : 0x00000000023e5866
Total Clusters : 0x000000000047cb0c
Free Clusters : 0x0000000000000bec
Total Reserved : 0x0000000000000000
Bytes Per Sector : 512
Bytes Per Physical Sector : 4096
Bytes Per Cluster : 4096
Bytes Per FileRecord Segment : 1024
Clusters Per FileRecord Segment : 0
Mft Valid Data Length : 0x0000000000a40000
Mft Start Lcn : 0x00000000000c0000
Mft2 Start Lcn : 0x0000000000000002
Mft Zone Start : 0x00000000000bc980
Mft Zone End : 0x00000000000bd4c0
Error: Transaction support within the specified resource manager is not started or was shut down due to an error.

No output from the last command.

Hmm. Usually I don't include the R: drive as there's nothing much on it.

Thanks for your help with this; I'll keep an eye on the behaviour in case I can characterise it better.

And if you're ever in Canberra, let me know and I'll buy you a beer

[void]

Thanks for the file system info.
Writing to this volume is probably disabled, that is why the USN Journal would fail to create.

1.3.2.645b should fix the issue.

[nmc]

Apologies for the late response.

Yes, this and subsequent betas work perfectly. Thanks for your help