HP Tru64 UNIX Version 5.1B-2 and Higher Patch Kit Installation Instructions (March 2009)

Note:
File system operations on directories are not bound by this tagged file restraint. For example, an
ls of a directory on any cluster member during a rolling upgrade lists both versions of a file.
However, the output of an ls -ail command on a member that has not rolled is different from
the output on a member that has rolled. In the following examples the ls -ail command is
run first on a member that has not rolled and then on a member that has rolled. (The awk utility
is used to print only the inode, size, month and day timestamp, and name of each file.)
The following output from the ls command is taken from a cluster member running with tags
before it has rolled. The tagged files are the same as their untagged counterparts (same inode,
size, and timestamp). When this member runs the hostname command, it runs the tagged
version (inode 3643).
# cd /sbin
# ls -ail hostname .Old..hostname ls .Old..ls init .Old..init |\
awk '{printf("%d\t%d\t%s %s\t%s\n",$1,$6,$7,$8,$10)}`
3643 16416 Aug 24 .Old..hostname
3648 395600 Aug 24 .Old..init
3756 624320 Aug 24 .Old..ls
3643 16416 Aug 24 hostname
3648 395600 Aug 24 init
3756 624320 Aug 24 ls
The following output from the ls command is taken from a cluster member running without
tags after it has rolled. The tagged files now differ from their untagged counterparts (different
inode, size, and timestamp). When this member runs the hostname command, it runs the
non-tagged version (inode 1370).
# cd /sbin
# ls -ail hostname .Old..hostname ls .Old..ls init .Old..init |\
awk '{printf("%d\t%d\t%s %s\t%s\n",$1,$6,$7,$8,$10)}`
3643 16416 Aug 24 .Old..hostname
3648 395600 Aug 24 .Old..init
3756 624320 Aug 24 .Old..ls
1187 16528 Mar 12 hostname
1370 429280 Mar 12 init
1273 792640 Mar 12 ls
After you create tagged files in the setup stage, we recommend that you run any administrative
command, such as tar, from a member that has rolled. You can always run commands on the
lead member because it never runs on tagged files.
The following rules determine which files have tagged files automatically created for them in
the setup stage:
• Tagged files are created for inventory files for the following product codes: base operating
system (OSF), TruCluster software (TCR), and Worldwide Language Support (IOS). (The
subsets for each product use that product's three-letter product code as a prefix for each
Rolling Upgrade 69