Question:

What causes ExtremeZ-IP to re-index a volume?

Answer:

For performance reasons, ExtremeZ-IP 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. ExtremeZ-IP 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, ExtremeZ-IP 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.

Tags: ExtremeZ-IP