vxprint

[simon_82]

Hi

i am trying to find out information using the vxprint command that will be equal to when using vgdisplay -v.

so far i have used :
1. vxprint -A
2. vxprint -A -g

can anyone help.

Regards
Simon

[Ian Dennison_1]

Question: What does vxprint provide that vgdisplay does not?

Share and Enjoy! Ian

[simon_82]

hi yeah i am trying to see how much is used over two striped disks.
c0t8d0
c0t9d0
regards

[Ian Dennison_1]

Simon,

If you do a vgdisplay -v you can see how many physical extents are allocated to each disk at the bottom.

A pvdisplay -v will show the list of logical volumes on each physical volume, and their sizes.

An lvdisplay -v will show the status of the original and mirror copy of the logical volume, including any stale extents.

Share and Enjoy! Ian

[simon_82]

thanks for that but due to this is veritas i need to know the equivalent in vxvm
regards
simon

[David_246]

Please,please please. If you are in the ability to keep using vxprint, do so !!!!

I cannot say to much her, but you know what I mean.

HP uses vgdisplay indeed and also calculates in PE's. You can read how big a PE is in it's config :
PE Size (Mbytes) 8
Then look at the disk and make the :
--- Physical volumes ---
PV Name /dev/dsk/c1t2d0
PV Status available
Total PE 4340
Free PE 3067
Autoswitch On

Free PE's * PE size, et voila.

Good luck !

Regs David

[Pete Randall · Accepted solution]

Simon,

Have you tried:

vxdisk list
vxprint -g disk_group
vxdg list
vxdisk list disk_group



Pete

[David_246]

Sorry,

Total PE size * Pe size

[David_246]

My big friend !!

You just helped me to become graduated.

So now finaly I am a "graduated fool" :)

Many thanks for your winning points !!


Regs David

[Jeff Schussele]

Hi Simon,

You can also run the Veritas GUI, which will give you any info at any level you desire.

Just export your DISPLAY & run:

/opt/VRTSob/bin/vea &

HTH,
Jeff

[Pete Randall]

Jeff,

Interesting path name. Makes me wonder wat the "VRTSob" stnds for. Where's RZ when we need him?


Pete

[Jeff Schussele]

Hi Pete,

Yep - my guess would be "operational binaries"

And under /opt along with the plain old VRTS, there's
VRTSdbed
~fsdoc
~fspro
~odm
~ordba
~ordoc
~orgui (Would expect it here, huh?)
~vlic
~vmpro
~vxms

If you have any Mission Critical OE installs, check it out. I swear that it looks like Veritas *deliberately* tries to make their SW as difficult & obtuse as possible.

Cheers,
Jeff

[Kenneth Tipper]

The ob in VRTSob is a holdover of obsolete terminology from development days when the concept of a generalized administration utility with plugin specific "providers" (e.g. VRTSvmpro and VRTSfspro) was called an Object Bus.