| Previous | Next |
| STATUS_VOLMGR_TOO_MANY_NOTIFICATION_REQUESTS | STATUS_VOLMGR_UNEXPECTED_DISK_LAYOUT_CHANGE |
STATUS_VOLMGR_TRANSACTION_IN_PROGRESS
A concurrent layout transaction is still active
STATUS_VOLMGR_TRANSACTION_IN_PROGRESS is a serialization status for configuration changes. Volume Manager already has a transaction in process and will not begin the conflicting operation now.
Dynamic-disk configuration is replicated in LDM metadata, and one volume operation can affect multiple disk extents or pack objects. Treating those changes as independent writes would risk an inconsistent topology, so management code must respect the active transaction boundary.
Find the operation that owns the transaction and wait for its definitive result. A UI or service timeout does not prove the storage transaction ended; refresh topology and task state before deciding to retry, especially after long-running migration, recovery, or layout updates.
What to inspect
- Correlate the status with currently active disk-management tasks and the exact volume or pack they modify.
- Prevent parallel workers from issuing topology changes against the same Volume Manager state.
- After the owning transaction completes, re-enumerate disks and volumes before rebuilding the next request.
References
- Microsoft VOLMGR entry for STATUS_VOLMGR_TRANSACTION_IN_PROGRESS.
- Microsoft description of replicated LDM configuration on dynamic disks.
- MS-DMRP behavior for asynchronous disk and volume management tasks.
Looking for a different code? Search another status or error code.