What does HRESULT 0xC0380047 (ERROR_VOLMGR_VOLUME_LENGTH_INVALID) mean?

ERROR_VOLMGR_VOLUME_LENGTH_INVALID

Read the code at the owning storage layer: volmgr volume length invalid

ERROR_VOLMGR_VOLUME_LENGTH_INVALID has unsigned value 0xC0380047. In the volmgr layer, the operation is rejected because the requested logical length is incompatible with the supplied extents or volume layout type. Diagnosis should follow logical volume geometry and the disk extents that realize it through one controlled state transition.

Diagnosis of this result should begin with the object model and generation current at the failure. A later successful enumeration may describe a replacement object and cannot retroactively validate the rejected request.

Build a trustworthy incident record

When it is followed by a secondary cleanup failure, store both codes with timestamps and retain this one as the initiating result.

Controlled comparison

1. Capture the API parameters and object map that led to this result; do not begin with cleanup.
2. Build a passing control with the same disks or image copy and preserve volume ID, requested length, sector sizes, extent table, plex/member counts, disk health and the exact VM_VOLUME_LAYOUT buffer.
3. Run the narrow transition described here: serialize the exact VM_VOLUME_LAYOUT buffer, validate every count and Size field, and compare it with a layout produced by a known-good management API.
4. Compare resulting IDs, counts, health and ownership to prove the caller crossed the result invariant rather than suppressing it.

ERROR_VOLMGR_VOLUME_LENGTH_NOT_SECTOR_SIZE_MULTIPLE describes a nearby but different storage condition; this result indicates that the requested logical length is incompatible with the supplied extents or volume layout type.

Mechanism-specific note

Validate logical length against the sum and mapping of supplied extents, not only against free space. For striped or mirrored layouts, the relationship is not a simple sum. Save the requested length and a normalized interval map so overlaps, gaps and arithmetic overflow can be reviewed independently of the live disks.

Completion criteria

Rebuild the layout from enumerated objects and checked arithmetic rather than patching one serialized field; validate counts, indices, sizes, alignment and overflow before submission. The repair is incomplete until a fresh enumeration and new handle observe the corrected state.

• the first retry uses newly enumerated identifiers rather than cached handles.
• The durable metadata or provider state agrees with the success returned after it.
• A second run after close/reopen does not recreate the rejected condition.
• the nearby ERROR_VOLMGR_VOLUME_LENGTH_NOT_SECTOR_SIZE_MULTIPLE path remains separately testable and separately logged.

Technical references

• Microsoft: COM error codes for VOLMGR, VHD and SDIAG — documents the supported management path relevant to this HRESULT.
• Microsoft: Virtual Disk Service object model — defines the volmgr objects used to interpret it.
• Microsoft: Pack object — primary API or object-model reference.
• Microsoft: Virtual Disk Service common return codes — use this source to verify volmgr state and parameters.