What is the maximum number of objects allowed in a disk group?
Article ID: 100017908
Updated On:
Description
Error Message
vxvm:vxmk: ERROR: no more space in disk group configurationResolution
The answer to this depends on the size of the disk group's configuration database. Each object in the disk group (be it volume, plex, subdisk, or disk) takes 256 bytes of configuration space. To find the size of the configuration database, run vxdg list . Then, look for the smallest configuration copy.
Here is an example:
# vxdg list newdg
Group: newdg
dgid: 886021133.2297.joke
import-id: 0.2396
flags:
copies: nconfig=default nlog=default
config: seqno=0.6521 permlen=795 free=772 templen=13 loglen=120
config disk c1t0d1s2 copy 1 len=1456 state=clean online
config disk c2t1d0s2 copy 1 len=795 state=clean online
log disk c1t0d1s2 copy 1 len=220
log disk c2t0d1s2 copy 1 len=120
In this case, the smallest configuration copy is 795 sectors. Multiply this by 2 to find the number of 256-byte records which can be stored in it, so this would be 1590 records.
To find out approximately how many records are being used, run the vxprint command, use grep to remove blank lines, and then use the wc (word count) command to count the objects in the disk group. In the following case about 45 records of the 1590 for which there is space are being used:
# vxprint -g newdg | grep . | wc -l
45
If there is no space left to create objects, there will be an error similar to this:"vxvm: vxmk: ERROR: no more space in disk group configuration". The only way to increase the configuration copy at this time is to use the vxdisk command to re-initialize the disks with larger private regions using the privlen=xxx option (see the man page for details or article # 180681).
Note: This cannot be done with data on the disks since it is not an online operation.
Another solution is to move the objects into another disk group. Please see article #190423 for instructions.
Here is an example:
# vxdg list newdg
Group: newdg
dgid: 886021133.2297.joke
import-id: 0.2396
flags:
copies: nconfig=default nlog=default
config: seqno=0.6521 permlen=795 free=772 templen=13 loglen=120
config disk c1t0d1s2 copy 1 len=1456 state=clean online
config disk c2t1d0s2 copy 1 len=795 state=clean online
log disk c1t0d1s2 copy 1 len=220
log disk c2t0d1s2 copy 1 len=120
In this case, the smallest configuration copy is 795 sectors. Multiply this by 2 to find the number of 256-byte records which can be stored in it, so this would be 1590 records.
To find out approximately how many records are being used, run the vxprint command, use grep to remove blank lines, and then use the wc (word count) command to count the objects in the disk group. In the following case about 45 records of the 1590 for which there is space are being used:
# vxprint -g newdg | grep . | wc -l
45
If there is no space left to create objects, there will be an error similar to this:"vxvm: vxmk: ERROR: no more space in disk group configuration". The only way to increase the configuration copy at this time is to use the vxdisk command to re-initialize the disks with larger private regions using the privlen=xxx option (see the man page for details or article # 180681).
Note: This cannot be done with data on the disks since it is not an online operation.
Another solution is to move the objects into another disk group. Please see article #190423 for instructions.
Issue/Introduction
What is the maximum number of objects allowed in a disk group?
Was this article helpful?
Yes
No
Powered by
