- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: added new devices to vgs now the snap jobs don...
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
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
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
тАО06-27-2009 07:02 PM
тАО06-27-2009 07:02 PM
I added 2 devs to vg05 and 1 dev to vg06. The devices in those vgs get snapped and mounted on the same system as vg21 and vg22 respectively.
I've ensured that the snap source/clones are correct, all 3 devs are differents sizes, and the snap would fail if the devs were different sizes.
I've added the source devs to vg05 and vg06 and created the new Raw lvols.
NOTE: vg04 and vg07 are also part of this process but no new devices were added. Everything still works for them.
My vgexport command succeeds:
vgexport -p -v -m /tmp/vg05.map /dev/vg05
creating the vg directories works fine.
vgchgid works fine and the three new target devs all succeed on this command.
the vgimport command fails for vg21 and vg22:
/usr/local/sbin# vgimport -m /tmp/scripts/vg05.map -f /usr/local/sbin/vg21.infile /dev/vg21
vgimport: The Physical Volumes specified on the command line
do not belong to the same Volume Group.
/usr/local/sbin/vg21.infile contains:
/dev/dsk/c49t3d6
/dev/dsk/c54t3d6
/dev/dsk/c55t3d6
/dev/dsk/c49t9d5
/dev/dsk/c54t9d5
/dev/dsk/c55t9d5
/dev/dsk/c49t9d7
/dev/dsk/c54t9d7
/dev/dsk/c55t9d7
which are correct.
I'm confused about the result of the vgimport:
"vgimport: The Physical Volumes specified on the command line
do not belong to the same Volume Group."
Since vg21 doesn't exist at this time how can it "not belong"
I feel like I'm missing something simple here.
Any help would be appreciated.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-27-2009 11:20 PM
тАО06-27-2009 11:20 PM
Re: added new devices to vgs now the snap jobs don't work
I think you have to check the vgid of each disk. Look some threads about reading vgid for example
http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=523849
and be sure to have the same vgid on each pv.
If it's not the case, well the vgimport could not succeed.
When you do the vgchdid you write the "3 news target devs". Try to check first the vgid of this news target.
Hope it helps
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-28-2009 01:03 AM
тАО06-28-2009 01:03 AM
Solution-example - I have a VG with 2 disks (lets ignore alternate links for this example):
c6t0d0
c6t0d1
Now I add another disk to the VG, which is c6t0d2
I go through my vgexport and snapclone process, and when I get to the vgchgid bit, the *only* correct invocation of vgchgid is:
vgchgid /dev/rdsk/c6t0d0 /dev/rdsk/c6t0d1 /dev/rdsk/c6t0d2
Anything else is incorrect, so for example if I did this:
vgchgid /dev/rdsk/c6t0d0
vgchgid /dev/rdsk/c6t0d1
vgchgid /dev/rdsk/c6t0d2
I would get the errors you describe, also if I only did the vgchgid on the new disk:
vgchgid /dev/rdsk/c6t0d2
but didn't run it for the others, I'd get the errors you describe...
vgchgid is writing a new VGID into the VG reserved area on the disk. IIRC this is made up of the machine identification number (i.e. the output of uname -i) concatenated with the time expressed in secoonds past the epoch (1/1/70). So if you just run it for 1 disk in a VG, or run it multiple times for seperate disks in a VG, you'll get a different VGID written into the VGRA on each disk - hence the problem you see.
HTH
Duncan
I am an HPE Employee
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-28-2009 05:31 AM
тАО06-28-2009 05:31 AM
Re: added new devices to vgs now the snap jobs don't work
Can't tell you how often I looked over that job :)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-28-2009 05:32 AM
тАО06-28-2009 05:32 AM