HP Tru64 UNIX Technical Updates for the Version 5.1B and Higher Operating System and Patches (February 2010)

You can now add the cluster members you removed and reinstall the hardware you removed,
as long as the support for it existed in the pre-patched system. You can also reinstall the patch
kit.
Actions You Can Take
The following list describes several actions you can take, followed by detailed steps for performing
those actions:
• The best workaround for this problem is to manually make backup copies of the /etc/
dfsc.dat and /etc/dfsl.dat data files before you install the patch kit, and then manually
restore them before rebooting the earlier version.
• If you do not do that, you may still be able to retrieve the Version 1.0 files if you have not
made too many disk configuration changes since the installation of the patch kit. The dsfmgr
program saves up to eight earlier copies of the files.
• If the Version 1.0 files are gone, you may be able to edit the existing files so they can be read
by Version 1.0 of dsfmgr.
Typically, /etc/dfsc.dat is a clusterwide file, while /etc/dfsl.dat is a per-member Context
Dependent Symbolic Link (CDSL). For example:
# ls -l /etc/dfs?.dat
/etc/dfsc.dat
/etc/dfsl.dat -> ../cluster/members/{memb}/etc/dfsl.dat
The sbin/dsfmgr command makes backup copies that have the same file name but a new file
extension: .h00, .h01, and so on, where .h00 is the latest backup. For example:
/etc/dfsc.h00
/etc/dfsl.h00 -> ../cluster/members/{memb}/etc/dfsl.h00
Backing Up Original Files
To make backup copies of the original Version V1.0 files before installing the kit, you must be
logged in as root. Then proceed as follows:
1. Copy the dfsc.dat file:
# cp /etc/dfsc.dat /etc/dfsc.dat.v10
2. Determine how many members are in the cluster and make backup copies of each member's
dfsl.dat file. (Noncluster systems have only member0.) This procedure requires that the
cluster has booted far enough so that all member directories are visible. The following
example cluster has 3 members, member0, member1 and member2. On a typical cluster,
member0 is the left over stand-alone disk from the original system, so do not be surprised
if it contains out-of-date files.
# cp ls /cluster/members
member member0 member1 member2
# cp /cluster/members/member0/etc/dfsl.dat /cluster/members/member0/etc/dfsl.dat.v10
# cp /cluster/members/member1/etc/dfsl.dat /cluster/members/member1/etc/dfsl.dat.v10
# cp /cluster/members/member2/etc/dfsl.dat /cluster/members/member2/etc/dfsl.dat.v10
Determining Which Files Are Version 1.0
The script /etc/dn_fix_dat.sh is intended to restore Version 1.0 of dfsc.dat and dfsl.dat
on the member on which it is run. Run /etc/dn_fix_dat.sh on each cluster member before
you reboot the member. If /etc/dn_fix_dat.sh is missing or is failing, you will have to
perform the following manual steps.
You will then have to configure your system.
Upgrade Problem with NHD6 (May 2003)
An interaction problem with New Hardware Delivery Kit 6 (NHD6) and Patch Kit 2 may cause
the patch kit to not install correctly if the following conditions exist:
• Your cluster is running Version 5.1A with Patch Kit 4 and NHD6 installed.
• You attempt to perform a rolling upgrade to Version 5.1B, NHD6, and V5.1B Patch Kit 2.
22