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-18-2007 08:54 AM
тАО06-18-2007 08:54 AM
VGID
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-18-2007 08:59 AM
тАО06-18-2007 08:59 AM
Re: VGID
When you do the vgimport and specify the '-s' and '-m' options, the map file is read to get that VGID. Then vgimport reads the VGRA of every disk on your system and finds all of those with a matching VGID. Those with the matching VGID are then imported made part of the VG you are importing.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-18-2007 08:59 AM
тАО06-18-2007 08:59 AM
Re: VGID
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-18-2007 09:59 AM
тАО06-18-2007 09:59 AM
Re: VGID
In fact, the VGID is composed on the machine ID (as seen via 'uname -i') and the Epoch timestamp marking the date and time that the volume group was created. The Physical Volume ID (PVID) is similarly stored:
# cat .fetchlvmid
#!/usr/bin/sh
RDEV=$1
KIND=`xd -An -j 8192 -N8 -tc ${RDEV} 2> /dev/null | xargs`
if [ "${KIND}" = "L V M R E C 0 1" ]; then
INFO=`xd -An -j8200 -N16 -tx ${RDEV}`
PVID=`echo ${INFO} | awk '{print $1 $2}'`
VGID=`echo ${INFO} | awk '{print $3 $4}'`
fi
echo "${RDEV} PVID = ${PVID}"
echo "${RDEV} VGID = ${PVID}"
# ./fetchlvmid /dev/rdsk/c0t6d0
/dev/rdsk/c0t6d0 PVID = 11823e9d33fb2abe
/dev/rdsk/c0t6d0 VGID = 11823e9d33fb2abe
....where "11823e9" is the hexadecimal value of the 'uname -i' and '33fb2abe' is the Epoch timestamp.
Regards!
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-20-2007 07:01 AM
тАО06-20-2007 07:01 AM
Re: VGID
A minor correction on your script, you had:
echo "${RDEV} PVID = ${PVID}"
echo "${RDEV} VGID = ${PVID}"
and I believe it should read:
echo "${RDEV} PVID = ${PVID}"
echo "${RDEV} VGID = ${VGID}"
Also I noticed that the VGID did not completely match that of what I got when I ran vgexport -m mapname.map -s -p vgtoexport. There appeared to be a leading 0 in the string from the output of the vgexport command. Other than that - a great little script-let.