- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Redundant VGID LV sneaked in
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
тАО12-13-2002 04:29 AM
тАО12-13-2002 04:29 AM
Redundant VGID LV sneaked in
yesterday I had to add new PVs to a MC/SG cluster package's shared VG.
While issuing the (preview) vgexport in order to create a map file for distribution to failback nodes, somehow (unfortunately unnoticed by me) a bogus VGID LV sneaked in:
# head -3 vgb01_20021212.map
VGID 29256fe4392e2fd8
1 VGID
1 lvol1
Today, when I wanted to extend the filesystems on the LVs I stumbled over the bogus LV and realized what happened.
As I wasn't sure, so far I only cleaned the LVM metadata from the cluster nodes that currently don't run the package,
and I still refrained from issueing an lvremove of VGID on the node that runs the package and has the real LV mounted.
Btw, when inspecting the LVM layout of this VG (and PVs) with the commands vgdisplay, lvdisplay, pvdisplay the bogus VGID LV appears to be treated as an alias (i.e. exactly same data, mounting of it fails but croaks device busy)
Any idea if it's safe to do the lvremove on the package holding node?
Regards
Ralph
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-13-2002 04:33 AM
тАО12-13-2002 04:33 AM
Re: Redundant VGID LV sneaked in
DON'T run lvremove. Just remove the device files /dev/vg??/VGID and /dev/vg??/rVGID.
Regards,
John
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-13-2002 05:13 AM
тАО12-13-2002 05:13 AM
Re: Redundant VGID LV sneaked in
VGID 29256fe4392e2fd8
1 VGID
1 lvol1
Then vgimport again.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-13-2002 06:37 AM
тАО12-13-2002 06:37 AM
Re: Redundant VGID LV sneaked in
I had done this already when I cleaned the LVM config for the other nodes.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-13-2002 06:45 AM
тАО12-13-2002 06:45 AM
Re: Redundant VGID LV sneaked in
will simple removal of redundant device files suffice?
I think for instance vgdisplay will still list the bogus LV though.
(well, you could call this a mere cosmetic detriment)
The device files are all referenced through individual inodes:
# ll -i /dev/vgb01/*
2479 brw-r----- 1 root sys 64 0x080001 Mar 12 2001 /dev/vgb01
/VGID
2480 crw-r--r-- 1 root sys 64 0x080000 Mar 12 2001 /dev/vgb01
/group
2481 brw-r----- 1 root sys 64 0x080001 Mar 12 2001 /dev/vgb01
/lvol1
2482 crw-r----- 1 root sys 64 0x080001 Mar 12 2001 /dev/vgb01
/rVGID
2483 crw-r----- 1 root sys 64 0x080001 Mar 12 2001 /dev/vgb01
/rlvol1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-13-2002 08:10 AM
тАО12-13-2002 08:10 AM
Re: Redundant VGID LV sneaked in
Yes, John is right, a simple removal is enough. Vgdisplay tries to find any information related to entries in /dev/vgXX. For example, if you create dummy entries (lvol and rlvol) with other minor numbers, vgdisplay will display them with a 0 size.
Regards.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-13-2002 08:19 AM
тАО12-13-2002 08:19 AM
Re: Redundant VGID LV sneaked in
I agree with John. Simply remove the "VGID" device files.
I built a volume group with a logical volume. I then inactivated it ('vgchange -a n') and created ('mknod') device files with the same minor number. Thus an 'ls -l /dev/vgXX/*' looks like your presentation.
When I activated the volume group and did a 'vgdisplay -v' you see a current LV count of <1> but an open LV count of <2>. Doing a 'lvdisplay -v' of the "real" LV or the one named "VGID" shows extent mapping to the same physical extents as you would expect.
Regards!
...JRF...