Data Deduplication full garbage collection phase 1 on volume "%1" encountered an error %2 while processing file %3. Phase 1 will need to be aborted since garbage collection of file-related metadata is unsafe to continue on file errors. %4
Data Deduplication failed to dedup file "%1" with file ID %2 due to non-fatal error %3 %4. Note: You can retrieve the file ...
Data Deduplication failed to initialize oplock as the file appears to be missing. File ID: %1 File name: "%2" Error: %3 %4 ...
Data Deduplication full garbage collection could not achieve maximum space reclamation because delete logs for data container ...
Data Deduplication full garbage collection phase 1 (cleaning file related metadata) on volume "%1" failed with error: %2. ...
Data Deduplication full garbage collection phase 1 on volume "%1" encountered an error %2 while processing file %3. Phase ...
Data Deduplication Garbage Collection encountered a delete log entry with an invalid stream map signature for stream map ...
Data Deduplication has detected a corrupt corruption metadata file on the store at %1. Please run deep scrubbing on the volume. ...
Data Deduplication has disabled the volume %1 because it has discovered too many corruptions. Please run deep scrubbing on ...
Data Deduplication has disabled the volume %1 because there are missing or corrupt containers. Please run deep scrubbing ...