39755: What causes Acronis Files Connect to re-index a volume?


What causes Acronis Files Connect (formerly ExtremeZ-IP) to re-index a volume?


For performance reasons, Acronis Files Connect indexes each volume that it shares, saving the names of every file and directory contained within the volume. While the volume is normally only indexed once, re-indexing can sometimes occur if the index becomes corrupted. Acronis Files Connect will consider an index corrupted and re-index if any of the following occur:

  1. The index does not exist or cannot be read (e.g. disk error, permissions problem). If a disk error occurs at any time during the read, Acronis Files Connect will re-index the volume.
  2. The entry for a directory within the volume is itself corrupted (e.g. the entry is the wrong size, contains an incorrect signature, or is of the wrong version).
  3. The entry for a file within the volume is itself corrupted (e.g. the entry is the wrong size, or is listed as containing children [only directory entries should have children]).
  4. The "root entry" does not have exactly one child. 


You are reporting a typo in the following text:
Simply click the "Send typo report" button to complete the report. You can also include a comment.
This question is for testing whether or not you are a human visitor and to prevent automated spam submissions.
2 + 0 =
Solve this simple math problem and enter the result. E.g. for 1+3, enter 4.