- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- How can I import a volume group, and retain PVG se...
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
11-15-2011 11:56 PM
11-15-2011 11:56 PM
Hi,
I am implementing a 2-node ServiceGuard cluster, with EVA storage in two sites:
Site 1 has node1 and 1 EVA frame, Site2 has node2 and another EVA frame. The goal is to have the storage mirrored over the two sites using LVM.
I have /etc/lvmpvg set up on node 1:
VG /dev/vgwaakdata
PVG EVADC1
/dev/disk/disk56
PVG EVADC2
/dev/disk/disk108
vgdisplay -v vgwaakdata shows PVG is OK:
VG Name /dev/vgwaakdata
VG Write Access read/write
VG Status available, exclusive
Max LV 255
Cur LV 1
Open LV 1
Max PV 16
Cur PV 2
Act PV 2
Max PE per PV 65535
VGDA 4
PE Size (Mbytes) 16
Total PE 31998
Alloc PE 31998
Free PE 0
Total PVG 2
Total Spare PVs 0
Total Spare PVs in use 0
VG Version 1.0
VG Max Size 16776960m
VG Max Extents 1048560
--- Logical volumes ---
LV Name /dev/vgwaakdata/lvol1
LV Status available/syncd
LV Size (Mbytes) 255984
Current LE 15999
Allocated PE 31998
Used PV 2
--- Physical volumes ---
PV Name /dev/disk/disk56
PV Status available
Total PE 15999
Free PE 0
Autoswitch On
Proactive Polling On
PV Name /dev/disk/disk108
PV Status available
Total PE 15999
Free PE 0
Autoswitch On
Proactive Polling On
--- Physical volume groups ---
PVG Name EVADC1
PV Name /dev/disk/disk56
PVG Name EVADC2
PV Name /dev/disk/disk108
Created a mapfile of the volume group with vgexport -p -s -v -m
after importing the volumegroup on node2 (vgimport -sv -N -m /tmp/vgwaakdata2.map vgwaakdata), manually updating /etc/lvmpvg with the correct disks for node2, and then switching the package to node2, LVM does not show the PVG information:
VG Name /dev/vgwaakdata
VG Write Access read/write
VG Status available, exclusive
Max LV 255
Cur LV 1
Open LV 1
Max PV 16
Cur PV 2
Act PV 2
Max PE per PV 65535
VGDA 4
PE Size (Mbytes) 16
Total PE 31998
Alloc PE 31998
Free PE 0
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0
VG Version 1.0
VG Max Size 16776960m
VG Max Extents 1048560
--- Logical volumes ---
LV Name /dev/vgwaakdata/lvol1
LV Status available/syncd
LV Size (Mbytes) 255984
Current LE 15999
Allocated PE 31998
Used PV 2
--- Physical volumes ---
PV Name /dev/disk/disk108
PV Status available
Total PE 15999
Free PE 0
Autoswitch On
Proactive Polling On
PV Name /dev/disk/disk56
PV Status available
Total PE 15999
Free PE 0
Autoswitch On
Proactive Polling On
Can someone please point out what I am missing?
Thanks!!
Peter
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-16-2011 05:05 AM
11-16-2011 05:05 AM
SolutionI seem to have found what I was missing:
By copy/pasting, apparently, the tabs between the name / value pair have been substituted by spaces. After editing /etc/lvmpvg, and replacing the spaces with a tab, vgdisplay correctly shows the Physical Volume Group information.
I have 7 volume groups that were in this scenario, and so far, I have fixed two of them. I will continue doing the same for the remainder and confirm my findings.
Peter