- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: LVM VG map files
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
тАО05-27-2009 08:46 AM
тАО05-27-2009 08:46 AM
Looking at the map file, I only see the VG ID and pairs of minor numbers and LV names. Does this mean that the only time I really need to send out new map files is when I add or delete LVs? Does adding a PV to a VG and then expanding an LV really require this procedure? It seems that the map file wouldn't contain any new information.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-27-2009 08:49 AM
тАО05-27-2009 08:49 AM
Re: LVM VG map files
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-27-2009 09:02 AM
тАО05-27-2009 09:02 AM
Re: LVM VG map files
After looking at the mapfile, what about your /etc/lvmtab file. Do we need to have each volume group shown with it's corresponding disk. If you don't run a fresh vgimport after adding disk on the primary node - do you think your lvmtab would be "good" on those other boxes?
So...do you need to keep your volume group and lvmtab in harmony? If they aren't in harmony could you maybe get an error that the volume group is out of sync with the kernel?
And what if you forgot last time, or the other person forgot to import last time you needed to (pesky phone interuptions-oops) what if we needed it last time.
I don't know, guess it's the housekeeper in me - I just like things all neat and harmonious and freshly imported.
/rcw
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-27-2009 09:15 AM
тАО05-27-2009 09:15 AM
Re: LVM VG map files
Rita is right.
Any change you make to the VG structure has to be updated to all the nodes.
Specially:
1) add or remove a disk from a VG.
2) add or remove a LV from a VG.
3) If you use BCVs that do a vgchgid.
for other operations it is not necessary but advisable to re-populate the VG structures.
Other wise you will end up with an inconsistent /etc/lvmtab across the SG nodes.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-27-2009 10:04 AM
тАО05-27-2009 10:04 AM
Solution>>Looking at the map file, I only see the VG ID and pairs of minor numbers and LV names.
Yes true ,the map file will only have lvol names and vgid(incase of -s used while creatin map).(Even you can import the vg with out refering to the map file but the lvol names in the imported vg will be like lvol1 ..lvol2 ...and offcourse u need to provide the disk details while importing)
>>Does this mean that the only time I really need to send out new map files is when I add or delete LVs?
NO ..You need to do export and import each time you do any lvm related activity
>>Does adding a PV to a VG and then expanding an LV really require this procedure?
Yes since the lvmtab of the other node will not have any info about the newly added disk
>>It seems that the map file wouldn't contain any new information.
The lvm structure is actually resids on the physical volumes and it is getting updated each time you do any lvm activity like creating lv ,adding ,removing pv etc...
Inorder to sync the updated lvm structure with the kernel/system u need a fresh vgexport and import.
Thanks!!
Johnson
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-27-2009 05:08 PM
тАО05-27-2009 05:08 PM
Re: LVM VG map files
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-28-2009 05:29 AM
тАО05-28-2009 05:29 AM
Re: LVM VG map files
I think the initial source of my confusion was that I sort of assumed that the map file contained a complete VG structure dump, an assumption dashed by actually looking at the map file.
Thanks!