| Previous | Next |
| STATUS_LOG_METADATA_FLUSH_FAILED | STATUS_LOG_APPENDED_FLUSH_FAILED |
STATUS_LOG_INCONSISTENT_SECURITY
STATUS_LOG_INCONSISTENT_SECURITY means the base log and one or more containers do not present a security state that CLFS can accept as a consistent physical log. Container security matters because the base .blf file and the data containers operate as one log set.
The result is not equivalent to a single access-denied response. It asks you to compare the security descriptors and ownership context across the entire set, including how containers were created and whether paths were later moved or restored under different ACLs.
What to inspect
- Enumerate every container associated with the base log and capture owner, DACL, inheritance, and share settings consistently.
- Compare the caller context that created containers with the intended security attributes of the base log.
- Repair access control as a coordinated set after preserving evidence; do not loosen ACLs broadly merely to make one open succeed.
References
- Microsoft: CLFS base-log and container security attributes
- Microsoft: CreateLogFile sharing and security parameters
- Microsoft Open Specifications: NTSTATUS values
- Wine: independent NTSTATUS constant definitions
Looking for a different code? Search another status or error code.