Error Message

Sample output from the vxconfigd generated core file


# pstack /core
core '/core' of 5011:   vxconfigd -d
-----------------  lwp# 1 / thread# 1  --------------------
 0013e708 vbwrite  (0, 56c668, 1, 32b000, 32ec00, 32ec00) + 20
 001282e4 request_loop (32b000, 129400, 32cc60, a8c0, ffffffff, 25983) + 2b8
 000f5c2c main     (0, 327000, ffffffff, 0, ffbffb00, 0) + fb0
 000402c0 _start   (0, 0, 0, 0, 0, 0) + 108
-----------------  lwp# 63 / thread# 63  --------------------
 ff1c97cc _thr_setup (0, 0, 0, 0, 0, 0)
-----------------  lwp# 64 / thread# 64  --------------------
 ff1c97cc _thr_setup (0, 0, 0, 0, 0, 0)

 

Defect:

Etrack 149000 - vxconfigd dumps core during vxconfigd startup in vbwrite



Prior to performing the below workaround the 5.1 RP1 volboot file results in vxconfigd core dumping

# cat /etc/vx/volboot
volboot 3.1 0.1 100
hostid dopey
hostguid {714379b0-e059-11e0-af5d-0003baa8421b}
request_threads 2
Command_Shipping 1
end
###############################################################
###############################################################
###############################################################
###############################################################
###############################################################
##############################################################


Following the below workaround the /etc/vx/volboot file is revised as follows:

 
# cat /etc/vx/volboot
volboot 3.1 0.1 90
hostid dopey
hostguid {714379b0-e059-11e0-af5d-0003baa8421b}
request_threads 2
end
###############################################################
###############################################################
###############################################################
###############################################################
###############################################################
###############################################################
##################

Workaround:


The following workaround can be implemented to restart vxconfigd by recreating the /etc/vx/volboot:

# vxdctl stop ; cat /etc/vx/volboot ; rm /etc/vx/volboot ; vxconfigd -r reset ; vxdctl init ; vxdctl enable


Where "vxconfigd -r reset" is not possible, "vxconfigd -d" can be used.


The "vxdctl support" command can be used to display the supported VxVM object and component attributes for the configuration daemon.


# vxdctl support
Support information:
  vxconfigd_vrsn:   32
  dg_minimum:       20
  dg_maximum:       160
  kernel:           32
  protocol_minimum: 90
  protocol_maximum: 100
  protocol_current: 100


The values are described as follows:

vxconfigd_vrsn             Version of vxconfigd that is currently running.
dg_minimum                  Lowest disk group version  supported by vxconfigd.
dg_maximum                 Highest disk group version supported by vxconfigd.
kernel                               Highest kernel version  supported by vxconfigd.
protocol_minimum       Lowest cluster protocol version supported by the node.
protocol_maximum      Highest cluster protocol version supported by the node.
protocol_current          Cluster protocol version currently running on the node.

Note: The protocol version information is only meaningful for the VxVM cluster feature.
 

Applies To

Solaris with VxVM 5.1 RP1.
 

# modinfo | grep vx
 29 7be00000  4d7e0 328   1  vxdmp (VxVM 5.1RP1 DMP Driver)
 31 7ba00000 1f9938 329   1  vxio (VxVM 5.1RP1 I/O driver)
 33 7bbdb478    d40 330   1  vxspec (VxVM 5.1RP1 control/status driv)
216 7b2c1268    d40 331   1  vxportal (VxFS 5.1_SP1RP1 portal driver)
217 7aa00000 1fe098  21   1  vxfs (VxFS 5.1_SP1RP1 SunOS 5.10)