- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: vgimport with a different minor number
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
Forums
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
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
11-12-2008 12:35 AM
11-12-2008 12:35 AM
I have recently created a cluster aware VG in a hurry. But later I realised that the minor number which I have used on the primary node is already in use on the secondary node..
Now I want to know than can i vgexport the current vg configuration on a map file, and then vgimport it using a different minor number..
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-12-2008 12:42 AM
11-12-2008 12:42 AM
SolutionYou can. Just export the VG on primary node with map file. Create new minor file and import it.
#vgexport -v -s -m /tmp/vg.map /dev/vgname
#mkdir /dev/vgname
#mknode /dev/vgname/group c 64 0x__0000
#vgimport -v -m /tmp/vg.map /dev/vgname
Ganesh.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-12-2008 12:57 AM
11-12-2008 12:57 AM
Re: vgimport with a different minor number
Minor number does not effect the ability to do a vgimport.
You have to use mknod to establish this so that you can do the import.
export/import is commonly used to correct errors made in volume group setup, including minor number issues.
http://unix.derkeiler.com/Newsgroups/comp.sys.hp.hpux/2003-10/0365.html
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-12-2008 01:02 AM
11-12-2008 01:02 AM
Re: vgimport with a different minor number
Typo error in my previous post.
#mknode /dev/vgname/group c 64 0x__0000
should be
#mknod /dev/vgname/group c 64 0x__0000
My sincere apologize for the mistake...
Ganesh.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-12-2008 01:08 AM
11-12-2008 01:08 AM