| Previous | Next |
| STATUS_LOG_ARCHIVE_IN_PROGRESS | STATUS_LOG_NOT_ENOUGH_CONTAINERS |
STATUS_LOG_EPHEMERAL
STATUS_LOG_EPHEMERAL distinguishes two deliberate CLFS retention models. A non-ephemeral log retains data until it is archived; an ephemeral log is allowed to discard older data to make space for new records and therefore cannot satisfy operations that depend on archive history.
This is not evidence that archiving merely has not started. The log’s retention mode is the issue. Changing an archive command or copying a subset of containers cannot retroactively make an ephemeral history complete.
What to inspect
- Check the physical log’s archive mode and determine whether the application needs durable historical recovery or only rolling log capacity.
- Keep archive operations on physical logs; an individual stream is not independently archivable.
- If retention requirements changed, plan the mode transition and archive workflow before relying on future logs as evidence.
References
- Microsoft: CLFS archive, archive tail, and ephemeral logs
- Microsoft: PrepareLogArchive, GetNextLogArchiveExtent, SetLogArchiveTail, and TerminateLogArchive
- Microsoft Open Specifications: NTSTATUS values
- Wine: independent NTSTATUS constant definitions
Looking for a different code? Search another status or error code.