- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- PV paths are missing after vgexport / vgimport
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-31-2012 12:47 PM
05-31-2012 12:47 PM
PV paths are missing after vgexport / vgimport
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
- Tags:
- vgimport
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-31-2012 01:01 PM
05-31-2012 01:01 PM
Re: PV paths are missing after vgexport / vgimport
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.
- Tags:
- insf
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-31-2012 01:28 PM
05-31-2012 01:28 PM
Re: PV paths are missing after vgexport / vgimport
Thanks for the reply,
Should I re-import the VG map file after running 'insf -e' ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-31-2012 01:45 PM
05-31-2012 01:45 PM
Re: PV paths are missing after vgexport / vgimport
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.