Do we use vmvx

[Darrell Tschakert]

Hi,
We have some rx4640's running 11.23 with A.11.16.00 Servicgaurd. I want to load the latested Quality Pack this weekend. This bundle contains patch PHSS_35303 which patches Servicguard. The documentation claimes that loading this patch can cause problems with packages using VxVm disk Groups. We use LVM, but I don't know if we use VxVm disk groups in any way. How would I determine whether or not we use VxVm disk groups? Running:
"print_manifest | grep -i vxvm"
gives me no output.
Running:
"swlist -l fileset | grep -i vxvm"
gives me lots of output.

Is there a sure fire way to determine if we use VxVm disk groups?

Thanks,

Darrell Tschakert

[Jason Ray]

Darrell,

You can check to see if you have VXFS and VXVM installed with:

swlist | grep -i veri
Which would give you something like this if its installed:
Base-VXFS 4.1.002 VERITAS File System Bundle 4.1 for HP-UX
Base-VXVM B.04.10.011 Base VERITAS Volume Manager Bundle 4.1 for HP-UX

Also, do an 'ls' in /dev/vx/dsk which would show you any veritas disk groups currently imported on your system.

[Steven E. Protter]

Shalom Darrell,

I seriously doubt on this sytem you could use a vxvm disk group because there is no vxvm software.

You have pretty much made sure its impossible for this bug to effect you.

Still, do an ignite make_tape_recovery or make_net_recovery of vg00 before the patch, because lots of things could go wrong.

You are however perfectly safe from this particular bug.

Just to be extra sure:
swlist -l product | grep -i vxvm

BTW, vxvm is installed be default, so some effort must have been made to remove it.

SEP

[A. Clay Stephenson]

Try running vxprint; it will fail instantly if LVM is not configured.

[A. Clay Stephenson]

Try running vxprint; it will fail instantly if VxVM is not configured.

[Darrell Tschakert]

I tried to give out points, but it takes forever and nothing happens.

Jason,
If I run your command, I get one of the entries that you listed. Not both. "ls -l /dev/vx" does not give me "disk" but it gives me lots of other devices.
---------------------------------

Steven, I always make recovery tapes before loading patches. I get the following with swlist ...

Base-VXVM B.03.50.IA.014 Base VERITAS Volume Manager Bundle 3.5 for HP-UX But I don't get the other line
---------------------------------

A. Clay, vxprint fails, but I don't know if that is because a certain service is turned off or what. I get the following output:
vxvm:vxprint: ERROR: IPC failure: Configuration daemon is not accessible
-----------------------------

I have to say, I'm still not certain, one way or the other, if we have VxVm. Not certain enough to load the bundle. I will call HP support tomorrow.
Thanks,

Darrell T.

[Robert-Jan Goossens_1 · Accepted solution]

Hi Darrel,

Yes you have vxvm (base version) installed, but you are not using it. The vxvm error you are seeing id because vxvm was never configured.

# bdf
and
# cat /etc/fstab
will probably display /dev/vgxx/lvoly for the devices. If where using vxvm it would display /dev/vx/dsk/rootdg/xxxvol.

PHSS_35303 is not a problem just because vxvm is installed.

Hope this helps,
Robert-Jan

[A. Clay Stephenson]

VxVM is installed on almost every 11i system; it's just not running on many of them. The error you get from vxprint is just what I was expecting; you have no vx daemons running so. If you do a ps -ef | grep "vx" the only thing I would expect to see running ix vxsvc. However, if you are on a system where VxVM is active then ps -ef | grep "vx" will display several processes.

[Ralph Grothe]

Hi Darrell,

VxVM comes with almost every B.11.11 installation.
However, if you never have configured it,
none of its vital daemons will be started.
Just have a look into the vxvm-startup init script where you will find this early bail out if VxVM is unconfigured on your box:

52 #
53 # If the volume manager hasn't yet been initialized, don't
54 # bother starting vxconfigd. The install-db file indicates tha
54 t
55 # initialization has NOT yet happened.
56 #
57
58 if [ -f "/etc/vx/reconfig.d/state.d/install-db" ]
59 then
60 exit 0
61
62 fi


So if you can find the file
/etc/vx/reconfig.d/state.d/install-db
then you most likely aren't using VxVM.

You may also check for the vital VxVM daemons separately if you still aren't convinced.

e.g.

# vxdctl mode
mode: not-running

# vxiod
0 volume I/O daemons running

# UNIX95= ps -C vxconfigd
PID TTY TIME CMD

# vxconfigd -f
vxvm:vxconfigd: ERROR: enable failed: Volboot file not loaded
transactions are disabled.
^C

[Darrell Tschakert]

We don't have VXVM configured and running. If it were configured and running, we would not have this file:

/etc/vx/reconfig.d/state.d/install-db

vxiod and vxdctl both say VxVm is not running.

Thanks to everyone for the help.

Darrell Tschakert