HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- -s adds VGID to map file
Operating System - HP-UX
1834789
Members
2830
Online
110070
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
Forums
Discussions
Discussions
Discussions
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
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
09-12-2002 10:18 AM
09-12-2002 10:18 AM
Looks like the -s switch adds a line to the map file, VGID... whereas just using the -p without the shared mode switch does not.
VGID 781a573a3cc590d3
1 lvol1
2 lvol2
Will this cause issues when rebuilding a "non" shared volume group?
VGID 781a573a3cc590d3
1 lvol1
2 lvol2
Will this cause issues when rebuilding a "non" shared volume group?
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-12-2002 10:19 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-12-2002 10:21 AM
09-12-2002 10:21 AM
Re: -s adds VGID to map file
Oops -
Please move into the "rebuilding system and saving LVM info" post
Please move into the "rebuilding system and saving LVM info" post
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-12-2002 10:24 AM
09-12-2002 10:24 AM
Re: -s adds VGID to map file
With "-s" it kindda makes it easy later on in the vgimport whereby you don;t have to specify the device path because the VGID is recorded in the map file. All of the disks that belong in a volume group have a VGID number. So in the vgimport (with "-s") you don't need to specify each and every disk. Having said that I prefer to not use "-s". To answer your question ..
No, it will not cause any issues. Just remember to use "-s" in your vgimport it you used it in vgexport.
No, it will not cause any issues. Just remember to use "-s" in your vgimport it you used it in vgexport.
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.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP