| Previous | Next |
| STATUS_LOG_FILE_FULL | STATUS_NO_TRUST_LSA_SECRET |
STATUS_TOO_LATE
The volume lifecycle has already passed the point where this write is accepted
STATUS_TOO_LATE is a sequencing status for volume teardown. The NTSTATUS text explicitly describes a write attempted after dismount, and Windows file-system control documentation also uses the status when a volume is shut down. The useful question is therefore which request raced the volume lifecycle, not whether the file data is malformed.
Trace the lock, flush, dismount and close sequence together with the writer that received this result. A background worker can retain a file object or queue work before teardown and issue it only after the volume has crossed into shutdown. A retry against the same stale handle is not a recovery strategy.
After a planned dismount, stop producing new work before the dismount request and drain or cancel queued writes. After an unexpected removal or failover, wait for the replacement volume or file-system instance to be mounted and reopen the target through its current namespace.
What to inspect
- The timestamp of
FSCTL_DISMOUNT_VOLUMEor other volume-shutdown activity. - The queueing time and dispatch time of the write that arrived too late.
- Whether the caller reused a handle or file object created before the volume transition.
References
- Microsoft: FSCTL_DISMOUNT_VOLUME
- Microsoft: FSCTL_OFFLOAD_WRITE return statuses
- Microsoft: FSCTL_SET_PERSISTENT_VOLUME_STATE
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.