| Previous | Next |
| VDS_E_NO_HEALTHY_DISKS | VDS_E_DISK_CONFIGURATION_CORRUPTED |
VDS_E_CONFIG_LIMIT
This HRESULT is a metadata-capacity limit, not a shortage of free data space. The VDS pack documentation explains that the dynamic provider stores configuration in a one-megabyte LDM database and estimates roughly 1000 volumes per pack when each volume has at least one plex and one extent; the maximum falls as the disk count grows. More complex topologies consume more configuration records.
Why this state matters
Adding capacity to an existing disk or extending a free extent does not enlarge the LDM configuration database. The diagnostic should inventory pack disks, volumes, plexes, and extents so configuration complexity is visible. A design with many small volumes or highly fragmented topology can reach the limit sooner than a simple capacity calculation suggests.
Diagnostic focus
- Count disks and volumes in the dynamic pack and enumerate plexes and extents for configuration complexity.
- Distinguish LDM database capacity from disk free space and provider memory/resource failures.
- Identify automation that creates large numbers of short-lived volumes without removing obsolete configuration.
- Plan a supported topology reduction or migration instead of repeatedly extending disks and retrying the same create call.
Technical references
Pack Object · Volume Object · Volume Plex Object · VDS_DISK_EXTENT · VDS common return codes
Looking for a different code? Search another status or error code.