cancel
Showing results for 
Search instead for 
Did you mean: 

vxconfigd died after adding new luns

Hi Team,

I have an issue where Customer informed after adding new LUNS to nodes in cluster , vxconfigd daemon died .

Below are error messages seen on nodes :

Nov 28 05:46:58 server101 kernel: sd 1:0:4:0: Warning! Received an indication that the LUN assignments on this target have changed. The Linux SCSI layer does not automatically remap LUN assignments.

Nov 28 05:51:35 server101 vxvm:vxconfigd: V-5-1-8615 Cannot get cluster information from kernel: Bad file descriptor
Nov 28 05:51:35 server101 vxvm:vxconfigd: V-5-1-8627 Cannot store private storage into the kernel: Bad file descriptor

SFHA 5.1 SP1RP4 on RHEL 5.11

Does anyone have any idea about these kind of issue?

2 Replies

Re: vxconfigd died after adding new luns

@linuxrocks

I have moved your post to a more appropriate forum.

Re: vxconfigd died after adding new luns

If you can reboot, just reboot to have a new fresh up to date kernel.

 

if cannot reboot, restart vxconfigd by the command below

vxconfigd -k

please note that it the system is a cluster node, freeze all the service group with atorage resources prior running the command.

Please also make sure that there is not any cx commands which may change vxvm configuration s running (commands like vxassist, vxmake, vxsd, vxplex etc)

 

Frank