| Previous | Next |
| VDS_E_INVALID_BLOCK_SIZE | VDS_E_NO_EXTENTS_FOR_PLEX |
VDS_E_PLEX_SIZE_INVALID
VDS_VOLUME_PLEX_PROP.ullSize reports plex size, and Microsoft explicitly requires a plex to be at least as large as its containing volume. That follows the VDS data model: a plex represents one complete copy or layout of the volume data. A smaller plex cannot cover the logical address range exposed by the volume.
Why this state matters
This status should be analyzed with volume and plex properties plus the plex extent map. Summing raw disk capacity is not enough because only extents assigned to the plex contribute to its size. A stale provider cache, incomplete topology update, or malformed create/repair input can leave the reported relationship inconsistent. Preserve object IDs and sizes before any refresh so the original mismatch remains observable.
Diagnostic focus
- Capture the containing volume size and
VDS_VOLUME_PLEX_PROP.ullSizefor every plex. - Enumerate the plex extents and verify their mapped sizes against the plex property rather than total disk capacity.
- Identify whether the mismatch followed create, extend, repair, mirror, or migration activity.
- If refresh changes the values, retain both snapshots and treat the original state as a provider/cache synchronization clue.
Technical references
VDS_VOLUME_PLEX_PROP · IVdsVolumePlex::QueryExtents · Volume Object · MS-VDS storage object relationships · IVdsVolumePlex
Looking for a different code? Search another status or error code.