| Previous | Next |
| STATUS_SVHDX_UNIT_ATTENTION_OPERATING_DEFINITION_CHANGED | STATUS_SVHDX_WRONG_FILE_TYPE |
STATUS_SVHDX_RESERVATION_CONFLICT
The command conflicts with persistent-reservation ownership
STATUS_SVHDX_RESERVATION_CONFLICT means the current SCSI initiator is not allowed to perform the command because the shared disk has an active reservation that excludes it. This is an access-control result from the shared-storage protocol, not evidence that the VHDX file has a damaged filesystem.
In a guest cluster, a reservation conflict normally directs the caller to the cluster ownership and failover path. Trying to bypass it with direct file access or unsynchronized raw SCSI can defeat the very protection that prevents two nodes from writing incompatible data.
What to verify
- Identify the command, initiator, reservation type, and reservation holder.
- Validate that the cluster service sees the expected owner before retrying an application write.
- Investigate unexpected conflicts as a potential stale node, split-brain, or configuration issue rather than a generic disk error.
References
- Microsoft: VHD Set files for guest clusters
- Microsoft: RawSCSIVirtualDisk
- T10: SCSI persistent reservations
Looking for a different code? Search another status or error code.