"V-35-503: Maximum number of volumes supported in attributes CVMVolume and CVMVolumeIoTest combined for a CVMVolDg resource is 380" appears when running cfsmntadm
Article ID: 100033246
Updated On:
Description
Error Message
Error: V-35-503: Maximum number of volumes supported in attributes CVMVolume and CVMVolumeIoTest combined for a CVMVolDg resource is 380. cvmvoldg1 already has .So cannot add vol381 to the service group sgCFS. Please use a different service group.Cause
- CVMVolume attribute definition: Name of shared volumes or volume sets. This list is used to check that the volumes or volume sets are in the correct state before allowing the resource to come online, and that the volumes remain in an enabled state.
- CVMVolumeIoTest (Optional Attribute) definition: List of volumes and volume sets that will be periodically polled to test availability. The polling is in the form of 4 KB reads every monitor cycle to a maximum of 10 of the volumes or volume sets in the list. For volume sets, reads are done on a maximum of 10 component volumes in each volume set.
CVMVolume and CVMVolumeIoTest values are passed to the online and monitor entry points of the CVMVolDg resource as command line arguments by the VCS agent framework. It has a limit of 512 maximum possible arguments. The value of 380 is the limit enforced by the cfsmntadm command, so that the limit for the CVMVolume attribute leaves room for other arguments to be passed on to online and monitor entry point.
Resolution
Check the number for CVMVolume defined for the attributes CVMVolume and CVMVolumeIoTest.
If the combined value is greater than 380, the cfsmntadm command fails to add the new CFS resource.
You could add the new volume to the CVMVolume attribute and create the CFSmount resource, separately, using the hares command. But it exposes the possibility of exceeding the agent framework limit of 512 arguments, and has potential to affect existing resources in the service group.
Option 1:
Add the new CFS resource to a different, or new, service group, using the cfsmntadm command. This allows the ability to add new CVM volumes, using the cfsmntadm command in the new service group.
Example:
Option 2:
Add a separate CVMVolDg resource to the service group for the CVMVolumes, and create the CFSMount resource, using the hares command. With this option, you won't be able to use the cfsmntadm command to add the new CFSMount in the service group.
#hares -value cvmvoldgresname CVMVolume | wc -w
# hares -value cvmvoldgresname CVMVolumeIoTest | wc -w
# hares -value cvmvoldgresname CVMVolumeIoTest | wc -w
If the combined value is greater than 380, the cfsmntadm command fails to add the new CFS resource.
You could add the new volume to the CVMVolume attribute and create the CFSmount resource, separately, using the hares command. But it exposes the possibility of exceeding the agent framework limit of 512 arguments, and has potential to affect existing resources in the service group.
Option 1:
Add the new CFS resource to a different, or new, service group, using the cfsmntadm command. This allows the ability to add new CVM volumes, using the cfsmntadm command in the new service group.
Example:
# cfsmntadm add cvmdg vol381 /381mntpoint newSG all=suid,rw
Option 2:
Add a separate CVMVolDg resource to the service group for the CVMVolumes, and create the CFSMount resource, using the hares command. With this option, you won't be able to use the cfsmntadm command to add the new CFSMount in the service group.
Issue/Introduction
When adding a new CFSMount resource, using the cfsmntadm command, the new volume is added to the CVMVolume attribute of the CVMVoldg resource. If the number of volumes in the CVMVolume, and the CVMVolumeIoTest attribute's combined value exceeds 380, the command fails.
Was this article helpful?
Yes
No
Powered by
