VERITAS Volume Manager 3.5 Release Notes (August 2002)

Chapter 1

VERITAS Volume Manager™ Release Notes

Patches and Fixes in This Version

• Problem: If you are installing from an Ignite_UX server, you will not see the question and it will appear

that the machine is hung.

The question should appear after the following message on the console:

* Bringing up Network (lan0)

* NFS mounting clients directory.

The question that is being asked is:

This appears to be a VxVM boot disk device.

Overwriting it will destroy the current LIF directory

Should the current LIF directory be destroyed [y/n]?

• Type “n” after the console message, if you suspect that the system is waiting for an answer.

NOTE This is ﬁxed in AR0902. The problem does not arise if you install AR0902 on different disk

on a machine that already has a vxvm root disk.

Cautionary Note when using HP-UX Maintenance Mode Boot (MMB)

HPUX Maintenance Mode Boot (MMB) is meant to used in the recovery from catastrophic failures that have

prevented the target machine from booting. If a mirrored root is conﬁgured, then when booting in MMB mode,

only one mirror is activated. Therefore, any writes to the root ﬁlesystem in this mode could cause root

ﬁlesystem corruption later when both mirrors are conﬁgured.

The vx_emerg_start script is provided to be used when starting the Volume Manager in MMB mode. This

script will avoid writing to the root ﬁlesystem, unless absolutely necessary. If it needs to update the volboot

ﬁle, then it will request that you reinvoke t the vx_emerg_start script, using the -f option, to perform the

write.

It is recommended that after the vx_emerg_start script has been run to start the Volume Manager while in

MMB mode on a mirrored root, that the half of the mirror not booted from is removed. This can be carried out

as follows:

• Determine which disk you booted from.

• Use the vxdisk list command to ﬁnd your boot disk in the DEVICE column on the far left.

• Find the Disk Media (DM) name of your boot device by looking up your boot device in the DISK column.

This will be a name such as rootdisk01, rootdisk02, and so on. Also note the name of the mirror disk DM.

• Use the vxprint -g rootdg rootvol command. If you have a mirrored root volume, you will see two lines

with "pl" on the far left side. Look at each pl (or "plex") entry and immediately below it will be the subdisk

associated with the plex. It will start with an "sd" in the far left column.

• Look at the NAME ﬁeld immediately to the right of the "sd" column. This will show the subdisk name,

which is made up of the DM name followed by -nn, where nn is a number such as 03, 04, and so on. This

should allow you to identify the DM name of the disk that is not your boot disk. You can remove the plex

and its associated subdisk by executing the vxplex command as follows:

vxplex -o rm dis plex name

For example, to remove the rootvol plex associated with rootdisk02:

vxprint -g rootdg rootvol

TY NAME ASSOC KSTATE LENGTH PLOFFS STATE