vxdisk list question

vxdisk list question

Post by boog » Fri, 08 Mar 2002 07:36:54



I started having slow response time on an turn key application running
on a solaris 2.6. So, I called the vendor and they told me that there
is nothing wrong. I wish they could tell that to my users. So in
desperation I run **vxdisk list** and I have no idea what it is all I
was told the system is using veritas volume manager.

I found few volume manager commands but no man pages. And when I ran
**vxdisk list** I got the following out. How do I interpret or read
the output? Do I have a problem? Thanks for any help.

c0t0d0s2     sliced    -            -            error
c0t1d0s2     sliced    disk01       rootdg       online spare
c0t2d0s2     sliced    disk04       rootdg       online
c0t3d0s2     sliced    disk05       rootdg       online
c2t0d0s2     sliced    disk02       rootdg       online
c2t1d0s2     sliced    disk03       rootdg       online
c2t2d0s2     sliced    disk06       rootdg       online
c2t3d0s2     sliced    disk07       rootdg       online
c3t0d0s2     sliced    disk08       rootdg       online
c3t1d0s2     sliced    disk09       rootdg       online

 
 
 

vxdisk list question

Post by Joe Blogg » Fri, 08 Mar 2002 07:44:58



Quote:> I started having slow response time on an turn key application running
> on a solaris 2.6. So, I called the vendor and they told me that there
> is nothing wrong. I wish they could tell that to my users. So in
> desperation I run **vxdisk list** and I have no idea what it is all I
> was told the system is using veritas volume manager.

> I found few volume manager commands but no man pages. And when I ran
> **vxdisk list** I got the following out. How do I interpret or read
> the output? Do I have a problem? Thanks for any help.

> c0t0d0s2     sliced    -            -            error
> c0t1d0s2     sliced    disk01       rootdg       online spare
> c0t2d0s2     sliced    disk04       rootdg       online
> c0t3d0s2     sliced    disk05       rootdg       online
> c2t0d0s2     sliced    disk02       rootdg       online
> c2t1d0s2     sliced    disk03       rootdg       online
> c2t2d0s2     sliced    disk06       rootdg       online
> c2t3d0s2     sliced    disk07       rootdg       online
> c3t0d0s2     sliced    disk08       rootdg       online
> c3t1d0s2     sliced    disk09       rootdg       online

Suspect the man pages weren't installed.  Try a grep for vxprint in
/var/sadm/install/contents, see if any man pages show up for the vxprint
command.

Either install the man pages, or view 'em at

e3%2Fcoll3%2FSUNWasevm%2Ftoc%2FSUNWab_263_1%3ASUNWab_263_1%3Aclose&Ab2Lang=C
&Ab2Enc=iso-8859-1

...and yes, you could well have an error.

"vxprint -Ath" offers more information than ust vxdisk list.

 
 
 

vxdisk list question

Post by Darren Dunha » Sun, 10 Mar 2002 02:32:46



> I started having slow response time on an turn key application running
> on a solaris 2.6. So, I called the vendor and they told me that there
> is nothing wrong. I wish they could tell that to my users. So in
> desperation I run **vxdisk list** and I have no idea what it is all I
> was told the system is using veritas volume manager.
> I found few volume manager commands but no man pages. And when I ran
> **vxdisk list** I got the following out. How do I interpret or read
> the output? Do I have a problem? Thanks for any help.
> c0t0d0s2     sliced    -            -            error

That line simply means that disk c0t0d0 is not under VxVM control.  If
it used to be and had failed, you would have an additional line showing
a failure.  

Quote:> c0t1d0s2     sliced    disk01       rootdg       online spare
> c0t2d0s2     sliced    disk04       rootdg       online
> c0t3d0s2     sliced    disk05       rootdg       online
> c2t0d0s2     sliced    disk02       rootdg       online
> c2t1d0s2     sliced    disk03       rootdg       online
> c2t2d0s2     sliced    disk06       rootdg       online
> c2t3d0s2     sliced    disk07       rootdg       online
> c3t0d0s2     sliced    disk08       rootdg       online
> c3t1d0s2     sliced    disk09       rootdg       online

Since there are no failures, this output shows nothing suspicious to me.

I think you're going to have to characterize the slowness first.  CPU or
disk?  Anything suspicous in vmstat or iostat...?

--

Unix System Administrator                    Taos - The SysAdmin Company
Got some Dr Pepper?                           San Francisco, CA bay area
          < How are you gentlemen!! Take off every '.SIG'!! >

 
 
 

vxdisk list question

Post by Fran » Thu, 14 Mar 2002 03:40:32




Quote:> I started having slow response time on an turn key application running
> on a solaris 2.6. So, I called the vendor and they told me that there
> is nothing wrong. I wish they could tell that to my users. So in
> desperation I run **vxdisk list** and I have no idea what it is all I
> was told the system is using veritas volume manager.

> I found few volume manager commands but no man pages. And when I ran
> **vxdisk list** I got the following out. How do I interpret or read
> the output? Do I have a problem? Thanks for any help.

> c0t0d0s2     sliced    -            -            error
> c0t1d0s2     sliced    disk01       rootdg       online spare
> c0t2d0s2     sliced    disk04       rootdg       online
> c0t3d0s2     sliced    disk05       rootdg       online
> c2t0d0s2     sliced    disk02       rootdg       online
> c2t1d0s2     sliced    disk03       rootdg       online
> c2t2d0s2     sliced    disk06       rootdg       online
> c2t3d0s2     sliced    disk07       rootdg       online
> c3t0d0s2     sliced    disk08       rootdg       online
> c3t1d0s2     sliced    disk09       rootdg       online

Hi,

To read the manual pages for Veritas Volumen Manager  you must expand your
MANPATH like
MANPATH=$MANPATH:/opt/VRTSvxvm/man:/opt/VRTSvmsa/man; export MANPATH
The path may be different if you have a vxvm version <3.0 (you may check
with pkginfo).
The output from vxdisk list:
c0t0d0        not under Veritas control (your boot disk?)
c0t1d0        member of diskgroup rootvg, spare disk for the case another
disk fails
c0t2d0-c3t1d0    members of rootvg; no chance to guess layout etc. from this
output; vxprint will help here.
About perfomance I can say nothing without furhter information. Look at
vxstat to get deatils for vxvm performance. But are thounds of other reasons
why the system is slow.

Hope this helps.

Frank