>>>if there vgimport before running disk disk30 disk40 used by another vg. there is any problem?<<<<
no problem -> if that vg is not active in secondary Node, if the vg is active "it would blow vg info from your "lvmtab"
so if i am correct in your case you have added new disks to cluster aware vg in(Pri-Node) you need to update the change to (Sec-Node)
you are using (DSF) legacy device file so -N option while help to convert while importing the vg to secondary)
normal practise when you add (new vg to cluster aware VG ) we always "vexport -p" perview options -s -m mapfile all were the (vg is active)
Primary Node:-
pvcreate,
vgextend
vgexport -p -s -v -m /tmp/vgname.map /dev/vgname
# rcp /tmp/vgmax4.map nodee2:/tmp/vgmax4.map
Secondary Node:-
# vgexport /dev/vgname
# mkdir /dev/vgname
# mknode /dev/vgname/group c 64 0x030000
# vgimport -N -p -s -v -m /tmp/vgname.map /dev/vgname
(if above preview show no errors than proceed to vimport by removing -p preview options)
# vgimport -N -s -v -m /tmp/vgname.map /dev/vgname
Problems are common to all, but attitude makes the difference