LVM PB

[Ibrahima BADJI_1]

I have already existing VG00 containing one physical volume(c0t2d0)on a RP7410 running HP-UX 11.0 on which.

I wanted to add an onther physical volume(c0t3d0)in order to mirror the first one.

But when I enter the command vgextend I receive the following error message:

vgextend:cannot execut, verify that the minor number for VG00 is unique

With the command ll /dev/ I've verified that there is not any duplicate minor numver between VGs or LVOLs.

How can i solve this case?

[Uday_S_Ankolekar]

IF you want to mirror boot disk here is the process..

pvcreate -B /dev/rdsk/c0t3d0;
vgextend /dev/vg00 /dev/dsk/c0t3d0,
mkboot -l /dev/rdsk/c0t3d0,
mkboot -a "hpux" /dev/rdsk/c0t3d0
mkboot -a "hpux -lq" /dev/rdsk/c0t3d0
lifcp /dev/rdsk/c0t3d0:AUTO -
setboot -a from iosan ex:0/0/2/0.3.0
lvextend -m 1 /dev/vg00/lvol1 /dev/dsk/c0t3d0 and do it for all other lvols in vg00
lvlnboot -b /dev/vg00/lvol1 /dev/vg00, lvlnboot -s /dev/vg00/lvol2 /dev/vg00, lvlnboot -d /dev/vg00/lvol2 /dev/vg00, lvlnboot -r /dev/vg00/lvol3 /dev/vg00

lvlnboot -v will now show you two boot disks. mirrored to each other

-Goodluck.
-USA..

[Pete Randall]

I would double check your minor numbers with ll /dev/vg*/group.

Example:

root# ll /dev/vg*/group
crw-r----- 1 root sys 64 0x000000 Feb 14 2000 /dev/vg00/group
crw-rw-rw- 1 root root 64 0x010000 Jul 13 2002 /dev/vg01/group
crw-rw-rw- 1 informix informix 64 0x020000 Jul 13 2002 /dev/vg02/group
crw-rw-r-- 1 informix informix 64 0x060000 Jul 19 2002 /dev/vg20/group
crw-r--r-- 1 root sys 64 0x030000 Jun 27 2000 /dev/vgswap/group


Pete

[RAC_1]

Post

ll /dev/*

Also did you do pvcreate on disk?

[Pete Randall]

Note that, in the example, all the minor numbers (the first two numbers after the 0x) are unique.


Pete

[Pete Randall]

Also, have you run the pvcreate yet?


Pete

[Jeff Schussele]

Hi,

If you have MC/SG or have had it on this system it creates a file /dev/slvmvg with the same major/minor numbers.

If it's there then mv it to temp, rename /etc/lvmtab & run vgscan -v

If it's not there then just rename lvmtab & run vgscan -v

HTH,
Jeff

BTW - see this TKB doc:

http://www1.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&admit=-682735245+1071252229477+28353475&docId=200000067003049

[Jeff Schussele]

I should have said..

mv it to /tmp

And the problem is that file can cause vgscan to corrupt the lvmtab file.

Rgds,
Jeff

[Ibrahima BADJI_1]

with ll /dev/vg*/group, I don't find any duplicated inor number, and comands like vgdisplay, vgextend don't work.

And necessarely, I must add a second physical volue to this existing VG00 while vgextend does not work. How to do?

[Jeff Schussele]

Did you check for that /dev/slvmvg file & follow the instructions I gave you?

You probably have a corrupted /etc/lvmtab file & until you do those cleanup steps I listed you'll be unsuccessful with this vgextend.

Rgds,
Jeff

[Robert-Jan Goossens]

Hi,

If you can not open Jeff's link, take a look at next thread.

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=262807

Hope this helps,
Robert-Jan

[Todd McDaniel_1]

Ibrahima,

Do as suggested and move the lvmtab out of the way and do:

vgscan ##to replace the lvmtab...there may be corruption in there.

Then try to add the disk again... I am somewhat puzzled why you get minor number errors when simply vgextending a VG. but it should be fixed with vgscan to recreate the lvmtab.

ALSO, you should pvcreate -fB on teh disk to wipe out any header info it may have on it.

[Lorenzo Facello]

Hi,
try
pvcreate -f -B (if bootable) /dev/rdsk/cxxxxx
vgextend vg00 /dev/dsk/cxxxxx

Regds.
L.