What does HRESULT 0x80042516 (VDS_E_MEMBER_SIZE_INVALID) mean?

 
Previous Next
VDS_E_EXTENT_EXCEEDS_DISK_FREE_SPACE VDS_E_INVALID_DISK

VDS_E_MEMBER_SIZE_INVALID

VDS models a plex member as storage assembled from disk extents and identifies the member with the zero-based memberIdx carried by extent and input-disk records. The meaning of a member depends on the plex type: striped and parity plexes have multiple members, while simple and spanned layouts use a single member. A size that is acceptable for one topology may be inconsistent in another.

Why this state matters

This status is more specific than “not enough space.” The requested bytes can exist on every disk and still fail structural validation if one member cannot participate in the same stripe or plex geometry. The useful evidence is the member-by-member size map, including which disk extents VDS selected or was asked to use, rather than only the final desired volume size.

Diagnostic focus

  • Log every VDS_INPUT_DISK entry with diskId, ullSize, plexId, and memberIdx.
  • Identify the intended volume and plex type before interpreting the member count or member size.
  • For striped or parity layouts, compare the contribution requested from every member rather than inspecting one disk in isolation.
  • Do not rewrite the request as a smaller simple volume merely to make the HRESULT disappear; that changes the requested topology.

Technical references

VDS_INPUT_DISK · VDS_VOLUME_PLEX_PROP · VDS_VOLUME_PLEX_TYPE · IVdsPack::CreateVolume · Volume Object


Looking for a different code? Search another status or error code.