- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Alternate link...
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
тАО03-11-2004 03:02 AM
тАО03-11-2004 03:02 AM
Alternate link...
I had to extend a VG that use Service Guard with a new drive allocated on a SAN, I did the "pvcreate /dev/rdsk/cXtXdX" and I also did a "pvcreate /dev/rdsk/cX1tX1dX1" of the "alternate path", that was my mistake... So when I did my "vgextend vgname /dev/dsk/cXtXdX" it worked fine and showed me a disk added in my VG. But when I did my "vgextend vgname /dev/dsk/cX1tX1dX1" to do my "alternate link", because I've did a pvcreate of that device before, it added a new disk instead of an "Alternate link". So I reduce the VG of the last disk (the one that suppose to be the alternate link)...
My question is how can I give back to /dev/dsk/cX1tX1dX1 the state to be the alternate link to /dev/dsk/cXtXdX instead of a new disk???
Regards
Jonathan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-11-2004 03:06 AM
тАО03-11-2004 03:06 AM
Re: Alternate link...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-11-2004 03:10 AM
тАО03-11-2004 03:10 AM
Re: Alternate link...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-11-2004 03:14 AM
тАО03-11-2004 03:14 AM
Re: Alternate link...
I've double checked and I'm sure that it's supposed to be the alternate path... But I'll check with the SAN team here to be pretty sure!! I'll let you know!!! any other idea will be welcome too ;)
ciao!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-11-2004 03:40 AM
тАО03-11-2004 03:40 AM
Re: Alternate link...
In the moment you do a pvcreate on disk (Your alternate disk) you had just short before initialized with a pvcreate you should have received a warning.
Because it was already initialized before. So you must use the "-f" option of the pvcreate command. I can't see this in your post. So I think the second disk was uninitialized disk and not the alternate path.
Roland
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-11-2004 03:45 AM
тАО03-11-2004 03:45 AM
Re: Alternate link...
When you do a vgextend on the same physical using anither path , it should be added as an alternate link .
Most probably your second physical volume was not the same as the first one .
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-11-2004 04:21 AM
тАО03-11-2004 04:21 AM
Re: Alternate link...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-11-2004 04:27 AM
тАО03-11-2004 04:27 AM
Re: Alternate link...
And when I did a pvcreate a the secondary path, I did it with the -f option.
Idea?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-11-2004 04:28 AM
тАО03-11-2004 04:28 AM
Re: Alternate link...
On EMC? do a syminq and verify the /dev/rdsk/cX1tX1dX1 is the same EMC Device as the other one....
Rgds...Geoff
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-11-2004 04:29 AM
тАО03-11-2004 04:29 AM
Re: Alternate link...
It depends on when you ran 'pvcreate' on the alternate link. Before creating the VG or after?.
If it was done before creating the VG, then you are fine. It's not going to hurt. If it still added it as a different device, then you will need to check if it is infact the alternate path.
If it was done after creating the VG, then you deleted the LVM headers of the same disk. You will need to restore them back. Take out the alternate path with vgreduce. Then do
vgcfgrestore -n vgxx /dev/rdsk/cxtxdx
vgchange -a y vgxx
vgextend vgxx /dev/dsk/cx1tx1dx1
That should get you back. If you already have the data in the VG, then back it up before you proceed.
-Sri