cannot access vg00 through sam, vgdisplay show error

[DnD_1]

hi guys,

i tried to extend the logical volume for lvo13 but got some error from vgdisplay.

SAM also show nothing about vg00.

anyone please help ?

# vgdisplay
vgdisplay: Couldn't query volume group "/dev/vg00".
Possible error in the Volume Group minor number; Please check and make sure the group minor number is unique.
vgdisplay: Cannot display volume group "/dev/vg00".

--- Volume groups ---
VG Name /dev/vg01
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 1
Open LV 1
Max PV 16
Cur PV 1
Act PV 1
Max PE per PV 17502
VGDA 2
PE Size (Mbytes) 4
Total PE 17499
Alloc PE 17499
Free PE 0
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

VG Name /dev/Vgstore
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 1
Open LV 1
Max PV 16
Cur PV 1
Act PV 1
Max PE per PV 17502
VGDA 2
PE Size (Mbytes) 4
Total PE 17499
Alloc PE 17499
Free PE 0
Total PVG 0
Total Spare PVs

$bdf
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 147456 140191 6867 95% /
/dev/vg00/lvol1 111637 30218 70255 30% /stand
/dev/vg00/lvol8 655360 509825 136488 79% /var
/dev/vg00/lvol7 1130496 854200 259066 77% /usr
/dev/vg00/lvol4 65536 10205 51934 16% /tmp
/dev/Vgstore/lvol1 71675904 32739224 38643928 46% /storage
/dev/vg00/lvol6 32768000 8024152 24357296 25% /opt
/dev/vg01/lvol1 71675904 27478360 43852272 39% /data

[Pete Randall · Accepted solution]

Post the output of "ll /dev/vg*/group" or examine it your self and look for duplicate minor numbers:

crw-r----- 1 root sys 64 0x000000 Mar 15 2004 /dev/vg00/group
cr--r--r-- 1 root sys 64 0x010000 Mar 30 2004 /dev/vg01/group
crw-rw-r-- 1 informix informix 64 0x020000 Mar 30 2004 /dev/vg02/group

The first two numbers after the "0x" are the minor number.


Pete

[John Guster]

First of all you have to reignite the system in order to extend lvol3 which is / file system.

What does "strings /etc/lvmtab" tell?

[Victor Fridyev]

Also you can rename /etc/lvmtab and run vgscan , which will create new /etc/lvmtab.
Take into account that you may have to import all additional file systems after this operation.

HTH

[Pete Randall]

John,

>> First of all you have to reignite the system in order to extend lvol3

I thought that, too, at first, but the author said lvol13, so I'm not sure what to think now. A little further clarification might be nice.


Pete

[Torsten.]

He said "lvo13" - could be anything ;-)

[DnD_1]

hi all,

thanks for the answer,

actually i want to extend this LV.

/dev/vg00/lvol3 147456 140191 6867 95% /

which already 95%, all our charging method failed :(

i will get back all the information soon i got back to the office tomorrow.

[Pete Randall]

In that case, you will need to use Ignite, but you will also first need to straighten out the problem with your minor numbers. Then we can get into the issues with lvol3. Normally the / file system should be static and significant growth within it can be traced to some sort of correctable error.


Pete

[Tim Nelson]

You will NOT be able to extend the root lvol !!!!! It must be contiguous !!!

Create an Ignite image and interactively rebuild your system giving a new lvol size.

Otherwise,

1) fix / post your vg00 info as asked

2) find the files that should NOT be in "/".

the root filesytem should be, and stay, static for just about the life of your install. Get the other junk out of there.

[DnD_1]

hi again,

ok, so i cant extend lvo13 :(

inside lvo13, we have

$:/data/home/charging.

/data is under /dev/vg01/lvol1

and /home is directly under /

in that case, can i extend /home ?