- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Create new logical vol on SG cluster
Operating System - HP-UX
1748352
Members
5099
Online
108762
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
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
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- 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
тАО03-04-2008 06:48 AM
тАО03-04-2008 06:48 AM
Hi,
I have created a new logical volume on a SG cluster system. No new disks were added to the volume group or anything, just the lv. I modified the cluster ctrl file (package) on both the primary and alternate nodes to add the LV. I did a "vgexport -p -v -s -m mapfile /dev/vgexp
The problem is when I do a "vgimport -v -s -m mapfile /dev/vgexp on the alternate node, I get the following:
Beginning the import process on Volume Group "/dev/vgexp".
vgimport: Volume group "/dev/vgexp" already exists in the "/etc/lvmtab" file.
So my question is, do I even have to do an import? I assume that I would so that it recognizes the new lv. I can't check if the import worked and the new lv is part of the vg because the vg is inactive on that server (and has to remain inactive).
Thanks,
SD
I have created a new logical volume on a SG cluster system. No new disks were added to the volume group or anything, just the lv. I modified the cluster ctrl file (package) on both the primary and alternate nodes to add the LV. I did a "vgexport -p -v -s -m mapfile /dev/vgexp
The problem is when I do a "vgimport -v -s -m mapfile /dev/vgexp on the alternate node, I get the following:
Beginning the import process on Volume Group "/dev/vgexp".
vgimport: Volume group "/dev/vgexp" already exists in the "/etc/lvmtab" file.
So my question is, do I even have to do an import? I assume that I would so that it recognizes the new lv. I can't check if the import worked and the new lv is part of the vg because the vg is inactive on that server (and has to remain inactive).
Thanks,
SD
whatever
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-04-2008 07:08 AM
тАО03-04-2008 07:08 AM
Solution
You need to vgexport the vg on the alternate node before vgimporting it. The sequence typically goes like this:
On primary:
vgexport -p -v -s -m mapfile /dev/vgexp
On alternate
ll /dev/vgexp/group
(note down the device minor number 0xNN0000)
vgexport /dev/vgexp
mkdir /dev/vgexp
mknod /dev/vgexp/group c 64 0xNN0000
(using the 0xNN0000 noted before)
vgimport -v -s -m mapfile /dev/vgexp
That should work...
HTH
Duncan
I am an HPE Employee
On primary:
vgexport -p -v -s -m mapfile /dev/vgexp
On alternate
ll /dev/vgexp/group
(note down the device minor number 0xNN0000)
vgexport /dev/vgexp
mkdir /dev/vgexp
mknod /dev/vgexp/group c 64 0xNN0000
(using the 0xNN0000 noted before)
vgimport -v -s -m mapfile /dev/vgexp
That should work...
HTH
Duncan
I am an HPE Employee
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-04-2008 07:11 AM
тАО03-04-2008 07:11 AM
Re: Create new logical vol on SG cluster
Bonsoir,
If you want to re-import the VG on the adoptive node, you must export it before.
A more simple way : if you have not modified VG structure, that is just created a new LV, you can simply create special files under /dev/vgexp. Look at major/minor of block (lvolX) and raw (rlvolX) devices of the new LV under /dev/vgexp on the native node and create them with same major/minor with mknod on the daoptive node.
And yes you can check the VG on the adoptive node : activate it in read-only --> vgchange -a r vgexp. Check what you want, the don't forget to deactivate it after --> vgchange -a n vgexp.
Regards
Eric
If you want to re-import the VG on the adoptive node, you must export it before.
A more simple way : if you have not modified VG structure, that is just created a new LV, you can simply create special files under /dev/vgexp. Look at major/minor of block (lvolX) and raw (rlvolX) devices of the new LV under /dev/vgexp on the native node and create them with same major/minor with mknod on the daoptive node.
And yes you can check the VG on the adoptive node : activate it in read-only --> vgchange -a r vgexp. Check what you want, the don't forget to deactivate it after --> vgchange -a n vgexp.
Regards
Eric
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP