- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- lvm warning message
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
Forums
Discussions
Discussions
Discussions
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
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
03-05-2003 10:13 PM
03-05-2003 10:13 PM
lvm warning message
Warning: logical volume number xxxx found in physical volume not found in /dev/vg01.
I've attached a few old discs to this workstation to do some lvm testing. I noticed one already had a boot partition. So, I thought I'd import it and see if there is already an OS installed. the import went fine. I tried import a second disc and vgimport wasn't able to find any lvm information. So, I did a pvcreate -B on this disc. and then a vgextend to add it to vg01 So, I was going to mirror this drive to the one I had imported. everything seems to work fine, except I get the above warning message whenever i do a lvextend to create a mirror or a lvreduce to remove the mirror.
any clues to the cause or a way to stop getting the message.
thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-05-2003 11:52 PM
03-05-2003 11:52 PM
Re: lvm warning message
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-06-2003 07:18 AM
03-06-2003 07:18 AM
Re: lvm warning message
no extras, none missing.
pvdisplay shows 8 lvols and vgdisplay shows 8 lvols
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-06-2003 07:23 AM
03-06-2003 07:23 AM
Re: lvm warning message
0x010001
0x010002, etc?
If so that's incorrect. The minor #'s should be:
0x010000
0x020000
0x030000, etc......
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-06-2003 07:47 AM
03-06-2003 07:47 AM
Re: lvm warning message
0x010000 = group
0x010001 = lvol1 and rlovl1
0x010002 = lvol2 and rlvol2
The lvol that you're having the problem extending, try to recreate its device files .. for instance if it's lvol2..
# mknod /dev/vg01/rlvol2 c 64 0x010002
# mknod /dev/vg01/lvol2 b 64 0x010002
What about the rest of the lvols ? Do you get the same error when you extend it ? Another thing I noticed ..why pvcreate with the -B option, you meant -f I hope.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-06-2003 08:20 AM
03-06-2003 08:20 AM
Re: lvm warning message
I've tried removing lvol8 and rlvol8 and recreating the nodes. No change. Still getting same warning message when doing a lvreduce to remove a mirror or a lvextend to add a mirror copy.
I did get the warning message when extending every lvol to add a mirrored copy. But, I've been doing my testing (making changes) just to lvol8 so far.
adding the second disk. vgimport reported no lvm structures on the disk. I did a pvcreate -B (no -f option was given). pvcreate finished sucessfully, with no messages of their being previous lvm structues on the disk being destroyed.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-06-2003 11:42 AM
03-06-2003 11:42 AM
Re: lvm warning message
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-06-2003 05:22 PM
03-06-2003 05:22 PM
Re: lvm warning message
...So, I was going to mirror this drive to the one I had imported...
Could you provide the syntax of the vgexport and vgimport please?
Also, could you now create another map file and check it against your old map file as well as your /etc/lvmtab file? With specific attention to the disks and VGID?
vgexport -m mapfile -p /dev/vg01
strings /etc/lvmtab | more
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-07-2003 08:10 AM
03-07-2003 08:10 AM
Re: lvm warning message
I don't know the prior history of the discs. Maybe they were exported, maybe not. No, I didn't have a mapfile for importing the disc.
vgimport /dev/vg01 /dev/dsk/c1t6d0
vgexport -m mapfile -p /dev/vg01
strings /etc/lvmtab | more
the attached file has this information.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-08-2003 12:29 PM
03-08-2003 12:29 PM
Re: lvm warning message
1)vgchange -a n /dev/vg##
2)vgexport -p -v -s -m mapfile /dev/vg##
3)vgexport -v -s -m mapfile /dev/vg## (* NOTE: This will update /etc/lvmtab and remove the volume group *)
For vgimport use:
a)mkdir /dev/vg##
b)mknod /dev/vg##/group -c 64 0x0#0000 (* NOTE: 0x0#0000 must be unique *)
c)vgimport -s -p -m mapfile /dev/vg## (*NOTE: This will preview and display responding disks *)
d1)vgimport -s -m mapfile /dev/vg## (* Create *)
d2)Alternative if d1) fails:
vgimport /dev/vg## /dev/dsk/c#t#d0 (* NOTE: As you have done *)
I'm looking for a disconnect with the VGID and the disks associated to the VG and /etc/lvmtab. They should all match up.