|
Patch 3477 : Status monitor and lockd rollup #3 for IRIX 6.2 : [IRIX 6.2]
INDEX
RELATIONS
RELEASE NOTES
1. Patch SG0003477 Release Note
This release note describes patch SG0003477 to IRIX 6.2.
1.1 Supported Hardware Platforms
Patch 3477 contains bug fixes for all IRIX 6.2 supported
hardware platforms.
1.2 Supported Software Platforms
This patch contains bug fixes for NFS and Failsafe-NFS on a
system running IRIX 6.2. The software cannot be installed
on other configurations.
This patch replaces patch SG0003058.
In order for fixes in patch SG0003477 to work correctly,
patch SG0001608 or higher from the NFS patch set must also
be installed. Without this, the user commands will fail
because kernel modifications required for patch SG0003477
are contained in patch SG0001608 and its successors.
Patch SG0003477 replaces patches SG0001745, SG0001679,
SG0001621, SG0001276 and SG0002278 and SG0003058 and
contains only the user commands from SG0001621. Patch
SG0001679 had incorrect relationships defined. Patch
SG0003477 is incompatible with patch SG0001448 and previous
NFS rollup patch sets because they did not have the proper
NFS kernel modifications necessary for patch SG0003477.
Should problems arise, delete the latest NFS rollup patch
set and Status monitor/Failsafe locking patch set.
Afterward, re-install SG0003477 and SG0001608 (or
successor).
1.3 Bugs Fixed by Patch SG0003477
This patch contains fixes for the following bugs in IRIX
6.2. Bug numbers from Silicon Graphics bug tracking system
are included for reference.
o Bug 577215 - ha_statd -a fails causing failsafe to
shutdown. ha_statd timed out, due to rpc.statd was busy
processing nfs system locks.
1.4 Bugs Fixed by Previous rollup patches
The following IRIS bugs were fixed by previous rollup
patches. Bug numbers from Silicon Graphics bug tracking
system are included for reference.
o Change the severity of a syslog message to INFO. (Bug
#512457)
o On FailSafe systems, rpc.statd can cause ha_statd to
timeout, causing failsafe to shutdown. (Bug #577215)
o On FailSafe systems, it is possible for rpc.statd to
attempt to send a crash notification to itself. This
results in some non-terminating loop behaviour in
rpc.statd where the crash notification is sent to
itself every 10 seconds. (Bug #588290)
o File locking can hang when the server is rebooted.
(Bug #495987)
o Non-SGI clients using NFS over TCP can hang when
attempting to acquire file locks. (Bug #499530)
o rpc.statd and rpc.lockd have been updated to support
highly available environments. Specifically, these
changes are necessary for the IRIS FailSafe product.
(BUG 370459)
1.5 Subsystems Included in Patch SG0003477
This patch release includes these subsystems:
o patchSG0003477.nfs_man.nfs
o patchSG0003477.nfs_sw.nfs
1.6 Installation Instructions
Because you want to install only the patches for problems
you have encountered, patch software is not installed by
default. After reading the descriptions of the bugs fixed
in this patch (see Section 1.3), determine the patches that
meet your specific needs.
If, after reading Sections 1.1 and 1.2 of these release
notes, you are unsure whether your hardware and software
meet the requirements for installing a particular patch, run
inst. The inst program does not allow you to install
patches that are incompatible with your hardware or
software.
Patch software is installed like any other Silicon Graphics
software product. Follow the instructions in your Software
Installation Administrator's Guide to bring up the miniroot
form of the software installation tools.
Follow these steps to select a patch for installation:
1. At the Inst> prompt, type
install patchSGxxxxxxx
where xxxxxxx is the patch number.
2. Initiate the installation sequence. Type
Inst> go
3. You may find that two patches have been marked as
incompatible. (The installation tools reject an
installation request if an incompatibility is
detected.) If this occurs, you must deselect one of
the patches.
Inst> keep patchSGxxxxxxx
where xxxxxxx is the patch number.
4. After completing the installation process, exit the
inst program by typing
Inst> quit
1.7 Patch Removal Instructions
To remove a patch, use the versions remove command as you
would for any other software subsystem. The removal process
reinstates the original version of software unless you have
specifically removed the patch history from your system.
versions remove patchSGxxxxxxx
where xxxxxxx is the patch number.
To keep a patch but increase your disk space, use the
versions removehist command to remove the patch history.
versions removehist patchSGxxxxxxx
where xxxxxxx is the patch number.
1.8 Known Problems INST SUBSYSTEM REQUIREMENTS No Requirements Information Available. INST SUBSYSTEM CHECKSUMS These checksums help to provide a 'signature' for the patch inst image which can be used to authenticate other inst images. You can obtain this kind of output by running sum -r on the image (from the command line): 57266 12 patch/README.patch.3477 61977 3 patchSG0003477 00278 46 patchSG0003477.nfs_sw 07835 3 patchSG0003477.nfs_man INST SUBSYSTEM FILE LISTINGS The following lists the files which get installed from each subsystem in the patch:
DOWNLOAD PATCH
|
||||||||||||||||||||||||||||||||||||
Document Id: 20021117073742-IRIXPatch-1329
|
||||||||||||||||||||||||||||||||||||