topic Re: cannot access vg00 through sam, vgdisplay show error in Operating System - HP-UX

cannot access vg00 through sam, vgdisplay show error

DnD_1 — Thu, 09 Oct 2008 13:57:07 GMT

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

Re: cannot access vg00 through sam, vgdisplay show error

Pete Randall — Thu, 09 Oct 2008 14:04:55 GMT

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

Re: cannot access vg00 through sam, vgdisplay show error

John Guster — Thu, 09 Oct 2008 14:41:07 GMT

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

What does "strings /etc/lvmtab" tell?

Re: cannot access vg00 through sam, vgdisplay show error

Victor Fridyev — Thu, 09 Oct 2008 14:45:13 GMT

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

Re: cannot access vg00 through sam, vgdisplay show error

Pete Randall — Thu, 09 Oct 2008 15:17:24 GMT

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

Re: cannot access vg00 through sam, vgdisplay show error

Torsten. — Thu, 09 Oct 2008 15:19:21 GMT

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

Re: cannot access vg00 through sam, vgdisplay show error

DnD_1 — Thu, 09 Oct 2008 15:48:35 GMT

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.

Re: cannot access vg00 through sam, vgdisplay show error

Pete Randall — Thu, 09 Oct 2008 16:04:33 GMT

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

Re: cannot access vg00 through sam, vgdisplay show error

Tim Nelson — Thu, 09 Oct 2008 16:41:55 GMT

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.

Re: cannot access vg00 through sam, vgdisplay show error

DnD_1 — Thu, 09 Oct 2008 18:07:38 GMT

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 ?

Re: cannot access vg00 through sam, vgdisplay show error

Torsten. — Thu, 09 Oct 2008 18:13:51 GMT

It's time to make it clear now ...

Is it LVOL13, LVOL3, or something else?
Is it in vg00?

Re: cannot access vg00 through sam, vgdisplay show error

Torsten. — Thu, 09 Oct 2008 18:15:18 GMT

Please post the output of

# mount

Re: cannot access vg00 through sam, vgdisplay show error

DnD_1 — Thu, 09 Oct 2008 19:00:50 GMT

hi thanks all for the help.

i will post all the information tomorrow

dont go awaaaaay !! :)

Re: cannot access vg00 through sam, vgdisplay show error

sen_ux — Fri, 10 Oct 2008 04:54:47 GMT

Hi All,
lvol3 can be extended if there is a free disk and free space available on root disk.Not sure whether it is supported/recommended.But it was success for me.

Steps Done.

1.Moved lvol4 to lvol8 to another disk using pvmove.
2.extended the lvol3 ( Online JFS )
3.moved back the lvols.(pvmove)

Rebooted and tested.All was fine.

Anybody tried this.
Can anybody suggest on this method.

Regards
sen

Re: cannot access vg00 through sam, vgdisplay show error

sreekanthtm — Fri, 10 Oct 2008 06:05:50 GMT

Hi,

You can extend the / (root filesystem) /dev/vg00/lvol3 as decribed

1.Moved lvol4 to lvol8 to another disk using pvmove.
2.extended the lvol3 ( Online JFS )
3.moved back the lvols.(pvmove)

But this not a recommended method.....
And one more thing, here size of lvol3 is around 65MB. So you can extend lvol3 by a maximum of 65MB.
HP recommend to restore the ignite backup to extend root file system.
But before taking an ignite backup, make sure that your vg00 is error free..... Please post all the o/p as suggested by experts.....

Cheers
Sreekanth

Re: cannot access vg00 through sam, vgdisplay show error

sen_ux — Fri, 10 Oct 2008 06:31:02 GMT

Sreekanth,
>>>>And one more thing, here size of lvol3 is around 65MB. So you can extend lvol3 by a maximum of 65MB

Could you expalin this much better,?

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

sen

Re: cannot access vg00 through sam, vgdisplay show error

DnD_1 — Fri, 10 Oct 2008 06:37:02 GMT

Hi all,

To simplify what i want to do,

The directory /home are located under lvol3, and it 95% full

$bdf
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 147456 140191 6867 95% /

md2:/home$df -k .
/ (/dev/vg00/lvol3 ) : 147088 total allocated Kb
6409 free allocated Kb
140679 used allocated Kb
95 % allocation used

so i want to extend it, but vgdisplay show error as above.

# ll /dev/vg*/group
crw-r----- 1 root sys 64 0x000000 Jul 18 17:02 /dev/vg00/group
cr--r--r-- 1 root sys 64 0x010000 Jul 31 12:16 /dev/vg01/group
#

# mount
/ on /dev/vg00/lvol3 log on Thu Oct 9 14:04:34 2008
/stand on /dev/vg00/lvol1 defaults on Thu Oct 9 14:04:35 2008
/var on /dev/vg00/lvol8 delaylog,nodatainlog on Thu Oct 9 14:04:40 2008
/usr on /dev/vg00/lvol7 delaylog,nodatainlog on Thu Oct 9 14:04:40 2008
/tmp on /dev/vg00/lvol4 delaylog,nodatainlog on Thu Oct 9 14:04:40 2008
/storage on /dev/Vgstore/lvol1 delaylog,nodatainlog,nolargefiles on Thu Oct 9 14:04:40 2008
/opt on /dev/vg00/lvol6 delaylog,nodatainlog on Thu Oct 9 14:04:40 2008
/data on /dev/vg01/lvol1 delaylog,nodatainlog,nolargefiles on Thu Oct 9 14:04:40 2008
#

Re: cannot access vg00 through sam, vgdisplay show error

DnD_1 — Fri, 10 Oct 2008 07:26:57 GMT

hi all,

my issue solved.

all i done is

# mv /etc/lvmtab /etc/lvmtab.save
# vgscan -v
# vgchange -a y vg00
# vgdisplay vg00

thanks !!

Re: cannot access vg00 through sam, vgdisplay show error

sreekanthtm — Fri, 10 Oct 2008 07:39:53 GMT

OK.... gd job.
But freeup some space is /dev/vg00/lvol3 (root). Its already 95%, otherwise you would be fell down to even big issue.... :)

Sen,

Size of lvol4 is 65 MB. While creating Lvol's PE's allocated in serial manner. After lvol4, the immediate PE would be already allocated to some other LV. As root file system demands continuous allocation of PE you cannot exceed the size of lvol4 (Here it is 65MB). Otherwise you have to delete subsequent LV.

Rgds
Sreekatnh

Re: cannot access vg00 through sam, vgdisplay show error

sen_ux — Fri, 10 Oct 2008 08:13:47 GMT

Sreekanth,

I understood what 65 MB is.

What I have done is to move all LVs after lvol4..
ie..lvol3,lvol4,6,7,8 to another disk.

If enough space is there in the root disk, u can increase the size as much u want.

Thanks
sen