- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- vgextend ...
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
Forums
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
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
07-14-2006 03:36 PM
07-14-2006 03:36 PM
vgextend ...
In My RAC Cluster (2*Superdome&EVA 4k). Two path device file got changed after a reboot of the server.Now i need to change the information in /etc/lvmtab.
I am writing my steps if i am wrong somewhere pls correct me
1)Halt the RAC Cluster (pkg & Node)
2)vgchange -c n -S n vg01
3)vgchange -a y vg01
4)vgreduce -f (This will remove my old missing links)
5)vgextend /dev/vg01 /dev/dsk/cxtydz /dev/dsk/cxtydz
6)vgchange -a n vg01
7)vgchange -c y -S y vg01
8)Then start the cluster (PKG & NODE)
or
Is there any other way to do it ???
Cheers
Arunkumar.B
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-14-2006 07:22 PM
07-14-2006 07:22 PM
Re: vgextend ...
The procedure looks oke.
Another option:
Do you have a backup of the original VG conf(/etc/lvmconf).
See man vgcfgrestore and vgimport.
Have you checked what the root cause of the device change is?
Darrel
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-14-2006 10:17 PM
07-14-2006 10:17 PM
Re: vgextend ...
I'm not sure that vgreduce/vgextend will store the data. I'd prefer to vgexport/vgimport procedure:
vgchange -a n vg01
vgexport vg01
mkdir /dev/vg01
mknod /dev/vg01/group c 64 0x010000
vgimport /dev/vg01 /dev/dsk/ ........
vgchange -c y -S y vg01
HTH
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-15-2006 01:43 AM
07-15-2006 01:43 AM
Re: vgextend ...
Abracos
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-23-2006 01:00 AM
07-23-2006 01:00 AM
Re: vgextend ...
The Problem resolved by using
vgscan -av
Thanks for ur replies
Arunkumar.B