- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: VG Import of a LVM Version 2.0 Volume Group
Operating System - HP-UX
1752292
Members
4432
Online
108786
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
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
тАО10-08-2009 12:40 PM
тАО10-08-2009 12:40 PM
VG Import of a LVM Version 2.0 Volume Group
I have no idea why, but I created two volume groups with Version 2.0. Here is my problem. I have data that I replicate via SRDF on a SYMM to my DR site. I've been able to do vgimports all of the time because the sybase guys use named raw partitions(lv's). Anyway, so I created a vgmap file with the following command. vgexport -v -m vg05.map -s /dev/vg05 and the same with vg6.
Here is the output of the VG05.map file(which is different then what I'm used to seeing).
MAPFILE02
VGID A0000000000000001Fri Feb 27 20:36:40 200975b7f04f-6bf3-11dd-ae35-663e139c07
cb
1 sybase
Anyway I'm able to do a vgimport, AND I found the data being populated in the /etc/lvmtab_p file(took me a bit to find that).
strings /etc/lvmtab_p
/dev/vg05
A0000000000000001Fri Feb 27 20:36:40 200975b7f04f-6bf3-11dd-ae35-663e139c07cb
/dev/dsk/c2t15d5
But every time I attempt to activate the drive with a vgchange I get the following error.
vgchange -a y /dev/vg05
vgchange: Couldn't activate volume group "/dev/vg05":
Quorum not present, or some physical volume(s) are missing.
I've attempted to tell it to activate without the quorum but still get the same error.
vg05 is a volume group with only one 9 gig lun in it on the other side, so I'm not missing anything. And I can clearly see the disks exist and size.
So what am I missing here?
Please help!
Here is the output of the VG05.map file(which is different then what I'm used to seeing).
MAPFILE02
VGID A0000000000000001Fri Feb 27 20:36:40 200975b7f04f-6bf3-11dd-ae35-663e139c07
cb
1 sybase
Anyway I'm able to do a vgimport, AND I found the data being populated in the /etc/lvmtab_p file(took me a bit to find that).
strings /etc/lvmtab_p
/dev/vg05
A0000000000000001Fri Feb 27 20:36:40 200975b7f04f-6bf3-11dd-ae35-663e139c07cb
/dev/dsk/c2t15d5
But every time I attempt to activate the drive with a vgchange I get the following error.
vgchange -a y /dev/vg05
vgchange: Couldn't activate volume group "/dev/vg05":
Quorum not present, or some physical volume(s) are missing.
I've attempted to tell it to activate without the quorum but still get the same error.
vg05 is a volume group with only one 9 gig lun in it on the other side, so I'm not missing anything. And I can clearly see the disks exist and size.
So what am I missing here?
Please help!
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-08-2009 12:48 PM
тАО10-08-2009 12:48 PM
Re: VG Import of a LVM Version 2.0 Volume Group
Shalom,
Can you back up the data, destroy and rebuild the volume group using a version you are more familiar with, followed by data restore?
I know its a pain, but downgrading a volume group does not seem possible.
SEP
Can you back up the data, destroy and rebuild the volume group using a version you are more familiar with, followed by data restore?
I know its a pain, but downgrading a volume group does not seem possible.
SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
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
тАО10-08-2009 01:56 PM
тАО10-08-2009 01:56 PM
Re: VG Import of a LVM Version 2.0 Volume Group
HI
a) check your old lvmtabs for another disk
b) pvdisplay disk and verify what vg is written to it
c) vgreduce -f /dev/vg
The is a discrepencey between the kernel and lvmtab. Using c) will keep lvmtab, refer to what is in the kernel, and remove the difference.
a) check your old lvmtabs for another disk
b) pvdisplay disk and verify what vg is written to it
c) vgreduce -f /dev/vg
The is a discrepencey between the kernel and lvmtab. Using c) will keep lvmtab, refer to what is in the kernel, and remove the difference.
Support Fatherhood - Stop Family Law
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-08-2009 02:02 PM
тАО10-08-2009 02:02 PM
Re: VG Import of a LVM Version 2.0 Volume Group
d) vgcfgrestore /etc/lvmconf/vg.map_old -l
Note the -l. This can also help you id the problem disk by listing out the old map file.
vgscan -p -s -a -v
-p preview
-s all pv's
-a all controllers
-v verbose
This will poll all luns accessible to the box and build a preview of a new lvmtab. Note: Don't use without -p preview unless you want to overwrite your current lvmtab.
Note the -l. This can also help you id the problem disk by listing out the old map file.
vgscan -p -s -a -v
-p preview
-s all pv's
-a all controllers
-v verbose
This will poll all luns accessible to the box and build a preview of a new lvmtab. Note: Don't use without -p preview unless you want to overwrite your current lvmtab.
Support Fatherhood - Stop Family Law
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