PV paths are missing after vgexport / vgimport

[Seungjun]

Hi,

I have a 2 node clustering system using SGeRAC.

I wanted to extend the shared VG, so I did followings after creating a new virtual disk in EVA.

(the new virtual disk is shown to both nodes in EVA)

- Deactivate the VG on all nodes

- Make the VG as unsharable

- Activate the VG in exclusive mode from node1

- Create a new PV => extend VG => create new LVs (from node1)

- Export VG (from node1)

# vgexport -s -p -v -m /tmp/vg_rac.map /dev/vg_rac

- Copy the mapfile to the other node

- On the other node, export the current VG and import the map file

# vgexport -m /tmp/vg_rac.old.map /dev/vg_rac

# mkdir /dev/vg_rac

# mknod /dev/vg_rac/group c 64 0x020000

# vgimport -v -s -m /tmp/vg_rac.map /dev/vg_rac

- Deactivate the VG

- Make the VG sharable

- Activate the VG in shared mode on all nodes

The result is that there are no paths (primary & alternate) to the new PV from node2.

Paths to existing PVs are okay.  Only the paths for the new PV are missing.

What did I miss?

Regards,

Jun

[Patrick Wallek]

Do the devices and paths to the new LUNs show up if you do an 'ioscan' on NODE2?

If the devices show up but the paths do not, you probably need to do an 'insf -e' to get HP-UX to create the paths to the new LUNs.

[Seungjun]

Thanks for the reply,

Should I re-import the VG map file after running 'insf -e' ?

[Patrick Wallek]

If the VG is not in use on that node, that may be the easiest way.  That would also verify that everything is working as expected and make sure all of your LVs are imported as well.