CDFSDATE_V50A Tru64 V5.0A CDFS File System ECO Summary
TITLE: CDFSDATE_V50A Tru64 V5.0A CDFS File System ECO Summary
PROBLEM STATEMENT:
A problem may be encountered with reading the creation date of a file
after the file is accessed from a CD-ROM using the cdfs file system. The
date may be incorrectly read from the CD-ROM. As a result of this incorrect
reading, a date such as 31-DEC-1969 may be displayed.
** NOTE: ** The stored creation date on the CD-ROM IS CORRECT. The
potential problem can only occur when the file is copied
or accessed from the CD-ROM.SOLUTION:
There is a new, release-specific, version of /sys/BINARY/cdfs.mod which
addresses this potential problem. This patch will need to be installed on
all systems running Tru64 UNIX versions 4.0D, 4.0F, 4.0G, 5.0, 5.0A, and
5.1 and on cluster configurations.
The README contained within the tar file provides details on how to install
the patch.
The corrected version of the /sys/BINARY/cdfs.mod is built to be installed
on specific versions of the operating system. The table below provides the
patch kit name, and location for each Tru64 UNIX version:
V4.0D Kit: cdfsdate_v40d.tar
Location: http://ftp1.support.compaq.com/public/unix/v4.0d/
V4.0F Kit: cdfsdate_V40f.tar
Location: http://ftp1.support.compaq.com/public/unix/v4.0f/
V4.0G Kit: cdfsdate_v40g.tar
Location: http://ftp1.support.compaq.com/public/unix/v4.0g/
V5.0 Kit: cdfsdate_v50.tar
Location: http://ftp1.support.compaq.com/public/unix/v5.0/
V5.0A Kit: cdfsdate_v50a.tar
Location: http://ftp1.support.compaq.com/public/unix/v5.0a/
V5.1 Kit: cdfsdate_v51.tar
Location: http://ftp1.support.compaq.com/public/unix/v5.1/
This README contains instructions for loading this patch, for determining
if a kernel rebuild and system reboot are required, and for configuring
this patch. The patch should be applied from the root process. The
patched cdfs.mod is delivered in the patch tar file as
/sys/BINARY/cdfs.mod.patch. The steps for loading and configuring the
patch will differ depending on whether a kernel rebuild and reboot is
required, and whether the patch is being applied to a TruCluster system.
For V4.0* based cluster systems this patch must be individually
loaded and configured on each cluster member. For V5.* based
TruCluster systems, this patch can be loaded once, but it also
must be configured on each cluster member.
Loading the patch:
Load this patch by moving the patched cdfs.mod to its proper
location and by rebuilding /genvmunix. Use the following commands.
# cp /sys/BINARY/cdfs.mod /sys/BINARY/cdfs.mod.pre_patch
# mv /sys/BINARY/cdfs.mod.patch /sys/BINARY/cdfs.mod
# chown bin.bin /sys/BINARY/cdfs.mod
# chmod 644 /sys/BINARY/cdfs.mod
Rebuild /genvmunix.
# doconfig -a -c GENERIC
# cp /sys/GENERIC/vmunix /genvmunix
Note, time can be saved on cluster systems by performing the
/genvmunix rebuild once and copying the resulting /genvmunix to
each cluster member.
The loading portion of this patch is now complete.
This patch can be applied to a running system and the corrected behavior
will take effect immediately. However depending on how the /vmunix
kernel is configured, it may be necessary to rebuild a new /vmunix
kernel and to reboot the system to have the patch be permanent.
Determining if a kernel rebuild is required:
To determine if a kernel rebuild is required, perform the following
command.
# nm /vmunix | grep -c cdfs_tounixdate
If the output is a '0', then a /vmunix kernel rebuild and system
reboot is not required. Proceed to OPTION 2.
If the output is a '1', then a /vmunix kernel rebuild and
system reboot will be required to make the patch permanent.
Proceed to OPTION 3.
For the most direct method of installing this patch, proceed to
OPTION 1.
OPTION 1: The most direct method to install this patch.
The most direct method for installing this patch is to rebuild
/vmunix and reboot. Here are the steps:
Rebuild /vmunix. Use doconfig with the -c option and specify
the existing config file name. The config file name is usually
the name of the system, in uppercase letters.
# doconfig -c
When the doconfig command completes, it will list a vmunix
file that must be copied to /vmunix.
Reboot the system.
The patch is now permanently installed.
OPTION 2: Installing this patch when a kernel rebuild and reboot is
not required.
This option shows how to install the patch on a system where a
kernel rebuild and reboot is not required for the patch to be
permanently applied.
Prepare to load the patch:
Loading the patch first requires that all cdfs file systems
are unmounted and the cdfs kernel option is unconfigured.
First unmount all cdfs file systems.
# umount -Av -t cdfs
Verify all cdfs file systems have been unmounted. The output
of the following mount command should not show any file
systems still mounted.
# mount -e -t cdfs
Second, unconfigure the cdfs kernel subsystem, making sure
it was first configured.
# sysconfig -c cdfs >> /tmp/cdfs_patch.out
# sysconfig -u cdfs >> /tmp/cdfs_patch.out
Configure the patch with the following command:
# sysconfig -c cdfs
The patch is now installed on the running kernel.
OPTION 3: Installing the patch on a system where a kernel rebuild
and reboot are required.
This option shows how to install the patch on a system where a
kernel rebuild and reboot is required for the patch to be
permanently applied.
If the system can be rebooted immediately, then proceed to
OPTION 1.
If the system cannot be rebooted immediately but the corrected
behavior from the patch is needed and a planned reboot will occur
at a later time, then:
Perform OPTION 2 to have the patch applied to the running system.
At the time of the next reboot, run doconfig to generate
a new /vmunix kernel and reboot the system. Use doconfi
with the -c option and specify the existing config file name.
The config file name is usually the name of the system, in
uppercase letters.
# doconfig -c
The patch is permanently installed once the new kernel is copied
to /vmunix and the system is rebooted.
** Note **:
Do not copy the new rebuilt kernel to /vmunix until the system is
ready to be rebooted.
This patch can be found at any of these sites:
Colorado Site
Georgia Site
Files on this server are as follows:
cdfsdate_v50a.README
cdfsdate_v50a.CHKSUM
cdfsdate_v50a.tar
cdfsdate_v50a.pdf
|