HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: hii sme help needed again for vgimport
Operating System - HP-UX
1836872
Members
2255
Online
110110
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
Forums
Discussions
Discussions
Discussions
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
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
11-20-2008 02:43 PM
11-20-2008 02:43 PM
hii sme help needed again for vgimport
hi,
m tryng to import vg from one node to to other node..
from node a i took an vgexport which is ;
root #/ >vgexport -p -v -s -m /tmp/vg_gbcb_bancs_dbday.map vg_gbcb_bancs_dbday
Beginning the export process on Volume Group "vg_gbcb_bancs_dbday".
vgexport: Volume group "vg_gbcb_bancs_dbday" is still active.
/dev/dsk/c20t1d4
/dev/dsk/c22t1d4
/dev/dsk/c24t1d4
/dev/dsk/c26t1d4
/dev/dsk/c11t1d4
/dev/dsk/c13t1d4
/dev/dsk/c15t1d4
/dev/dsk/c17t1d4
/dev/dsk/c11t2d1
/dev/dsk/c13t2d1
/dev/dsk/c15t2d1
/dev/dsk/c17t2d1
n wen m tryng to vgimport on another node its giving me;
strings /etc/lvmtab;
/dev/vg_gbcb_bancs_dbday
/dev/dsk/c1t1d4
/dev/dsk/c3t1d4
/dev/dsk/c5t1d4
/dev/dsk/c7t1d4
/dev/dsk/c11t1d4
/dev/dsk/c13t1d4
/dev/dsk/c15t1d4
/dev/dsk/c17t1d4
as a result of whch m not able to up my package in node b ....the above one..error given below...
########### Node "cedge2": Starting package at Fri Nov 21 03:51:17 IST 2008 ###########
Nov 21 03:51:17 - Node "cedge2": Activating volume group vg_gbcb_bancs_appl with exclusive option.
Activated volume group in Exclusive Mode.
Volume group "vg_gbcb_bancs_appl" has been successfully changed.
Nov 21 03:51:17 - Node "cedge2": Activating volume group vg_gbcb_bancs_dbday with exclusive option.
vgchange: Couldn't activate volume group "vg_gbcb_bancs_dbday":
Quorum not present, or some physical volume(s) are missing.
ERROR: Function activate_volume_group
ERROR: Failed to activate vg_gbcb_bancs_dbday
Nov 21 03:51:17 - Node "cedge2": Deactivating volume group vg_gbcb_bancs_appl
Deactivated volume group in Exclusive Mode.
Volume group "vg_gbcb_bancs_appl" has been successfully changed.
Nov 21 03:51:17 - Node "cedge2": Deactivating volume group vg_gbcb_bancs_dbday
vgchange: Volume group "vg_gbcb_bancs_dbday" has been successfully changed.
Nov 21 03:51:17 - Node "cedge2": Deactivating volume group vg_gbcb_bancs_dbnight
vgchange: Volume group "vg_gbcb_bancs_dbnight" has been successfully changed.
Nov 21 03:51:17 - Node "cedge2": Deactivating volume group vg_gbcb_prod_fone
vgchange: Volume group "vg_gbcb_prod_fone" has been successfully changed.
m tryng to import vg from one node to to other node..
from node a i took an vgexport which is ;
root #/ >vgexport -p -v -s -m /tmp/vg_gbcb_bancs_dbday.map vg_gbcb_bancs_dbday
Beginning the export process on Volume Group "vg_gbcb_bancs_dbday".
vgexport: Volume group "vg_gbcb_bancs_dbday" is still active.
/dev/dsk/c20t1d4
/dev/dsk/c22t1d4
/dev/dsk/c24t1d4
/dev/dsk/c26t1d4
/dev/dsk/c11t1d4
/dev/dsk/c13t1d4
/dev/dsk/c15t1d4
/dev/dsk/c17t1d4
/dev/dsk/c11t2d1
/dev/dsk/c13t2d1
/dev/dsk/c15t2d1
/dev/dsk/c17t2d1
n wen m tryng to vgimport on another node its giving me;
strings /etc/lvmtab;
/dev/vg_gbcb_bancs_dbday
/dev/dsk/c1t1d4
/dev/dsk/c3t1d4
/dev/dsk/c5t1d4
/dev/dsk/c7t1d4
/dev/dsk/c11t1d4
/dev/dsk/c13t1d4
/dev/dsk/c15t1d4
/dev/dsk/c17t1d4
as a result of whch m not able to up my package in node b ....the above one..error given below...
########### Node "cedge2": Starting package at Fri Nov 21 03:51:17 IST 2008 ###########
Nov 21 03:51:17 - Node "cedge2": Activating volume group vg_gbcb_bancs_appl with exclusive option.
Activated volume group in Exclusive Mode.
Volume group "vg_gbcb_bancs_appl" has been successfully changed.
Nov 21 03:51:17 - Node "cedge2": Activating volume group vg_gbcb_bancs_dbday with exclusive option.
vgchange: Couldn't activate volume group "vg_gbcb_bancs_dbday":
Quorum not present, or some physical volume(s) are missing.
ERROR: Function activate_volume_group
ERROR: Failed to activate vg_gbcb_bancs_dbday
Nov 21 03:51:17 - Node "cedge2": Deactivating volume group vg_gbcb_bancs_appl
Deactivated volume group in Exclusive Mode.
Volume group "vg_gbcb_bancs_appl" has been successfully changed.
Nov 21 03:51:17 - Node "cedge2": Deactivating volume group vg_gbcb_bancs_dbday
vgchange: Volume group "vg_gbcb_bancs_dbday" has been successfully changed.
Nov 21 03:51:17 - Node "cedge2": Deactivating volume group vg_gbcb_bancs_dbnight
vgchange: Volume group "vg_gbcb_bancs_dbnight" has been successfully changed.
Nov 21 03:51:17 - Node "cedge2": Deactivating volume group vg_gbcb_prod_fone
vgchange: Volume group "vg_gbcb_prod_fone" has been successfully changed.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-20-2008 06:07 PM
11-20-2008 06:07 PM
Re: hii sme help needed again for vgimport
Hi,
>>> n wen m tryng to vgimport on another node its giving me;<<
what error are you getting ..?
NodeA
do you have created the vg_gbcb_bancs_dbday.map ..?
If yes
# vi vg_gbcb_bancs_dbday.map --> copy the output
NodeB
# vi /tmp/vg_gbcb_bancs_dbday.map --> past the output
:wq! -> save and exit
NodeB
# Scan your current system to identify all disks by their volume groups.
/usr/sbin/vgscan -v
# Create a directory for the volume group to which the new LVM disk will belong. For example, a new volume group might be called vg06.
mkdir /dev/vg_gbcb_bancs_dbday
# Check to make sure that you are creating a unique minor number for the new group file. Then create a character device special file for the new volume group's group file. The character major number for LVM is 64. In the minor number, n must be in the range between 0 and 9, because the maximum number of volume groups by default allowed on a system is ten. You can increase the number by changing the operating-system parameter maxvgs in /usr/conf/master.d/core-hpux or by using SAM.
ll /dev/*/group
mknod /dev/vg_gbcb_bancs_dbday/group c 64 0x0n0000
# Import the LVM disk to the current system, citing the block device special file name you noted when the system booted up and the mapfile you created when invoking vgexport at the beginning of the procedure. You can preview the effect of the import by using the -p option.
vgimport -pv -m mapfile /dev/vg_gbcb_bancs_dbday block_device_special_file
vgimport -v -m mapfile /dev/vg_gbcb_bancs_dbday block_device_special_file
The vgimport command adds the volume group name to the /etc/lvmtab file. It also adds the device special files associated with the volume group's logical volumes to the system.
# Activate the new volume group.
/usr/sbin/vgchange -a y /dev/vg_gbcb_bancs_dbday
Thanks,
Johnson
>>> n wen m tryng to vgimport on another node its giving me;<<
what error are you getting ..?
NodeA
do you have created the vg_gbcb_bancs_dbday.map ..?
If yes
# vi vg_gbcb_bancs_dbday.map --> copy the output
NodeB
# vi /tmp/vg_gbcb_bancs_dbday.map --> past the output
:wq! -> save and exit
NodeB
# Scan your current system to identify all disks by their volume groups.
/usr/sbin/vgscan -v
# Create a directory for the volume group to which the new LVM disk will belong. For example, a new volume group might be called vg06.
mkdir /dev/vg_gbcb_bancs_dbday
# Check to make sure that you are creating a unique minor number for the new group file. Then create a character device special file for the new volume group's group file. The character major number for LVM is 64. In the minor number, n must be in the range between 0 and 9, because the maximum number of volume groups by default allowed on a system is ten. You can increase the number by changing the operating-system parameter maxvgs in /usr/conf/master.d/core-hpux or by using SAM.
ll /dev/*/group
mknod /dev/vg_gbcb_bancs_dbday/group c 64 0x0n0000
# Import the LVM disk to the current system, citing the block device special file name you noted when the system booted up and the mapfile you created when invoking vgexport at the beginning of the procedure. You can preview the effect of the import by using the -p option.
vgimport -pv -m mapfile /dev/vg_gbcb_bancs_dbday block_device_special_file
vgimport -v -m mapfile /dev/vg_gbcb_bancs_dbday block_device_special_file
The vgimport command adds the volume group name to the /etc/lvmtab file. It also adds the device special files associated with the volume group's logical volumes to the system.
# Activate the new volume group.
/usr/sbin/vgchange -a y /dev/vg_gbcb_bancs_dbday
Thanks,
Johnson
Problems are common to all, but attitude makes the difference
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-20-2008 09:19 PM
11-20-2008 09:19 PM
Re: hii sme help needed again for vgimport
Hi,
Hi,
For missing PV please check the syslog.log file is there any hardware failure is there or not.
Reagrds
Prashant
Hi,
For missing PV please check the syslog.log file is there any hardware failure is there or not.
Reagrds
Prashant
For success, attitude is equally as important as ability
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.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP