SEO

hi, i got the below when i enter vgdisplay

vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/pvg60".
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/pvg80".
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/pvg70".


what is this all about?

In article <c06e4d68.0407112351.13fe03b2@posting.google.com >, yls177 wrote:
> hi, i got the below when i enter vgdisplay
>
> vgdisplay: Volume group not activated.
> vgdisplay: Cannot display volume group "/dev/pvg60".
> vgdisplay: Volume group not activated.
> vgdisplay: Cannot display volume group "/dev/pvg80".
> vgdisplay: Volume group not activated.
> vgdisplay: Cannot display volume group "/dev/pvg70".
>
>
> what is this all about?

Pretty much exactly what it says. HP volume groups must be
activated before they can be accessed. Either there's something
amiss with these three volume groups or they're not configured to
activate on boot. About the only reason that I know of not to configure
volume groups on boot is if they're used in a ServiceGuard cluster.
I'm sure there are other reasons; that's the only one coming to mind
now.

Assuming this is *not* a serviceguard cluster, check the system log
in /var/adm/syslog/syslog.log to see if there's anything in there
referencing these volume groups. Troubleshoot as necessary. If
there's nothing in the syslog, try "vgchange -a y pvg60"
to activate the group. Troubleshoot as necessary.

HTH;

Doug


--
--------
Senior UNIX Admin
O'Leary Computer Enterprises
dkoleary@olearycomputers.com (w) 630-904-6098 (c) 630-248-2749
resume: http://www.olearycomputers.com/resume.html

Doug O'Leary <dkoleary@olearycomputers.com> wrote in message news:<qBxIc.3088$696.1138@fe07.usenetserver.com>.. .
> In article <c06e4d68.0407112351.13fe03b2@posting.google.com >, yls177 wrote:
> > hi, i got the below when i enter vgdisplay
> >
> > vgdisplay: Volume group not activated.
> > vgdisplay: Cannot display volume group "/dev/pvg60".
> > vgdisplay: Volume group not activated.
> > vgdisplay: Cannot display volume group "/dev/pvg80".
> > vgdisplay: Volume group not activated.
> > vgdisplay: Cannot display volume group "/dev/pvg70".
> >
> >
> > what is this all about?
>
> Pretty much exactly what it says. HP volume groups must be
> activated before they can be accessed. Either there's something
> amiss with these three volume groups or they're not configured to
> activate on boot. About the only reason that I know of not to configure
> volume groups on boot is if they're used in a ServiceGuard cluster.
> I'm sure there are other reasons; that's the only one coming to mind
> now.
>
> Assuming this is *not* a serviceguard cluster, check the system log
> in /var/adm/syslog/syslog.log to see if there's anything in there
> referencing these volume groups. Troubleshoot as necessary. If
> there's nothing in the syslog, try "vgchange -a y pvg60"
> to activate the group. Troubleshoot as necessary.
>
> HTH;
>
> Doug


yes, u are right.. i am on serviceguard cluster and the dmesg appears
in my adoptive node and not in my productive node.

yls177@hotmail.com (yls177) wrote:

>hi, i got the below when i enter vgdisplay
>
>vgdisplay: Volume group not activated.
>vgdisplay: Cannot display volume group "/dev/pvg60".
>vgdisplay: Volume group not activated.
>vgdisplay: Cannot display volume group "/dev/pvg80".
>vgdisplay: Volume group not activated.
>vgdisplay: Cannot display volume group "/dev/pvg70".
>
>
>what is this all about?

As it says, these volume groups are not activated on this node.

Are you running a ServuceGuard cluster?
If so all packaged volume groups are defined on all nodes in the
cluster but only activated on the node currently running the package.

Regards.

Ted.
================================================== ============
| Ted Linnell <edlinnell@acslink.net.au> |
| |
| Nunawading, Victoria , Australia |
================================================== ============

Ted Linnell <edlinnell@acslink.net.au> wrote in message news:<75j4f0h6k5bikicl4t4132ujnu32d94ts6@4ax.com>. ..
> yls177@hotmail.com (yls177) wrote:
>
> >hi, i got the below when i enter vgdisplay
> >
> >vgdisplay: Volume group not activated.
> >vgdisplay: Cannot display volume group "/dev/pvg60".
> >vgdisplay: Volume group not activated.
> >vgdisplay: Cannot display volume group "/dev/pvg80".
> >vgdisplay: Volume group not activated.
> >vgdisplay: Cannot display volume group "/dev/pvg70".
> >
> >
> >what is this all about?
>
> As it says, these volume groups are not activated on this node.
>
> Are you running a ServuceGuard cluster?
> If so all packaged volume groups are defined on all nodes in the
> cluster but only activated on the node currently running the package.
>
> Regards.
>
> Ted.
> ================================================== ============
> | Ted Linnell <edlinnell@acslink.net.au> |
> | |
> | Nunawading, Victoria , Australia |
> ================================================== ============



yes, u are totally right. my current setup. i have 3 L-class, DEV,
QAS, PRD. the latter two are on serviceguard with a one package
concept.

