vxvm issue

[swarup kundu]

Hi
In one Hpux server I am seeing some disks as online invalid after importing forcefully since normal import failed.can any one tell me how to recover private region in those disks to make them online.

[Sameer_Nirmal]

Those "some disks" may belongs to a diskgroup which maybe "disabled" ?

Can you post the results of the followings
# vxprint -ht
# vxprint -g -ht
# vxdg list
# vxdisk list

I am wondering as why the diskgroup was imported forcefully? What errors did it give while importing it in normal/usual way? Something maybe wrong which needs to be fixed to make the diskgroup(s) enabled.

[Javed Khan_1]

Hi,
If you see online invalid then your disk is not initialized by vxvm , perhaps if tou initialize the disk you will loose the data on the disk

do vxdisk list diskname on the disk which you imported , if are able to see
group: name=rootdg id=1186556662.1041.hostname
in vxdisk list diskname output you can import the disk group with
#vxdg import 1186556662.1041.hostname
Good Luck

Regards,
Javed Khan

[Ralph Grothe]

Usually disk groups should get imported automatically on reboot according to their disks' host id.
Thus I can only conclude that the disk whose auto-import failed probably was tagged with another host's ID.

You can esaily verify by

# vxdisk list cXtXdX | grep hostid

If it is not the same as a "uname -n" would produce, and if you are absolutely sure that this particular disk is not currently active in a disk group imported on another host,
you may clear the hostid tag by either

# vxdisk clearimport cXtXdX

or during import of the DG

# vxdg -C dg_name


Please, note that my VxVM experience is totally based on VxVM 3.5 under Solaris on Ultra SPARC, which may totally differ from HP's VxVM implementation.
So you better consult your manpages of vxdisk and vxdg before issueing any command!