HNAS Dedupe Job Failing with "Failed to Open an Existing Index"

Environment

• Hitachi Network Attached Storage (HNAS)

Resolution

1. If this alert has only occurred once and the file system is not at immediate risk of filling up, wait 24 hours for the next scheduled run of deduplication. Depending on the specific issue in regards to open the deduplication index, it is possible that this is a one-time issue that will resolve on its own upon the next deduplication job.
2. If the errors are persisting, please contact support to request a HNAS DEV password. When opening the SR, please provide the output of HNAS CLI command: pn all getmacid
3. After support has provided you with the DEV password, please run the following to enable/log-in as DEV user and correct the inconsistent dedupe index.
   1. devuser on
   2. logout
   3. login dev <INSERT DEV PASSWORD>
   4. fs-dedupe-index-invalidate <INSERT FILESYSTEM NAME> incremental
4. Wait for the next scheduled run of this dedupe job and verify that the dedupe now completes successfully. If you are still running into any issues or had problems running the DEV command to clear the index, please contact support for next steps.

Cause

The HNAS uses an index for incremental dedupe jobs. If the HNAS is having issues accessing this index, this can cause dedupe to fail so the resolution is to invalidate that problematic index and allow the HNAS to build a new index upon the next deduplication job.