1833589 Members
4337 Online
110061 Solutions
New Discussion

Re: vgdisplay and bdf

 
Leoanrdo Bowens
Advisor

vgdisplay and bdf

I created a 12gb vg but vgdisplay shows it as 8gb and bdf shows it as 8gb. What is the deal?
Excuses are tools of the incompetent.
13 REPLIES 13
Christopher McCray_1
Honored Contributor

Re: vgdisplay and bdf

Can you post the output of you bdf and your vgdisplay. You may be confusing differences between total PE and allocated PE, but let's see what you have first.
It wasn't me!!!!
A. Clay Stephenson
Acclaimed Contributor

Re: vgdisplay and bdf

First of all, bdf will really show you nothing about the volume group or even the logical volume - it is for filesystems and nobody ever said that a filesystem HAS to fill the entire logical volume.

However, if vgdisplay shows 8GB that is what it is. If you post your vgdisplay -v output, we may be able to help. It looks like you simply created an 8GB vg. It is possible than when you dis the pcvreate you specified a smaller disk size arg. Normally, -s is not specfied and pvcreate is able to determine the disk size itself.
If it ain't broke, I can fix that.
linuxfan
Honored Contributor

Re: vgdisplay and bdf

Hi,

Is there a possibility that you have alternate paths to the same disk?

The output of vgdisplay -v would be helpful in analyzing the problem.

-Ramesh
They think they know but don't. At least I know I don't know - Socrates
Leoanrdo Bowens
Advisor

Re: vgdisplay and bdf

Here is what I get.

vgdisplay

--- Logical volumes ---
LV Name /dev/vg12/lvol1
LV Status available/syncd
LV Size (Mbytes) 12000
Current LE 3000
Allocated PE 3000
Used PV 1

bdf
/dev/vg12/lvol1 8192000 2754792 5099275 35% /zrtph0ag_u01/home/oracle/admin/dcodb1/arch
Excuses are tools of the incompetent.
Patrick Wallek
Honored Contributor

Re: vgdisplay and bdf

When you created the logical volume and did an fsadm or newfs of it, did you specify the entire 12GB? My guess would be that you just newfs'd 8GB and not the entire usable space.
A. Clay Stephenson
Acclaimed Contributor

Re: vgdisplay and bdf

Hi:

Vgdisplay does show it to be a 12GB lvol; you simply created a smaller filesystem within it.
If it ain't broke, I can fix that.
Leoanrdo Bowens
Advisor

Re: vgdisplay and bdf

Did it all through SAM

--- Logical volumes ---
LV Name /dev/vg12/lvol1
LV Status available/syncd
LV Size (Mbytes) 12000
Current LE 3000
Allocated PE 3000
Used PV 1

LV Name /dev/vg12/lvol2
LV Status available/syncd
LV Size (Mbytes) 8000
Current LE 2000
Allocated PE 2000
Used PV 2

LV Name /dev/vg12/lvol3
LV Status available/syncd
LV Size (Mbytes) 18800
Current LE 4700
Allocated PE 4700
Used PV 2

LV Name /dev/vg12/lvol4
LV Status available/syncd
LV Size (Mbytes) 18124
Current LE 4531
Allocated PE 4531
Used PV 1


--- Physical volumes ---
PV Name /dev/dsk/c19t14d4
PV Name /dev/dsk/c21t14d4 Alternate Link
PV Status available
Total PE 4744
Free PE 0
Autoswitch On

PV Name /dev/dsk/c19t14d5
PV Name /dev/dsk/c21t14d5 Alternate Link
PV Status available
Total PE 4744
Free PE 0
Autoswitch On

PV Name /dev/dsk/c19t14d6
PV Name /dev/dsk/c21t14d6 Alternate Link
PV Status available
Total PE 4744
Free PE 1
Autoswitch On
Excuses are tools of the incompetent.
linuxfan
Honored Contributor

Re: vgdisplay and bdf

Hi,

Is it possible you did lvextend but did not do a fsadm or a extendfs. You DON'T want to do a newfs(newfs will overwrite all the data).

If you have online JFS, you could just do
fsadm -F vxfs -b $((12*1024*1024)) /zrtph0ag_u01/home/oracle/admin/dcodb1/arch

If you don't have online JFS, you will have to unmount the filesystem

umount /zrtph0ag_u01/home/oracle/admin/dcodb1/arch

and then extend the filesystem extendfs -F vxfs /dev/vg12/lvol1

and then mount it back
mount /zrtph0ag_u01/home/oracle/admin/dcodb1/arch

-Ramesh
They think they know but don't. At least I know I don't know - Socrates
James R. Ferguson
Acclaimed Contributor

Re: vgdisplay and bdf

Hi:

If you have 'lvextend'ed your logical volume but *not* used 'extendfs' or 'fsadm' (if you are using Online JFS (VxFS) to extend the filesystem, then 'bdf' will not show your expected size.

Regards!

...JRF...
A. Clay Stephenson
Acclaimed Contributor

Re: vgdisplay and bdf

Hi again:

One more thought, it your don't have a lost+found directory, fsadm cannot create a .fsadm file and the extend of the filesystem will fail (if this was an extend of an existing filesystem).
If it ain't broke, I can fix that.
Alan Riggs
Honored Contributor

Re: vgdisplay and bdf

If you have purchased and installed online JFS do:

fsadm -F vxfs -b 12288000

If not, do:
umount
extendfs
Juergen Nagel_1
Frequent Advisor

Re: vgdisplay and bdf

Hi,
This could be after an lvdisplay. In this case you should run:
extendfs ?F /dev/vg12/rlvol1
You have to umount the filesystem.

bye
Santosh Nair_1
Honored Contributor

Re: vgdisplay and bdf

If you have the luxury of umounting the filesystem, then you can run extendfs on it:

extendfs -F vxfs /dev/vg12/rlvol1

Otherwise, if you have OnlineJFS, use fsadm:

fsadm -F vxfs -b 12000M /zrtph0ag_u01/home/oracle/admin/dcodb1/arch

-Santosh
Life is what's happening while you're busy making other plans