- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- VGMODIFY - HPUX 11iv2 system
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
тАО01-04-2011 08:13 AM
тАО01-04-2011 08:13 AM
1. can run 'vgmodify -tv volgroup' to see table of values.
2. The volgroup is cluster owned/aware so I need to halt the package.
3. After package is halted, make the cluster unaware with 'vgchange -c n /dev/volgroup'
4. deactive it with 'vgchange -a n /dev/volgroup' (is this step needed????)
4. apply the change with 'vgmodify -p xx volgroup' xx is my new max numbers of pVs
5. reactive it with 'vgchange -a y /dev/volgroup'
6. run 'vgdisplay /dev/volgroup' to confirm the changes.
7. deactive the volgroup again. (-a n)
8. make the volgroup cluster aware (-c y)
8. start my package
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-04-2011 09:46 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-04-2011 09:47 AM
тАО01-04-2011 09:47 AM
Re: VGMODIFY - HPUX 11iv2 system
I had documented these tasks a short time back but left out a step or two. Was re-confirming!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-04-2011 09:49 AM
тАО01-04-2011 09:49 AM
Re: VGMODIFY - HPUX 11iv2 system
Per the manpage on 11.23 for vgmodify:
"... The volume group can be active when reporting the configuration (-r) or displaying a table of available settings (-t). The volume group must be de-activated before vgmodify can perform any configuration
changes (see vgchange(1M))."
/rcw
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-04-2011 01:34 PM
тАО01-04-2011 01:34 PM
Re: VGMODIFY - HPUX 11iv2 system
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-04-2011 01:36 PM
тАО01-04-2011 01:36 PM