Facing error while adding CFS mounts via "cfsmntadm" command

book

Article ID: 100021374

calendar_today

Updated On:

Cause

If a CFSMount resource is added to the cvm group using cfsmntadm, and a node was rebooted, the cvm group can become faulted. This was traced down to the missing dependency between the newly added CFSMount resource and vxfsckd and between the CVMVolDg resource and cvm_clus. cfsmntadm does not add these dependencies and user could end with a config which would not come up properly on reboots. As a result, the cfsmntadm tool was updated to not allow adding any CFSMount resources to the cvm service group to avoid these kind of issues.

cvm service group is an infrastructure service group. No customer defined resources should be added in to cvm service group. Veritas Engineering limited the functionality in the cfsmntadm script. However, CFSMount resource can still be added using ha command but this is not a good practice.

Resolution

Create new service group for the CFSMount resources or add them to existing parallel service group by running:

# /opt/VRTS/bin/cfsmntadm add shareddg svol1 /share01 cfsSG all=rw


cfsSG service group is created (if it doesn't exist) and the CFSMount, CVMVolDg resources are added to this service group.
 

Additionally, if the CFSMount resource is a nested mount point, it needs to be in the same service group as the parent mount point resource.  Alternatively, you can create the resource manually in a new service group and link the dependent service groups.

 

Issue/Introduction

In Storage Foundation 5.0MP3 and above, adding a CFS mount point via "cfsmntadm" command to cvm service group would fail with the following message:
# /opt/VRTS/bin/cfsmntadm add shareddg svol1 /share01 cvm all=rw

Error: V-35-376: cfsmntadm: cvm Incompatible Service Group