|
Patch 3549 : NFS rollup #16 for Irix 6.2 : [IRIX 6.2]
INDEX
RELATIONS
RELEASE NOTES
1. Patch SG0003549 Release Note
This release note describes patch SG0003549 to IRIX 6.2.
1.1 Supported Hardware Platforms
This patch contains bug fixes for all machine types
supported by IRIX 6.2. This patch subsumes patches
SG0001240, SG0001393, SG0001437, SG0001448, SG0001608,
SG001735, SG002042, SG002104, SG002365, SG002654, SG0002956,
SG0003049, SG0003213, SG0003326 and SG0003447.
1.2 Supported Software Platforms
This patch contains bug fixes for IRIX 6.2. The software
cannot be installed on other configurations.
1.3 Bugs Fixed by Patch SG0003549
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 NFS file locking hangs with NetApp server. (Bug
#618406)
o When file locks are held when a file system is
unexported (exportfs -u), the file locks are released,
but the hold on the vnode is not. (Bug #587189)
o Applications which perform NFS writes to files opened
with O_SYNC can cause kernel panics on some machines
with nfs patches 2956, 2957, or 2958 installed. (Bug
#604463)
o Under certain conditions during rename and remove, both
versions of NFS can cause memory to be freed twice.
(Bug #515834)
o Lock grant callback do not fill in the caller name in
the RPC arguments correctly. This causes clients to
not generate reply messages. (Bug #487525)
o Kernel panics when processing a crash notification.
(Bug #535400)
o Kernel panic on IP28 with Beta patch 2104 when
compiling C++ code. (Bug #514007)
o Fixed a panic in rfs3_readdirplus_free. (Bug #544912)
o Eliminated unnecessary getattrs. (Bug #527040).
o Fixed a problem with the lockd process count that was
introduced in a Beta version of an earlier patch. (Bug
#550649)
o NFS panics in ovbcopy during readdir. (Bug #527086)
o NFS panics when handling a statvfs call from ClearCase.
(Bug #530299)
o NFS panics in makenfs3node when passed an attribute
with an invalid type. (Bug #707176)
o The NFS3 server never changes its commit verifier.
This will cause clients to think that a write has been
comitted to stable storage when it may have been lost
instead. (Bug #512165)
o NFS version 2 open-rename processing now works. (Bug
#302721)
o Brings NLM versions 1 and 3 into conformance with the
XNFS specification with respect to the use of
NLM_GRANTED and NLM_GRANTED_MSG. (Bug #469123)
o Fixes a kernel panic on lock requests from PCs. (Bug
#435114)
o Fixes a problem where file attributes are not always
updated properly at file lock boundaries (lock or
unlock). (Bug #394385)
o NFS sequential performance is too low, add Bulk Data
Service. (Bug #383918) See the Bulk Data Service
release notes, and Getting Started with BDSpro for more
details.
o NFS file lock requests can hang. (Bug #378158)
o The NLM server responds improperly to retransmitted
lock requests when the original request was blocked.
(Bug #379574)
o NFS Version 3 client panics when trying to access a
namefs or Atria file system (Bugs #358785 and #360700)
o NFS Version 3 clients issue unnecessary setattr calls.
(Bug #359683)
o NFS Version 3 servers incorrectly export loopback
mounted filesystems. This shows up as a client's
failure to access remote CDROMs and DOS directories.
Patch 1222 is also required for correct handling of
statfs(2). (Bug #360700)
o System panics in chunkread. This is a very rare panic.
(Bug #369374)
o Programs using sproc(2) and accessing NFS or NFS3 files
by both mmap(2) and read(2)/write(2) could cause the
system to deadlock. (Bug #375390)
o SEGV panic in xfs_lookup code (6.2, r10k) (Bug #388410)
o Updates to files on the server are sometimes not seen
by the clients (Bug #392807)
o Fixes bug that was causing extremely slow startup for
vi and slow response from /bin/pwd for filesystems
exported with the nohide option. (Bug #399824)
o Fixes to the Directory Name lookup cache handling in
nfs version 3 speeds up ls -lR and fixes iso9660 cdrom
handling. Note: These fixes affect both nfs client and
nfs server code. If a server has not applied patch
1448, clients that have may see unusual behaviour when
trying to read directories that are mountpoints
exported with the nohide option. (Bug #402692)
o Fixes the problem in nfs version 3 where setuid
programs could not read files readable by the real
user. (Bug #411885)
o NFS version 3 now returns the correct device major
number. (Bug #412281)
o Fixed the problem that was causing processes to hang in
NFS version 3 with patch 1437 (Bug #404410, Bug
#422814)
o Fixes the temporary corruption caused by using Jot on
NFS version 3 filesystems. (Bug #394222)
o NFS version 2 was getting decode errors trying to read
directories from HP and Auspex systems (Bug #432972)
o Fixes the problem with processing hanging in
nfs_purge_caches. (Bug #433429)
o Fixes a panic in nfs_vget. (Bug #430822)
o Corrects a problem where the client receives
RPC_PROGUNAVAIL and returns an error when the server
crashes and comes back up. (Bug #454597)
o Eliminates the fhtovp_end:(VFS_GET failed or vp NULL)
messages (Bug #447729)
o Kernel panic'd when trying to connect to Intergraph NFS
Server using NFS version 3. (Bug #454538)
o Fixes a panic when using nfs version 3 over an Amass
filesystem. (Bug #457145)
o Correct a bug where both versions of NFS return the
incorrect file system ID. (Bug #457662)
o Make the nfs minor maps dynamic to allow more than 256
mounts. (Bug #406888)
o Corrects problem in readdirplus that was causing
tlbmiss panics. (Bug #445408)
o Corrects permission problem with locks caused by
extraneous commit call (Bug #455639)
o Fix NFS version 3 client attribute problem, causing
client to use slightly out of date attributes (Bug
#460403)
o Fixed a few interoperability problems discovered at
Connectathon 97, including guard time mismatch problem,
readdir cookie verifier problem, and a problem with TCP
record sizes (Bug #470179)
o Fix NFS version 3 server panic when client ignores
FSINFO values and sends a read request larger than the
negotiated maximum transfer size. (Bug #463244)
o Fix NFS to not hang up nfsd processes when waiting for
a DMAPI application to reload file to disk. (Bug #
467350)
o NFS version 3 mknod was creating special files with the
wrong major/minor numbers. (Bug # 468061)
o System panics in free routines called from
rfs_dispatch. (Bug # 476784)
o NFS version 3 sometimes returns the wrong data to
CacheFS. (Bug # 418493)
o Fix some cookie error NFS3 readdir path that caused
problems with some xfs directories.(Bug #467586)
o Change the way nfs version 2 clients set up a READDIR2
call so that it is compatible with NeXtStep and other
legacy NFS implementations. (Bug #470452)
o Fix error introduced in Patch 1735 that caused panics
when ClearCase file system is mounted. (Bug #480231)
o Fixes for V_SOCK support in nfs version 3 (Bug
#481998). This bug was actually fixed in patch 1608,
but not mentioned in the release notes.
o NLM Cancel request were not honored properly. (Bug
#474898)
o APP: NFS file locking failed in mixed OS networks - and
with NFS3 (Bug #489374)
o In NFS, writes to locked regions of a file could
overwrite unlocked regions (Bug #495969)
o Grace period lock denials were placed into the NLM dup
cache (Bug #497094)
o NFS version 3 was doing way too many ACCESS calls.
(Bug #492432)
o NFS version 2 was not sending required DMAPI read
events. (Bug #499569)
o NFS file locking hangs. (Bug #495987)
o Kernel memory leak on the NFS server when file locking
is used. (Bug #496671)
o Kernel panic when reclaiming file locks. (Bug #508579)
o Kernels were panic'ing during reboot after a FailSafe
takeover or while moving failover resources back and
forth between the two nodes in a cluster. (Bug
#428159)
o Any stat of a named pipe in an nfs version 2 or 3
filesystem would result in the following error: "Can't
stat vfs: Stale NFS file handle" (Bug #504703)
o NFS version 3 was ignoring the Set Group ID bit on
directories. (Bug #519739)
o NFS version 3 writes NULLs to files that are locked and
memory mapped. (Bug #505673)
o NFS version 3 clients did not properly update it's file
attributes when the file changed on the server. (Bug
#475062)
o The NFS server does not appropriately reply to illegal
rename requests that span different filesystems. (Bug
#526773)
o NFS version 3 clients may corrupt files grown in mapped
regions as seen with some compilers and linkers. (Bug
#517969)
o NFS version 3 clients may briefly operate with stale
attributes. (Bug #538784)
o NFS version 3 client systems may hang or panic while
compiling C++. (Bug #514007)
o Creating a file with exclusive access over NFS version
3 can fail to set the proper access permissions. (Bug
#532520)
o NFS version 3 clients send writes of O_SYNC files in an
unsafe way (UNSTABLE without commits instead of
FILE_SYNC). (Bug #548408)
o NFS version 3 clients returned incorrect disk usage
information in the 'used' field in the attribute
structure, which caused non-Irix clients to display
incorrect ls -s information. (Bug #430985, #520045)
o NFS version 3 clients write NULLs into files that have
recently grown on the server. (Bug #550690)
o NFSv3 writes greater than 8K have extra UDP garbage at
end of datagram. (Bug #564379)
o BDS client do appending writes gets data corruption.
(Bug #565785)
o Fix for 561653, NFS over TCP client can hang on a
server which shuts down half a connection (Solaris).
o Fix for bug #346054 NFS V2 can prevent authorized users
from accessing files if root, typically, opened it
first.
o Fix for Bug #567461, NFS V2 writes are serialized.
o Fix for 508894. Don't read a zero length buffer, or a
buffer you're just about to write all over.
o Fix for 527040/546326, NFS V3 writes are serialized.
o Fix for 552271, NFS commits don't always work.
o NFS deadlock. (Bug #571065)
o When using NFSV2 over TCP, a crashed server can crash
the client. (Bug #559749)
o Apps were hanging, due to NFS' failure to release a
buffer in the case of EFAULT during a write. (Bug
#499079)
o For FSYNC write data, only write out the requested
data, not the entire buffer cache block. (Bug
#576605)
o Autoconfig fails with unresolved symbol errors. (Bug
#580304)
o Fix for 579542, stopped NFS/TCP hangs client.
o For an exported NFS loopback filesystem, use the fsid
of the NFS filesystem in the export list structure, so
we can maintain the export after media are ejected.
(Bug #567372)
o Extra call to SMAP_RELE by server (NFS/TCP) upon error
replying to client allows socket to be closed
prematurely, leading to a panic. (Bug #587590)
o System panic while running "pwd" on an NFS mounted
directory (Bug #545940)
o Fix for bug 586988, which was causing unnecessary write
error messages.
o BDS read never completes -- infinite loop. (Bug
#591309)
o Third party server response to READDIRPLUS caused
incomplete 'ls' over NFSv3. (Bug #586244)
o Files written with NFSv3 are sometimes truncated. (Bug
#593276)
o NFS responses get dropped when running ipfilterd. (Bug
#580372)
o NFS panics when using NULL r_cred. Seen on systems that
export filesystems controlled by their own local NFS
server application. (Bug #586988)
o Fix an NFSv3 SETATTR "out of sync" problem. (Bug
#590099)
o autofsd error messages in SYSLOG (Bug #585924)
o Limit server's max transfer size to be 8K. (Bug
#616890)
o Exclusive create call on sgid set directory fails for
some users (Bug #623617)
o Fix a problem with NFSv2 failing to check for EINTR
during bio. (Bug #631209)
o Zone corruption panics due to bad crfree() calls in
do_bio(). (Bug #627091)
o NFS client generating "RMDIR2 ." hangs IRIX. (Bug
#637450)
o umount /unmount gets resource busy on STALE nfs mounts.
(Bug #633347)
o NFS3 directory not showing all entries (Bug #643199)
o NFS corruption with SGI NFS2-mounting AIX 4.3 (Bug
#637060)
o Cachefs issues too many getattr calls. (Bug #644919)
o NFSv2 symlinks can cause a panic. (Bug #633038)
o Corruption in pregion avl tree. (Bug #630464)
o kernel fault due to corrupt avl tree when detaching
region (Bug #631359)
o stack overflow panic in 6.5.1m due to recursion in
spec_getattr (Bug #638603)
o tlbmiss in xfs_ail_delete() (Bug #588160)
o App CATIA: lock on read on a read only fs broken since
patch 2656 (Bug #658012)
o Rewind test fails with NFSv2 client (Bug #659189)
o race between nfs_lookup and reclaim_locks (Bug
#605226)
o not getting the right handle for an NFS3 mountpoint
(Bug #662884)
1.4 Subsystems Included in Patch SG0003549
This patch release includes these subsystems:
o patchSG0003549.eoe_sw.unix
o patchSG0003549.nfs3_sw.nfs3
o patchSG0003549.nfs_sw.nfs
1.5 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.
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. Select the desired patches for installation.
3. Initiate the installation sequence. Type
Inst> go
4. You may find that two patches have been marked as
incompatible. If this occurs, you must deselect one
of the patches.
Inst> keep patchSGxxxxxxx
where xxxxxxx is the patch number.
5. After completing the installation process, exit the
inst program by typing
Inst> quit
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.
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): 16438 1862 patchSG0003549.nfs_sw 30355 1240 patchSG0003549.nfs3_sw 56199 33 patch/README.patch.3549 36930 379 patchSG0003549.onc3_eoe_sw 28407 14 patchSG0003549 08490 22 patchSG0003549.idb 10202 2989 patchSG0003549.eoe_sw INST SUBSYSTEM FILE LISTINGS The following lists the files which get installed from each subsystem in the patch:
DOWNLOAD PATCH
|
||||||||||||||||||||||||||||||||||||
Document Id: 20021117074257-IRIXPatch-1351
|
||||||||||||||||||||||||||||||||||||