from Ted previous post, all the volume groups in QAS, PRD are in the
cluster? QAS, PRD has their own volume groups with logical volumes
and filesystems, and are these in the cluster too?

yls177@hotmail.com (yls177) wrote:

>Ted Linnell <edlinnell@acslink.net.au> wrote in message news:<75j4f0h6k5bikicl4t4132ujnu32d94ts6@4ax.com>. ..
>> yls177@hotmail.com (yls177) wrote:
>>
>> >hi, i got the below when i enter vgdisplay
>> >
>> >vgdisplay: Volume group not activated.
>> >vgdisplay: Cannot display volume group "/dev/pvg60".
>> >vgdisplay: Volume group not activated.
>> >vgdisplay: Cannot display volume group "/dev/pvg80".
>> >vgdisplay: Volume group not activated.
>> >vgdisplay: Cannot display volume group "/dev/pvg70".
>> >
>> >
>> >what is this all about?
>>
>> As it says, these volume groups are not activated on this node.
>>
>> Are you running a ServuceGuard cluster?
>> If so all packaged volume groups are defined on all nodes in the
>> cluster but only activated on the node currently running the package.
>>
>> Regards.
>>
>> Ted.
>> ================================================== ============
>> | Ted Linnell <edlinnell@acslink.net.au> |
>> | |
>> | Nunawading, Victoria , Australia |
>> ================================================== ============
>
>
>
>yes, u are totally right. my current setup. i have 3 L-class, DEV,
>QAS, PRD. the latter two are on serviceguard with a one package
>concept.
>
>from Ted previous post, all the volume groups in QAS, PRD are in the
>cluster? QAS, PRD has their own volume groups with logical volumes
>and filesystems, and are these in the cluster too?

Each node will have its own vg00. This usually consists of the onboard
disks only and holds the OS and swap space.

There may be other "local" vgs, which will hold stuff exclusive to
that node, depends on how it was set up.

Each application package has its own set of 1 or more vgs which will
be activated on the node running the package. These vgs will be
deactivated when the package is halted. They are only visable on the
node running that package, although defined to all hosts.

Regards,

Ted.


================================================== ============
| Ted Linnell <edlinnell@acslink.net.au> |
| |
| Nunawading, Victoria , Australia |
================================================== ============

Ted Linnell <edlinnell@acslink.net.au> wrote in message news:<s9jcf0peh23thvisvr3dq39gicut4shqqv@4ax.com>. ..
> yls177@hotmail.com (yls177) wrote:
>
> >Ted Linnell <edlinnell@acslink.net.au> wrote in message news:<75j4f0h6k5bikicl4t4132ujnu32d94ts6@4ax.com>. ..
> >> yls177@hotmail.com (yls177) wrote:
> >>
> >> >hi, i got the below when i enter vgdisplay
> >> >
> >> >vgdisplay: Volume group not activated.
> >> >vgdisplay: Cannot display volume group "/dev/pvg60".
> >> >vgdisplay: Volume group not activated.
> >> >vgdisplay: Cannot display volume group "/dev/pvg80".
> >> >vgdisplay: Volume group not activated.
> >> >vgdisplay: Cannot display volume group "/dev/pvg70".
> >> >
> >> >
> >> >what is this all about?
> >>
> >> As it says, these volume groups are not activated on this node.
> >>
> >> Are you running a ServuceGuard cluster?
> >> If so all packaged volume groups are defined on all nodes in the
> >> cluster but only activated on the node currently running the package.
> >>
> >> Regards.
> >>
> >> Ted.
> >> ================================================== ============
> >> | Ted Linnell <edlinnell@acslink.net.au> |
> >> | |
> >> | Nunawading, Victoria , Australia |
> >> ================================================== ============
> >
> >
> >
> >yes, u are totally right. my current setup. i have 3 L-class, DEV,
> >QAS, PRD. the latter two are on serviceguard with a one package
> >concept.
> >
> >from Ted previous post, all the volume groups in QAS, PRD are in the
> >cluster? QAS, PRD has their own volume groups with logical volumes
> >and filesystems, and are these in the cluster too?
>
> Each node will have its own vg00. This usually consists of the onboard
> disks only and holds the OS and swap space.
>
> There may be other "local" vgs, which will hold stuff exclusive to
> that node, depends on how it was set up.
>
> Each application package has its own set of 1 or more vgs which will
> be activated on the node running the package. These vgs will be
> deactivated when the package is halted. They are only visable on the
> node running that package, although defined to all hosts.
>
> Regards,
>
> Ted.
>
>
> ================================================== ============
> | Ted Linnell <edlinnell@acslink.net.au> |
> | |
> | Nunawading, Victoria , Australia |
> ================================================== ============



i have a clearer picture now. the logs below

vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/pvg60".
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/pvg80".
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/pvg70".

are from my QAS which is an adoptive node. okay, my primary node is in
PRD. and yes yes, pvg60, pvg80 and pvg70 are in PRD and can be shown
clearly in vgdisplay. However, in QAS, i have a qpvg50 as well