| Previous | Next |
| ERROR_LOG_NO_RESTART | ERROR_LOG_METADATA_INVALID |
ERROR_LOG_METADATA_CORRUPT
The CLFS metadata file is corrupt
A CLFS physical log consists of a base log file containing metadata and a set of containers holding actual log data. Metadata describes the physical log so CLFS can locate and manage the container set. Corrupt metadata can prevent the service from reconstructing the physical layout even when individual container files remain readable at the file-system level.
Preserve the .blf and every associated container before recovery. Check disk and file-system events, recent snapshot or backup restores, antivirus or filter-driver interference, and any manual movement of CLFS files. An application should not parse and rewrite CLFS metadata as if it were its own record header. For an archived log, ValidateLog is the documented consistency check before archive and after restore. For a live component log, identify whether the owner supports reset, restore, or rebuild and understand the recovery data that will be lost before removing the log.
What to inspect
- Collect the complete base-log and container set from the same point in time.
- Correlate corruption with storage errors or partial restore operations.
- Use CLFS/archive validation or the component-supported recovery path instead of editing .blf metadata.
References
- Microsoft: CLFS base log files, containers, dedicated and multiplexed logs
- Microsoft: CLFS archive mode, archive tail, and physical-log archive contexts
- Microsoft: PrepareLogArchive and active-log extent snapshots
Looking for a different code? Search another status or error code.