Minor numbers used for /dev/vg_name/group during setup

[Marco Shaw_1]

HP-UX 11.23-PA with MC SG 11.16

Creating a 2 node cluster, I'm going to have a shared VG managed by SG named vg_share.

When creating /dev/vg_share/group on each node, *must* I have the same minor number on each system?

I'm going to have a active-passive setup.

[Calandrello]

Friend
Imports the VG created in all nodes vgexport - s - p - m vgxxx.map /dev/vgxxx to copy the archive vgxxx.map for the others nodes. to create the archives special, mknod /dev/vgxxx/group c 64 0x0000 vgimport - s - p vgxxx.map /dev/vgxxx to activate in shared mode executes the /usr/sbin/vgchange option - c to cluster - S vgxxx in the others nodes.

[Pete Randall]

Marco,

No, I don't believe it's necessary - just common.


Pete

[Steven E. Protter]

Shalom,

This is useful because you want to have the same cluster configuration files and package control scripts to be the same on both nodes. This may not be possible if the minor numbers are not the same.

Make sure you activate the volume group in exclusive mode for an active-passive configuration.

SEP

[A. Clay Stephenson]

All that is necessary is that the volume group names and the LVOL names are the same on each node. You could have completely different minor device numbers and completely different pv paths for the PV's which comprise the VG BUT you are adding possible confusion to the mix. Whenever possible, I prefer to use exactly the same minor device numbers and PV paths on all the nodes.