Error Message

VxVM vxdg ERROR V-5-1-4597 vxdg join  failed : Configuration too large for configuration copies

If the tagmeta feature is enabled (option which places a copy of the VxVM configuration database and kernel log on all the disks in a diskgroup that share a given tag on the disk) it creates tagmeta info records which are being stored persistently into configuration database.

During split operation, tagmeta info records are being copied into both the source and target disk group and during join operation tagmeta info records are not cleaned up and hence tagmeta info records are doubled after every split and join operation which consumes the configuration copies and can lead to join failure with error "Configuration too large for configuration copies".

The DGSJ operations can be slowed down further after every split and join operation due to increasing number of tagmeta info records which are being persistently updated into the configuration database on the disk.

How to identify if a system is running into this issue :

----------------------------------------------------

1) In VxVM environment, if tagmeta is enabled on a disk group and disk group split and join (DGSJ) featured is used, user can easily hit this issue.

2) Monitor the tagmeta type info records after every DGSJ operation. If it's doubled after every split and join operation then user will hit this issue after few more DGSJ operations.

The Command Line examples which can help user to identify if tagmeta is involved:

   # vxdg –q listmeta

   # vxprint –g -i –m | grep “type=102”

NOTE :  "type=102" means the info record is of type 'tagmeta' and tagmeta is enabled on the disk group.

To address this issue, remove the VxVM Info records that were mistakenly duplicated by 'vxdg join', to reduce config size and to vastly improve the SPLIT/JOIN times.

By turning off the TAGMETA objects, the associated Inforec object is also removed from the VxVM configuration:

1) Identify which TAGMETA tags exist on a given diskgroup (tagdg):

# vxdg listmeta tagdg
DISK GROUP      NAME                               NCONFIG      NLOG

tagdg           dgconfig                                    0           0

tagdg           dgconfig                                    0           0

tagdg           dgconfig                                    0           0

tagdg           dgconfig                                    0           0

2) For each of these duplicated tagmeta objects we need to run (removing "dgconfig" tag from tagdg) :

# vxdg -g tagdg set tagmeta=off tag=dgconfig
 

NOTE: When this 'duplicate tag' issue is hit, it's expected that the above command will need to be re-run for each of the duplicates. If there are many duplicates to remove, this cleanup may take a few hours.

This can be scripted:

# while [ $? == 0 ]; do  vxdg -g tagdg set tagmeta=off tag=dgconfig; done

3) When the 'tagmeta=off' has been run for all of the tags, it is a good idea to then look that all of the associate Inforecords have also been removed.

Check this with:

# vxprint -g -i -m | grep "type=102"