| Previous | Next |
| ERROR_LOG_SECTOR_PARITY_INVALID | ERROR_LOG_BLOCK_INCOMPLETE |
ERROR_LOG_SECTOR_REMAPPED
The physical log contains a remapped-sector condition
CLFS organizes the physical log into containers and sector-aligned log blocks. A remapped-sector status belongs to that physical storage layer and is distinct from an invalid client record or an LSN outside the active range. The important diagnostic question is whether the remapping state reflects a recoverable CLFS write-history condition, a storage-layer relocation, or a log set whose physical metadata no longer matches the containers currently present.
Inspect the physical log as a unit and correlate the timestamp with storage changes, snapshot restores, volume movement, or replacement of individual container files. A log client normally addresses records by LSN and should not attempt to reinterpret or repair sector mappings itself. If the log is used for recovery, preserve it before resetting the owner. If it is a disposable diagnostic log, recreate it through the component that owns it rather than deleting a single container and leaving the base log metadata behind.
What to inspect
- Identify recent restore, clone, snapshot, or container-file replacement operations on the volume.
- Collect the .blf and all containers before allowing the owning service to recreate the log.
- Separate a physical CLFS condition from application record corruption by checking whether CLFS can open and enumerate the log.
References
- Microsoft: CLFS base log files, containers, dedicated and multiplexed logs
- Microsoft: dedicated CLFS logs and physical log storage
- Microsoft: clfsw32 API reference
Looking for a different code? Search another status or error code.