| Previous | Next |
| ERROR_COULD_NOT_RESIZE_LOG | ERROR_LOG_DEDICATED |
ERROR_LOG_MULTIPLEXED
The target is a multiplexed CLFS log rather than a dedicated stream
CLFS supports dedicated logs and multiplexed physical logs. A multiplexed log can contain multiple logical streams identified by stream names after the physical log name. Because physical containers and shared space belong to the underlying log, some direct physical-log write or management operations are not valid through a logical stream as though it owned the log exclusively.
Inspect the log-name syntax passed to CreateLogFile and determine whether the handle represents the physical log or a named stream. Do not remove the stream suffix or switch APIs blindly: a physical-log operation can affect other streams sharing the containers. For sizing, archive, or container maintenance, use the documented physical-log handle and coordinate all clients. For record appends, use the logical stream and its marshalling context. This separation is central to diagnosing multiplexing errors.
What to inspect
- Parse the CLFS log name into physical log and optional stream name.
- Determine whether the failing API operates on a logical stream or the shared physical log.
- Coordinate physical-log maintenance with every stream that shares the multiplexed log.
References
- Microsoft: CLFS base log files, containers, dedicated and multiplexed logs
- Microsoft: clfsw32 API reference
- Microsoft: CLFS archive mode, archive tail, and physical-log archive contexts
Looking for a different code? Search another status or error code.