Node fails to join a Cluster Volume Manager cluster because vxconfigd cannot find a disk

Article:TECH37313  |  Created: 2005-01-09  |  Updated: 2006-01-09  |  Article URL http://www.symantec.com/docs/TECH37313
Article Type
Technical Solution

Product(s)

Environment

Issue



Node fails to join a Cluster Volume Manager cluster because vxconfigd cannot find a disk

Error



vxvm:vxconfigd: V-5-1-8222 slave: missing disk 1104366468.5014.jacaranda
vxvm:vxconfigd: V-5-1-7830 cannot find disk 1104366468.5014.jacaranda
vxvm:vxconfigd: V-5-1-4109 -1 returned from volcvm_establish
vxvm:vxconfigd: V-5-1-10123 cluster_establish: (222) Cannot find disk on slave node

Solution



When a node wants to join a Cluster Volume Manager cluster, vxconfigd will first receive a list of disks from the Cluster Volume Manager master.  This list of disks are those already imported on the other nodes as Cluster Volume Manager shared disk groups.  vxconfigd will try to locate them on the local node.  

Note that not only the disks have to be physically present on the local system, their attributes have to match those sent by the Cluster Volume Manager master.  The disks must be present and meet all the following conditions:

1. The disk is shared
2. The disk is ready
3. The clusterid must match that of the VERITAS Cluster Sever (tm) cluster (main.cf)

# vxdisk list sdc1t12d0s6
clusterid: sunjac                                        <<< clusterid
flags:     online ready private foreign shared autoimport   <<< ready and shared

If vxconfigd fails to find a disk, it will not join the Cluster Volume Manager cluster and display the following error messages (deonted by vxconfigd:) together will messages from other components:

Feb  9 15:13:33 jacaranda vxfen: [ID 214757 kern.notice] NOTICE: VCS FEN INFO V-11-1-34 The ioctl VXFEN_IOC_CLUSTSTAT returned 0
Feb  9 15:13:37 jacaranda gab: [ID 316943 kern.notice] GAB INFO V-15-1-20036 Port u gen   3d5058 membership 0
Feb  9 15:13:37 jacaranda gab: [ID 674723 kern.notice] GAB INFO V-15-1-20038 Port u gen   3d5058 k_jeopardy ;1
Feb  9 15:13:37 jacaranda gab: [ID 513393 kern.notice] GAB INFO V-15-1-20040 Port u gen   3d5058    visible ;1
Feb  9 15:13:42 jacaranda gab: [ID 316943 kern.notice] GAB INFO V-15-1-20036 Port v gen   3d5052 membership 01
Feb  9 15:13:47 jacaranda gab: [ID 316943 kern.notice] GAB INFO V-15-1-20036 Port w gen   3d5058 membership 01

Feb  9 15:13:42 jacaranda vxvm:vxconfigd: [ID 456610 daemon.notice] V-5-1-7900 CVM_VOLD_CONFIG command received
Feb  9 15:13:42 jacaranda vxvm:vxconfigd: [ID 699813 daemon.notice] V-5-1-7899 CVM_VOLD_CHANGE command received
Feb  9 15:13:42 jacaranda vxvm:vxconfigd: [ID 322665 daemon.notice] V-5-1-7961 establishing cluster
Feb  9 15:13:48 jacaranda vxvm:vxconfigd: [ID 874742 daemon.warning] V-5-1-8222 slave: missing disk 1104366468.5014.jacaranda
Feb  9 15:13:48 jacaranda vxvm:vxconfigd: [ID 857411 daemon.warning] V-5-1-7830 cannot find disk 1104366468.5014.jacaranda
Feb  9 15:13:48 jacaranda vxvm:vxconfigd: [ID 778436 daemon.error] V-5-1-4109 -1 returned from volcvm_establish
Feb  9 15:13:48 jacaranda vxvm:vxconfigd: [ID 172191 daemon.error] V-5-1-10123 cluster_establish: (222) Cannot find disk on slave node
Feb  9 15:13:48 jacaranda vxvm:vxconfigd: [ID 700632 daemon.error] V-5-1-8039 kernel_fail_join() : master_takeover is 0
Feb  9 15:13:48 jacaranda vxvm:vxconfigd: [ID 100000 daemon.error]

Feb  9 15:13:48 jacaranda vxio: [ID 535583 kern.warning] WARNING: VxVM vxio V-5-0-164 Failed to join cluster sunjac, aborting
Feb  9 15:13:48 jacaranda gab: [ID 397130 kern.notice] GAB INFO V-15-1-20032 Port u closed
Feb  9 15:13:48 jacaranda gab: [ID 397130 kern.notice] GAB INFO V-15-1-20032 Port v closed
Feb  9 15:13:48 jacaranda vxvm:vxconfigd: [ID 741513 daemon.notice] V-5-1-7901 CVM_VOLD_STOP command received
Feb  9 15:13:48 jacaranda gab: [ID 397130 kern.notice] GAB INFO V-15-1-20032 Port w closed

Note that in VERITAS Volume Manager (tm) 3.5 and below, by default,  vxconfigd will send its messages to the console device only (see the linked TechNote 275120 for details).





Legacy ID



275122


Article URL http://www.symantec.com/docs/TECH37313


Terms of use for this information are found in Legal Notices