Patch Name: PHNE_24143 Patch Description: s700_800 10.20 NFS/NIS General Release/Performance Patch Creation Date: 01/06/05 Post Date: 01/07/18 Hardware Platforms - OS Releases: s700: 10.20 s800: 10.20 Products: N/A Filesets: OS-Core.CORE-KRN OS-Core.CORE-ENG-A-MAN OS-Core.UX-CORE NFS.NFS-CORE NFS.NFS-SERVER NFS.NFS-CLIENT NFS.NIS-CLIENT NFS.NIS-SERVER NFS.NFS-ENG-A-MAN Automatic Reboot?: Yes Status: General Superseded Critical: Yes PHNE_24143: CORRUPTION Due to a race condition in AutoFS nodes could become corrupted. Corrupted nodes could eventually result in empty AutoFS directories. PHNE_22877: PANIC HANG Panic due to race condition between mount and umount with ufs filesytems. Hang encountered because of rfs_readdirplus3() memory leak in NFS PV3. PHNE_20021: PANIC panic in internal test - cachefs with autofs. PHNE_16924: PANIC CORRUPTION Panic due to buffer cache corruption PHNE_16925: PANIC CORRUPTION Panic due to buffer cache corruption PHNE_15863: PANIC HANG CORRUPTION Hang encountered in nfs_fsync() Panic with m_free(), sbdrop(), and clntkudp_callit() Panic with truncated file Panic with nfs_purge_caches(), binvalfree(), bwrite(), nfs_strategy(), do_bio(), and nfswrite() recursion Hang encountered with autofs (this applies only to systems that have the ACE 2 software bundle installed) Hang encountered because of rfs_readdirplus3() memory leak (this applies only to systems that have the ACE 2 software bundle installed) Hang encountered with cachefs (this applies only to systems that have the ACE 2 software bundle installed) Panic with rfs3_readlink_free() (this applies only to systems that have the ACE 2 software bundle installed) Corruption encountered with reads (this applies only to systems that have the ACE 2 software bundle installed) PHNE_15864: PANIC HANG CORRUPTION Hang encountered in nfs_fsync() Panic with m_free(), sbdrop(), and clntkudp_callit() Panic with truncated file Panic with nfs_purge_caches(), binvalfree(), bwrite(), nfs_strategy(), do_bio(), and nfswrite() recursion Hang encountered with autofs (this applies only to systems that have the ACE 2 software bundle installed) Hang encountered because of rfs_readdirplus3() memory leak (this applies only to systems that have the ACE 2 software bundle installed) Hang encountered with cachefs (this applies only to systems that have the ACE 2 software bundle installed) Panic with rfs3_readlink_free() (this applies only to systems that have the ACE 2 software bundle installed) Corruption encountered with reads (this applies only to systems that have the ACE 2 software bundle installed) PHNE_15041: PANIC Panic encountered with autofs (this applies only to systems that have the ACE 2 software bundle installed) PHNE_15042: PANIC Panic encountered with autofs (this applies only to systems that have the ACE 2 software bundle installed) PHNE_14071: PANIC HANG Panic encountered in ku_sendto_mbuf() Panic encountered in ckuwakeup() Panic encountered in vn_rele() Hang encountered in nfs_fsync() PHNE_14072: PANIC HANG Panic encountered in ku_sendto_mbuf() Panic encountered in ckuwakeup() Panic encountered in vn_rele() Hang encountered in nfs_fsync() PHNE_13823: HANG PANIC Hang encountered in nfs_fsync() Panic encountered in clnt_kudpinit() PHNE_13824: HANG PANIC Hang encountered in nfs_fsync() Panic encountered in clnt_kudpinit() PHNE_13668: HANG Hang encountered in Instant Ignition PHNE_13669: HANG Hang encountered in instant ignition PHNE_13235: PANIC CORRUPTION Panic encountered in nfs_prealloc() Corruption encountered with retransmissions PHNE_13236: PANIC CORRUPTION Panic encountered in nfs_prealloc() Corruption encountered with retransmissions PHNE_12427: HANG Hang encountered with exportfs command PHNE_12428: HANG Hang encountered with exportfs command PHNE_11386: HANG Hang encountered in NFS IO PHNE_11387: HANG Hang encountered in NFS IO PHNE_11008: CORRUPTION PANIC Overwritten rnode error in do_bio() Rename of jfs file system from PCNFS causes panic Data page fault in ckuwakeup() PHNE_11009: CORRUPTION PANIC Overwritten rnode error in do_bio() Rename of jfs file system from PCNFS causes panic Data page fault in ckuwakeup() PHKL_8544: HANG PHKL_8545: HANG Path Name: /hp-ux_patches/s700_800/10.X/PHNE_24143 Symptoms: PHNE_24143: automountd SR:8606180865 DTS:JAGad50086 Quota does not get enforced when mounting an NFS directory with the automountd quota option. automountd SR:8606197432 DTS:JAGad66625 AutoFS mounts local filesystem(s) as a loopback filesystem type=nfs instead of LOFS (type=lofs) when a hostname other than that returned by hostname() is used. libnfs.a SR:8606176017 DTS:JAGad45257 AutoFS directories are empty under heavy NFS load. libnfs.a SR:8606193515 DTS:JAGad62727 Duplicate entries for direct AutoFS mounts appear in the /etc/mnttab file. rpc.mountd SR:8606167148 DTS:JAGad36434 First mount request fails from linux diskless client the first time. PHNE_22877: libnfs.a SR:8606138879 DTS:JAGad08145 The NFS client was extremely slow during the back-up so that the ATM time daemon did not get run and causes the ATM switch reset. libnfs.a SR:1653275800 DTS:JAGaa24099 System hang caused by memory leak. libnfs.a SR:8606135856 DTS:JAGad04988 Panic occurs when trying to umount a ufs filesystem which is still in the process of mounting. libnfs.a SR:8606159736 DTS:JAGad29062 Unexpected delay in unmounting of Autofs mounts. libnfs.a SR:8606144704 DTS:JAGad14044 NFSv3 does not remove the hardlink of a file if the file is busy. PHNE_22893: {Site Specific Patch} PHNE_22288: automount, automountd SR: 8606128188 DTS: JAGac78988 Inconsistent choice of 'best server' from a list of replicated servers. SR: 8606132942 DTS: JAGad02090 Mounting AutoFS managed file system leads to a hang in a replicated host configuration. automountd SR: 8606104308 DTS: JAGab71724 AutoFS mounts fail when map includes a cachefs entry in a replicated host environment. SR: 8606152534 DTS: JAGad21864 AutoFS occasionally mishandles unmounts when server is down. This may appear as bdf command anomalies. mount SR: 8606124644 DTS: JAGac40027 Any attempt to mount from Plug&stor device fails. rpc.lockd SR: 8606131496 DTS: JAGad00646 Unexpected failover of ServiceGuard NFS package caused by lockd termination. SR: 8606145476 DTS: JAGad14812 Remote locking of a file occasionally leads to a system hang. rpc.mountd, rpc.rexd, rpc.rquotad, rpc.rusersd, rpc.rstatd, rpc.sprayd, rpc.statd, rpc.rwalld, rpc.yppasswdd, ypbind, ypserv SR: 1653270413 DTS: JAGab17308 NFS debug gives 'year' in unusual format. rpc.mountd SR: 8606134248 DTS: JAGad03388 Unable to mount/unmount because mountd unexpectedly terminates. rpc.statd SR: 8606131366 DTS: JAGad00517 Unexpected core dump caused by high memory utilization (when available memory runs low). rpc.statd SR: 8606136063 DTS: JAGad05198 Core dump caused by repeated requests for file lock, rpc.statd aborts. ypserv SR: 8606134296 DTS: JAGad03431 NIS unavailable while calling ypcat, using the TCP transport mode. SR: 8606142896 DTS: JAGad12245 NIS unavailable when system limit for file table is reached. PHNE_22892: {Site Specific Patch} PHNE_22117: libnfs.a SR:8606140818 DTS:JAGad10180 Nulls appearing at end of 10.20 NFS V2 client files w/ PHNE_21108 patch. PHNE_21704: 1. File System may eventually get full due to several debug messages in dmesg and syslog when Cachefs is used after installing PHNE_21108, PHNE_20957 or PHNE_20313. The debug messages are like: vmunix: cachefs_getattr: backvp: vmunix: cachefs_getattr: vap->va_nodeid: JAGad08894 SR:8606139585 PHNE_21375: automountd SR: 8606139829 DTS: JAGad09141 Filesystem unmounts by autofs do not occur within expected timeframe causing false reports of mountpoints not being found in automount.log and a large number of "server xxx not responding" messages seen in syslog.log. PHNE_21108: 1. AutoFS incorrectly handles certain indirect hierarchical maps 2. Improved read-ahead algorithm to enhance READ performance. 3. Data corruption occurs in the form of embedded NULL characters in files written to simultaneously by more than one process. 4. nfsstat(1M) output does not accurately report retransmissions. 5. ls -s reports incorrect number of blocks for files on NFS PV3 server. 6. The link(1M) command does not return an error on NFS PV3 mounted directory when trying to create a new linked file and an existing linked file is already present. 7. A system panic occurs when a process writes to a file and then immediately tries to perform another file operation, such as truncating the file. PHNE_20957: 1. Glance tool fails to start after installing PHNE_20313. PHNE_20628: 1. cachefs does not use more than about 10% of dedicated file system. 2. ypmake and Makefile failed on some mail.aliases file and mail.aliases map is corrupted. 3. File locks hang when NFS server uses fully-qualified hostname. 4. Application hangs on client when obtaining NFS lock on server. 5. rpc.statd 10.20 Makefile references old rpc.lockd directory and this would make rpc.statd behave incorrectly. 6. Modified Mount NFS manpage to mention 32k read/write block size support. 7. automount experiencing hang. 8. autofs hangs when unmounting from down server. 9. /etc/rmtab is growing and causes FS to fill up. 10. rpc.mountd logging of year is in atypical format. 11. rpc.pcnfsd denies valid print requests when file name contains "~" character. PHNE_20626: 1. Incorrect behavior by AutoFS in processing executable maps. 2. Replicated automounts fail if maxfiles > 2048. 3. Showmount -a shows disconnected entry of AutoFS. PHNE_20313: 1. Automounter hangs when trying to mount cachefs filesystem. 2. The timeo option in the mount command does not have any effect when set. 3. Untar-ing a large quantity of files over NFS can be slow. 4. NFS version 3 client is very slow when performing a write operation to a Celerra server. 5. 'maxcnodes' is a constant but should be made a configurable variable to improve cachefs performance. 6. fuser does not work over Cachefs mountpoint. 7. diff(1) failed on AIX client with HP 10.20 server due to name of a regular file passed to pathconf(2) call. 8. MP_SPINLOCK was not taken in nfs3_do_bio()which could have caused a credential related panic. 9. NFS3ERR_TOOSMALL reported as a last packet when it should not be. SUNs solstice PC-NFS-client and DEC-clients cannot handle this error message and fail while accessing the directory. 10. mount command fails with kernel data page fault panic instead of failing with ETIMEDOUT. 11. Enhanced NFS version 3 to support the full 32k read/write block size. PHNE_20091: 1. Automountd not using LOFS to mount local filesystems. PHNE_20021: 1. Panic found during internal testing in cachefs with autofs. PHNE_19426: 1. Client process can hang forever over NFS. This can occur when an NFS client generates a high amount of write requests, and the NFS server is very busy. Once the process is hung it cannot be killed. 2. Client might see many networking timeouts using NFS version 3. 3. NFS file creation fails with EACCESS when open() is called with O_TRUNC|O_EXCL. 4. mknod of /dev/rroot (c 255 0xffffff) fails over NFS mount. 5. 10.20: implicit UDP bind results in using inp_lport==0 in ku_fastsend. 6. NFS client panic when mounting using smaller than 1k block size. 7. Loading executable file or running memory map applications over NFS will fail when NFS read/write block size is not set to 4k increment. 8. Autofs not always triggering a re-mount with concurrent mounts and umounts, incorrectly gets error ENOENT - "No such file or directory" 9. Autofs hangs even with PHNE_17200 when running scripts triggering concurrent mount/umount 10. Autofs - cp(1) to inactive direct mount fails with error EOPNOTSUPP - "Operation not supported" 11. Autofs - mv command fails in direct mnt with error ENOSYS - "Function is not available" PHNE_19073: 1. Autofs chooses a slower replicated server 2. AutoFS does not support the "port" option 3. Processes locking files over NFS may hang in case of a loopback mount. 4. rpc.lockd logging is difficult to interpret. PHNE_19072: 1.Enhanced nfsconf to support Networking Ace bundle. PHNE_18961: 1. Some Sun's clients using Automount might fail to mount when HPUX's server setting MOUNTD_VER to 2 in /etc/rc.config.d/nfsconf 2. Memory leak in the NFS client system when using NFS file locking. PHNE_18962: 1. Some Sun's clients using Automount might fail to mount when HPUX's server setting MOUNTD_VER to 2 in /etc/rc.config.d/nfsconf 2. Memory leak in the NFS client system when using NFS file locking. PHNE_18915: 1. Some Sun's clients using Automount fail to mount when HPUX's server setting MOUNTD_VER to 2 in /etc/rc.config.d/nfsconf PHNE_17842: 1. on(1) command fails when using AutoFS mounted home directories. 2. nis.server script won't run correctly unless the new nfsconf is installed at the same time. 3. automounter incorrectly tries to re-mount an NT filsystem 4. rpc.mountd will not match given hostname unless it is an exact case match. 5. stdhosts command fails on lines longer than 256 char. 6. ypmake builds hostmap in upper or lower case keys. 7. make.script builds hostmap in upper or lower case keys. 8. ypserv runs out of file descriptors. 9. automount caught in loop. 10.rpc.statd and rpc.lockd hang in an attempt to send messages to each other. 11.rpc.lockd does not support version 4 share and freeall functions. 12.rpc.lockd core dumps with a segmentation fault. 13.rpc.lockd fails causing data corruption. 14.rpc.lockd core dumps. 15.The nfsconf script has been enhanced to support the new patch structure. See the Special Installation Instructions for more details 16.The nfs client start up script has been enhanced to support the new patch structure. See the Special Installation Instructions for more details 17.The nfs mount demon has been enhanced to support the new patch structure. See the Special Installation Instructions for more details. 18.The nfs mount command has been enhanced to support the new patch structure. See the Special Installation Instructions for more details 19.The automount command has been enhanced to support the new patch structure. See the Special Installation Instructions for more details 20.The automount man page has been enhanced to support the new patch structure. See the Special Installation Instructions for more details 21.The autofs deamon has been enhanced to support the new patch structure. See the Special Installation Instructions for more details 22.The nfs mount man page has been enhanced to support the new patch structure. See the Special Installation Instructions for more details 23.The nfs mountd man page has been enhanced to support the new patch structure. See the Special Installation Instructions for more details PHNE_17619: NOTE: This ONC+/NFS patch has been reconstructed to deliver the ONC+/NFS Networking ACE products (NFS PV3, AutoFS, and CacheFS). In addition, the older NFS Automounter will be delivered, along with configuration scripts (in /etc/rc.config.d/nfsconf) necessary to select AutoFS, or the Automounter, or neither. Please read the NOTE in Special Installation Instructions for more details. 1. With a umask of 027, a write followed by a sleep followed by another write (all over an NFS mount) fails with a "Permission denied" error. 2. Autofs hangs when manual unmounts are used 3. NFS PV3 only supports up to 8k read/write transfer size 4. NFS PV3 performs poorly when writing small records in synchronous mode. 5. Cannot copy NFS PV3 Large files greater than 2GB from the NFS mounted file system to the local file system. 6. NFS3ERR_JUKEBOX is not handled in 10.20 ACE PV3 7. System hang/sleep at clntkudp_callit() at outbuf and not waking up 8. NFS file can be removed even when the file is still being referenced. 9. The system may panic with a kernel stack overflow. 10. Root trying to write to an NFS mounted file that is not writable by root can reset the file size to zero on 10.20 PV3. 11. 10.20 Client writes NULL characters into file even though client application did not generate them. 12. System panic while doing reading or writing over cachefs mount point for a long period of time. PHNE_17620: NOTE: This ONC+/NFS patch has been reconstructed to deliver the ONC+/NFS Networking ACE products (NFS PV3, AutoFS, and CacheFS). In addition, the older NFS Automounter will be delivered, along with configuration scripts (in /etc/rc.config.d/nfsconf) necessary to select AutoFS, or the Automounter, or neither. Please read the NOTE in Special Installation Instructions for more details. 1. With a umask of 027, a write followed by a sleep followed by another write (all over an NFS mount) fails with a "Permission denied" error. 2. Autofs hangs when manual unmounts are used 3. NFS PV3 only supports up to 8k read/write transfer size 4. NFS PV3 performs poorly when writing small records in synchronous mode. 5. Cannot copy NFS PV3 Large files greater than 2GB from the NFS mounted file system to the local file system. 6. NFS3ERR_JUKEBOX is not handled in 10.20 ACE PV3 7. System hang/sleep at clntkudp_callit() at outbuf and not waking up 8. NFS file can be removed even when the file is still being referenced. 9. The system may panic with a kernel stack overflow. 10. Root trying to write to an NFS mounted file that is not writable by root can reset the file size to zero on 10.20 PV3. 11. 10.20 Client writes NULL characters into file even though client application did not generate them. 12. System panic while doing reading or writing over cachefs mount point for a long period of time. PHNE_17098: 1. After Installation of PHNE_17055 the customer modifiable version of ypmake is overwritten. PHNE_17055: 1. Nfsd file missing after Install of PHNE_16117. networking stops on server. PHNE_16924: The system may panic with a data page fault. NOTE: Patch PHNE_16924 installs a patch for the networking ACE 2 software bundle (PHNE_13833) only if that bundle has been installed on the system. Otherwise, patch PHNE_16924 installs a patch for the standard release and its patches (represented by PHNE_13823). PHNE_16925: The system may panic with a data page fault. NOTE: Patch PHNE_16925 installs a patch for the networking ACE 2 software bundle (PHNE_13834) only if that bundle has been installed on the system. Otherwise, patch PHNE_16925 installs a patch for the standard release and its patches (represented by PHNE_13824). PHNE_16117: 1. mknetid mknetid core dumps. 2. rpc.yppasswdd If a password contains a ":", it cannot be changed via NIS. 3. ypbind Missing ypbind file slows NIS performance. 4. ypmake When "ypmake mapname with NOPUSH=1" is issued on the NIS master, transferring the newly made map by ypxfr on the NIS slave would fail sometimes. 5. ypxfrd ypxfrd times out due to libndbm performance problem. 6. automount Automounter removes entry for filesystem if server down. 7. automountd AutoFS will not unmount LOFS mounts AutoFS will not unmount CacheFS filesystems Duplicate entries in /etc/mnttab error message in syslog not removed. 8. nfs.client nfs.client script does not kill biod daemons. rpc.lockd does not reclaim locks after NFS server reboots. 9. rpc.lockd rpc.lockd behaves incorrectly in the NLM_CANCEL case. Loss of UDP NFS file locking packets results in a growing msg queue. 10. rpc.pcnfsd rpc.pcnfsd allowed any user to change permissions on the spool directory. 11. /sbin/fs/autofs/mount The unmount for autonodes timeout is 10 minutes. 12. exportfs reads and writes will fail if clients hostname resolves to more than one IP address. PHNE_15863: 1. Processes may hang when trying to access files across NFS. 2. The system may panic with a data page fault when an NFS operation is interrupted on a uniprocessor system. 3. The system may panic with a data page fault when reading a file that has been truncated. 4. The system may panic with a kernel stack overflow. 5. Syslog shows the message: vxfs: mesg 016: vx_ilisterr 6. Quotas are not honored on a diskless client in the same way that they are honored on its server under certain circumstances. 7. The setting of NFS file/directory modification and access time stamps is inconsistent. 8. An HP NFS server does not permit NFS file/directory time stamps to be set from a non-HP NFS client. 9. Autofs hangs when remounting hierarchical autofs mount points (this applies only to systems that have the ACE 2 software bundle installed). 10. Autofs hangs when running Netscape (this applies only to systems that have the ACE 2 software bundle installed). 11. System hangs when using NFS PV3 as a server (this applies only to systems that have the ACE 2 software bundle installed). 12. Cachefs hangs (this applies only to systems that have the ACE 2 software bundle installed). 13. When an archive library is in an NFS PV3 mounted directory, nm gives the "bad magic" error string after listing all symbols (the symbols list is fine). This problem does not occur with NFS PV2 (this applies only to systems that have the ACE 2 software bundle installed). 14. The system may panic with a data page fault on an NFS PV3 server and shows rfs3_readlink_free() in the panic stack trace (this applies only to systems that have the ACE 2 software bundle installed). 15. A read() after an lseek() past EOF is successful (this applies only to systems that have the ACE 2 software bundle installed). 16. A cp over an NFS PV3 mount encounters an error: Value too large to be stored in data type NFS PV2 does not encounter the error (this applies only to systems that have the ACE 2 software bundle installed). NOTE: Patch PHNE_15863 installs a patch for the networking ACE 2 software bundle (PHNE_13833) only if that bundle has been installed on the system. Otherwise, patch PHNE_15863 installs a patch for the standard release and its patches (represented by PHNE_13823). PHNE_15864: 1. Processes may hang when trying to access files across NFS. 2. The system may panic with a data page fault when an NFS operation is interrupted on a uniprocessor system. 3. The system may panic with a data page fault when reading a file that has been truncated. 4. The system may panic with a kernel stack overflow. 5. Syslog shows the message: vxfs: mesg 016: vx_ilisterr 6. Quotas are not honored on a diskless client in the same way that they are honored on its server under certain circumstances. 7. The setting of NFS file/directory modification and access time stamps is inconsistent. 8. An HP NFS server does not permit NFS file/directory 9. Autofs hangs when remounting hierarchical autofs mount points (this applies only to systems that have the ACE 2 software bundle installed). 10. Autofs hangs when running Netscape (this applies only to systems that have the ACE 2 software bundle installed). 11. System hangs when using NFS PV3 as a server (this applies only to systems that have the ACE 2 software bundle installed). 12. Cachefs hangs (this applies only to systems that have the ACE 2 software bundle installed). 13. When an archive library is in an NFS PV3 mounted directory, nm gives the "bad magic" error string after listing all symbols (the symbols list is fine). This problem does not occur with NFS PV2 (this applies only to systems that have the ACE 2 software bundle installed). 14. The system may panic with a data page fault on an NFS PV3 server and shows rfs3_readlink_free() in the panic stack trace (this applies only to systems that have the ACE 2 software bundle installed). 15. A read() after an lseek() past EOF is successful (this applies only to systems that have the ACE 2 software bundle installed). 16. A cp over an NFS PV3 mount encounters an error: Value too large to be stored in data type NFS PV2 does not encounter the error (this applies only to systems that have the ACE 2 software bundle installed). NOTE: Patch PHNE_15864 installs a patch for the networking ACE 2 software bundle (PHNE_13834) only if that bundle has been installed on the system. Otherwise, patch PHNE_15864 installs a patch for the standard release and its patches (represented by PHNE_13824). PHNE_15541: 1. automountd automountd with LOFS turned on. All local filesystems will be mounted using lofs instead of loopback nfs. 2. rpc.statd rpc.statd core dumps during string compare operation. 3. autofs_setup If the transition links are removed the scripts autofs and autofs_setup fail. 4. autofs If the transition links are removed the scripts autofs and autofs_setup fail. 5. rpcinfo -p does not report that NFS PV3 is running. PHNE_15041: 1. Poor NFS performance over 100BT. 2. System panics with data page fault (this applies only to systems that have the ACE 2 software bundle installed). 3. Application fails (this applies only to systems that have the ACE 2 software bundle installed). 4. Application fails (this applies only to systems that have the ACE 2 software bundle installed). NOTE: Patch PHNE_15041 installs a patch for the networking ACE 2 software bundle (PHNE_13833) only if that bundle has been installed on the system. Otherwise, patch PHNE_15041 installs a patch for the standard release and its patches (represented by PHNE_13823). PHNE_15042: 1. Poor NFS performance over 100BT. 2. System panics with data page fault (this applies only to systems that have the ACE 2 software bundle installed). 3. Application fails (this applies only to systems that have the ACE 2 software bundle installed). 4. Application fails (this applies only to systems that have the ACE 2 software bundle installed). NOTE: Patch PHNE_15042 installs a patch for the networking ACE 2 software bundle (PHNE_13834) only if that bundle has been installed on the system. Otherwise, patch PHNE_15042 installs a patch for the standard release and its patches (represented by PHNE_13824). PHNE_14071: 1. The system may panic with a data memory protection fault. 2. Processes may hang when trying to access files across NFS. 3. The system may panic with a data page fault. 4. The system may panic with a vn_rele. NOTE: Patch PHNE_14071 installs a patch for the networking ACE 2 software bundle (PHNE_13833) only if that bundle has been installed on the system. Otherwise, patch PHNE_14071 installs a patch for the standard release and its patches (represented by PHNE_13823). PHNE_14072: 1. The system may panic with a data memory protection fault. 2. Processes may hang when trying to access files across NFS. 3. The system may panic with a data page fault. 4. The system may panic with a vn_rele. NOTE: Patch PHNE_14072 installs a patch for the networking ACE 2 software bundle (PHNE_13834) only if that bundle has been installed on the system. Otherwise, patch PHNE_14072 installs a patch for the standard release and its patches (represented by PHNE_13824). PHNE_13833: This patch is part of the 10.20 ACE 2 bundle which adds networking enhancements to 10.20. New networking features supported in ACE 2 include NFS Version 3.0, AutoFS, and CacheFS. PHNE_13834: This patch is part of the 10.20 ACE 2 bundle which adds networking enhancements to 10.20. New networking features supported in ACE 2 include NFS Version 3.0, AutoFS, and CacheFS. PHNE_13823: 1. Processes may hang when trying to access files across NFS. 2. The system may panic with a spinlock deadlock. PHNE_13824: 1. Processes may hang when trying to access files across NFS. 2. The system may panic with a spinlock deadlock. PHNE_13731: 1. ypserv ypserv stops answering some queries for entries outside domain on a slow system 2. rpc.pcnfsd rpc.pcnfsd does not allow logins with trusted systems. rpc.pcnfsd was enhanced to spawn a process to do lpstat -v. 3. namesvrs-nis.server Ypinit -s on HP machine results in error messages when an IBM machine is the master. 4. rpc.statd client never responds to servers SM_NOTIFY message after reboot. Appears hung. 5. netgroup.4 Man page unclear on use of domainnames. 6. ypclnt.3c Man page unclear on use of free() for get_default_ domain() call. 7. pcnfsd.1m manpage updated to reflect new changes. 8. yppasswdd.1m manpage references /var/adm/ptmp instead of /etc/ptmp. 9. Only a limited number of client processes can simultaneously connect to the server process. 10. portmapper stops responding to requests. Note: This patch will not patch the ACE 2 networking modules unless the "Networking ACE for HP-UX 10.20 (April 1998) Bundle" has been previously installed To install "Networking ACE for HP-UX 10.20 (April 1998) Bundle" visit http://www.software.hp.com. PHNE_13835: This patch is part of the 10.20 ACE 2 bundle which adds networking enhancements to 10.20. New networking features supported in ACE 2 include NFS Version 3.0, AutoFS, and CacheFS. PHNE_13668: Client IO from root is denied across an NFS mount point, causing hang in instant ignition and NFS clients. PHNE_13669: Client IO from root is denied across an NFS mount point causing hang in instant ignition and NFS clients. PHNE_13235: 1. JFS Servers with NFS clients may see poor performance when doing large file transfers across NFS 2. When using swap across an NFS mount, and the mounted disk becomes full, the system may panic. 3. Data corruption may occur when a transmission errors on a crowded network force retransmissions. PHNE_13236: 1. JFS Servers with NFS clients may see poor performance when doing large file transfers across NFS 2. When using swap across an NFS mount, and the mounted disk becomes full, the system may panic. 3. Data corruption may occur when a transmission errors on a crowded network force retransmissions. PHNE_12427: The exportfs -u command hangs. PHNE_12428: The exportfs -u command hangs. PHNE_11386: Hang when doing IO across an NFS mount PHNE_11387: Hang when doing IO across an NFS mount PHNE_11008: 1. Some instances of NFS writes (such as cp from an NFS client) may complete successfully even when errors occur. 2. Renaming a VxFS file to another VxFS from a PCNFS client causes a panic. 3. Disabling anonymous access is not recognized by PCNFS clients, allowing them to run as a priviledged user. 4. Data page faults caused in the client 5. Directories in an NFS mounted file system are created with 000 permissions value. PHNE_11009: 1. Some instances of NFS writes (such as cp from an NFS client) may complete successfully even when errors occur. 2. Renaming a VxFS file to another VxFS from a PCNFS client causes a panic. 3. Disabling anonymous access is not recognized by PCNFS clients, allowing them to run as a priviledged user. 4. Data page faults caused in the client PHNE_10894: 1. automount: automount does not correctly support the "nodevs" mount option. 1653218305/INDaa27653 2. rpc.lockd: Enhancement to rpc.lockd to fix problem of forwarding unlocks to kernel contained a bug that caused rpc.lockd to send incorrect unlock range to the kernel. Applications failed with unexpected results due to this problem. INDaa26432/INDaa26633 3. rpc.mountd: Rpc.mountd does not handle requests from an IBM machine. 1653207654 4. rpc.rquotad: rpc.rquotad has memory leak. 5003373092 5. pcnfsd.1m: Man page for PCNFSD not correct. The man page does not list the entry for /etc/shells. 5003332296/INDaa26031 PHNE_10515: 1. rpc.lockd: rpc.lockd forwards unlock to kernel when no match exists in queue. Cause was Unlock range passed into kernel by rpc.lockd via nfs_fcntl() call was incorrect. Read Locks are now examined for overlapping regions and non-overlapping regions are deleted selectively in the kernel. When a unlock rqst with range offset=0 and len=0 from a client is received at LOCKD ,LOCKD will now examine if the client had any NFS locks on the file and selectively delete kernel locks held by that client. 5003355784/INDaa26432 Ksh hangs when $HOME is nfs mounted and HISTFILE is under $HOME. This defect is discussed in an earlier patch,but an additional problem due to too frequent retransmits has been fixed. This caused rpc.lockd to invalidate cache entries more often than required. A timestamp has been added to struct reclock which keeps track of the time the request got queued up in the retransmit queue. This timestamp is used in nlm_call() to prevent retransmits of that request from occurring more frequently than 10 secs. INDaa25087 2. rpc.yppasswdd Rpc.yppasswdd when started from the command line with Sun options (nogecos, nosh, nosingle,nopw) did not handle these properly. Since HP does not support these options they were never activated. However, Sun systems do use them and if they are given to an HP machine they should handle them correctly. The options now give the correct response but are still not yet supported fully. PHNE_9864: Directories in an NFS mounted file system are created with 000 permissions value. PHNE_9465: exports.4: 1. Exports man page comments cause exportfs to use them as illegal hostnames. Also has incorrect anonymous information. exportfs.1m: 1. Exportfs man page has wrong information for anonymous access defaults. secure_rpc.3c: 1. Get_myaddress() call has wrong information on man page on what it actually does. rpc.lockd: 1. Enhance lockd logging of duplicate messages and correct hang problem. pcnfsd: 1. Doesn't work correctly with wlogin() changes ypxfr: 1. Ypxfr doesn't tell user that it is retrying ypxfr if ypxfrd is not found. PHKL_9155: 1. Add write-gathering support for NFS servers. 2. The length of a timeout for an NFS request may become extremely long (on the order of minutes). PHKL_9156: 1. Add write-gathering support for NFS servers. 2. The length of a timeout for an NFS request may become extremely long (on the order of minutes). PHKL_8544: 1. Data page fault in an MP environment due to synchronization problems with the client's biod's. 2. A panic within kernel RPC (in svc_getreqset) in an MP environment is generated due to another synchronization problem. 3. System hangs caused in large systems. PHKL_8545: 1. Data page fault in an MP environment due to synchronization problems with the client's biod's. 2. A panic within kernel RPC (in svc_getreqset) in an MP environment is generated due to another synchronization problem. 3. System hangs caused in large systems. PHNE_8310: automount: 1. Automount cannot correlate entries in log file to entries in syslog.log because of missing timestamps. rpc.rquotad: 1. rquotad doesn't support JFS rpc.lockd: 1.Logging of unnecessary messages to log file rpc.statd: 1. Possible mem leak problem. rpc.yppasswdd: 1. rpc.yppasswdd fails to rename mnttab if /tmp is on a separate partition. rpc.mountd: 1. mount daemon runs from non-privileged ports. exportfs: 1. Hostname containing the string "rw" is erroneously flagged as a mutually exclusive error when the host is also tagged as -ro. rpc.pcnfsd: 1. Enhanced pcnfsd logging in wtmp file to include ip and system name of caller. makedbm: 1. Makedbm now issues an error if the hash algorithm is exceeded. ypserv: 1. NIS returns wrong nextkey when concurrent access is allowed to maps. ypwhich: 1. ypwhich fails connection on X.25 interface. PHCO_9543: If a file system is mounted on system over NFS, and the file system goes down, doing a bdf will report and error of "Stale NFS File handler". The current NFS umount will not allow this file system to be unmounted, even if the file system comes back on the original Defect Description: PHNE_24143: automountd JAGad50086 The automountd code was not parsing the quota option from the options string. Resolution: Added a hasmntopt call to check for the quota option and set the quota flag as needed. automountd JAGad66625 Hostname checking routine in automountd, to determine if the mounted host is a local machine, was coded incorrectly causing it to return FALSE, meaning "not local machine", when a hostname other that that returned by hostname() was used in the map. This caused automountd to mount the local directory to nfs type, not lofs. Resolution: Rewrote hostname checking routine to use ioctl to find and match local hostname and return TRUE when using private hostname in the autofs map. libnfs.a JAGad45257 Due to a race condition in AutoFS, nodes could become corrupted. Corrupted nodes could eventually result in empty AutoFS directories. Resolution: Modified the code to eliminate the race condition. libnfs.a JAGad62727 For direct mounts, AutoFS would not wait for mounts to complete when accessing the direct mount point. This would trigger a second mount creating a duplicate entry in the /etc/mnttab file. Resolution: Added code in AutoFS to wait for mounts in progress for direct mount points. rpc.mountd JAGad36434 When a diskless Linux machine tries to mount the root disk "/" with AUTH type of AUTH_NONE, the mount fails. Resolution: file: For a mount request with AUTH_NONE, return the machine name obtained from the previous gethostbyaddr call in getclientsname routine in rpc.mountd.c. PHNE_22877: libnfs.a JAGad08145 From gprof data collected, it showed that the dnlc_purge() was not properly used to purge the entire dnlc cache. Also the rnode hash table size and algorithm was inefficent so that more than 1000 entries hashed in the same hash bucket. Resolution: Used the appropriate dnlc_purge_vp per file and dnlc_purge_vfs per file system to purge only cache entries needed instead of entire cache table. Also increased the rnode hash table size and algorithm to provide a better distributed hash table and algorithm. libnfs.a JAGaa24099 Memory leak in rfs_readdirplus3() in NFS PV3. Resolution: Now the size to be malloc'ed is checked. No memory is allocated when the number of entries not already read in the directory is 0. libnfs.a JAGad04988 Race condition between mount and umount with ufs filesystems. Resolution: Check VFS_MOUNTING flag in make_unmount_list and get_hierarchical_mounts. libnfs.a JAGad29062 When an unmount request comes in to the automountd, it stats each file system to find the entry with the matching file system id. The stat command updates the reference times of the autonodes, preventing them from unmounting when they should. Resolution: AutoFS now uses an existing macro to make sure that the calling process is not automountd before updating the reference times of autonodes. libnfs.a JAGad14044 Cannot remove a file or a hardlink to that file, depending on which is removed first; the first one to be removed will succeed and will be renamed, the second one to be removed will get an error. Resolution: Busy file and its hardlink will be removed without an error. PHNE_22893: {Site Specific Patch} PHNE_22288: automount, automountd JAGac78988 autofs does not time the return from replicated servers in a consistent manner. If the replicated server list has some host names being retrieved from DNS or NIS, then their apparent response time tends to be greater and hence they become less "responsive". These hosts are always picked up later. Resolution: Modified the code to remove dependencies on the timing of hostname lookup. JAGad02090 automountd leaks memory when processing a map entry involving a list of replicated hosts. This memory was identified to be temporary storage used to determine the "best" host from the list of hosts. Resolution: Modified the code in "nfs_cast::nfs_cast()" and related modules to release temporary storage used for tracking replicated host responses. automountd JAGab71724 When a map entry for a cachefs mount is specified, autofs fails to parse more than one host entry. Instead it treats the entire entry as one host name, causing an error on the mount if the map entry represents a replicated (multiple) host. Resolution: Proper loading of default mount options. JAGad21864 During unmount operations, automountd incorrectly returns a success error code to the kernel, which causes the kernel to remove autonode data structures. Subsequent events then cause autonodes to be created with partial data, which results in the bdf command anomaly. Resolution: Modified automountd code to return the correct error code to the kernel during unmount operations. mount JAGac40027 A GETPORT request (which should return the identity of the mountd port number), sends a PROG_MISMATCH reply. The server should be replying to the GETPORT call with the port number of the version which they currently support. Then when the client sends in a NULL procedure call to that daemon it should reply with PROG_MISMATCH and give the low and high version numbers. Resolution: Lower the version number in the GETPORT request and re-try. rpc.lockd JAGad00646 There are routines that call "xmalloc()" but do not check the value returned. A "NULL" pointer is returned from "xmalloc()" when no memory is available. A "NULL" pointer value causes a "core dump" if used to access data. Resolution: Check the return value of xmalloc() in prot_nlm_share(), prot_nlm4_share(), new_sxx() and new_sxx4(). Log the reason of failure in these routines. JAGad14812 When a client crashes after locking a remote file, the server does not grant the lock held by the crashed client to other clients waiting for the lock. Resolution: Code modified. Server now releases the lock information held by the crashed client. Another client waiting for the same lock can now obtain it. rpc.mountd, rpc.rexd, rpc.rquotad, rpc.rusersd, rpc.rstatd, rpc.sprayd, rpc.statd, rpc.rwalld, rpc.yppasswdd, ypbind, ypserv JAGab17308 When the executables are run with logging enabled, any dates after year 2000 reports three digits for the year (e.g. 100 instead of 00). Resolution: Removed the year from the date, in logging. rpc.mountd JAGad03388 svc_run_ms() function in the rpc.mountd takes only 60 file descriptors, which is hard coded. This value needs to be changed to the system-wide tunable file descriptor limit. Resolution: Set the number of file descriptors for svc_run as a kernel tunable value, the soft limit of the file descriptors. rpc.statd JAGad00517 There are routines that call "xmalloc()" but do not check the value returned. A "NULL" pointer is returned from "xmalloc()" when no memory is available. A "NULL" pointer value will cause a "core dump" if used to access data. Resolution: Check the return value of xmalloc() in insert_name() and logged the reason for failure in this function. rpc.statd JAGad05198 When an unknown host requests a file lock, rpc.statd in the server site cannot add this client to the monitor queue as the hostname is not resolved. So the lock request fails. But the unknown host keeps sending lock requests, which causes the memory region of rpc.statd to be used up and finally abort. Resolution: The insert_mon() in rpc.statd is called to add a client to the monitor queue. In case that this routine fails, free the memory area allocated before this routine is called. ypserv JAGad03431 NIS server eventually closes its UDP socket, thus becoming useless for local ypbind and every other NIS client which has to find another NIS server using UDP broadcast. Resolution: Destroy the server handle for the TCP connection only and not for the UDP connection. JAGad12245 There is a hard coded value (64) in ypserv for the total number of file descriptors that the select call is tested on. This causes ypserv to be unavailable after using 64 file descriptors. Resolution: Modified svc_run_as() to get the kernel parameter for the range of the file descriptors in select call. PHNE_22892: {Site Specific Patch} PHNE_22117: libnfs.a JAGad10180 When a file is truncated on the server the client never sees the new smaller size. Hence the client displays null characters at the end of the file. Resolution: The logic to update the atttribute cash is fixed to update the size in all cases (if the size on the server is larger or smaller than the size on the client). PHNE_21704: 1. Code had some printf messages which filled the syslog and dmesg when CacheFs is used. JAGad08894 SR:8606139585 Resolution: The printf messages which were causing this have been deleted. PHNE_21375: automountd JAGad09141 A un-initialized variable being used as an argument in a "pingnfs" call in the automountd "unmount" procedure was causing the call to fail with an RPC_PROG_MISMATCH error. Resolution: Changed the problematic "pingnfs" call argument to an initialized value. PHNE_21108: 1. When hierarchical indirect maps are used on 10.20 these maps fail with a mkdir error from automountd. The same maps work on 11.0 systems. Resolution: Allow indirect maps lookups initiated by the daemon to always succeed. Affected module: auto_vnops.c 2. The new read ahead algorithm calculates the number of blocks to read ahead, instead of doing two blocks read ahead everytime. The max number of blocks to read ahead is 4. If the calculated read ahead blocks is larger than the nfs read head max, the max is applied. Resolution: Enhancement. The new read ahead algorithm calculates the number of blocks to read ahead, instead of doing two blocks read ahead everytime. The max number of blocks to read ahead is 4. If the calculated read ahead blocks is larger than the nfs read head max, the max is applied. The rw3vp() routine in nfs3/hpnfs_vnops.c and rwvp() routine in nfs/nfs_vnops.c have been changed. 3. When two processes write to the same file, Null characters are written to the file. This problem does not occur when -noac (no attribute caching) is specified at mount time. NFS write code has a race condition where the second process zeroes out the buffer the first process has written to, if the write size is less than nfs block size of 8K. Resolution: A partial fix was put in to check if r_size has increased while the process waits for an empty buffer and not zero out the buffer is r_size has increased. The condition was coded in error to zero out the buffer is r_size has increased. Fix the if condition to not zero out if r_size is larger than previous value. rw3vp() routine in nfs3/hpnfs_vnops.c and rwvp() routine in nfs/nfs_vnops.c have been changed. The second race condition is in getattr code, where r_size is updated with size received from the server, when r_size is larger and more accurate. r_size should be updated only if r_size is smaller than the server file size and client has dirty buffers to flush. nfsgetattr3() routine in nfs3/nfs_vnops3.c and nfsgetaatr() routine in nfs/nfs_vnops.c have been changed. 4. A NFS client was experiencing many retransmissions of NFS packets (viewable in a nettle trace) but nfsstat is not incrementing the retrans counter. This was because the retrans counter was only being incremented if a packet we tried to send on the wire failed due to resource problem. But the retrans counter should be incremented regardless of why the call failed, if the call failed. Resolution: Code change. In clntkdup_callit() in rpc/clnt_kudp.c the retrans incrementation check was moved out of the RPC_SYSTEMERROR if statement. 5. For each directory argument,the ls command lists the contents of the directory. The -s options gives size in blocks for each entry. If the ls -s command was run on the same directory on the client and the server, different block sizes was reported for the files. The problem was due to the fact that the MAXBSIZE used for the calculation of va_blksize in fattr_to_vattr3() in nfs3/nfs_subr3.c was 64K, unlike 11.0 code or Sun code where it is 8K. Resolution: The solution was to include onc+sys/param.h in nfs_subr3.c where MAXBSIZE = 8K. Previously only h/param.h was included where MAXBSIZE=64K. 6. The link(2)(1M) does not return an EEXIST on NFS PV3 mounted directory though there is a linking file. This was due to the fact that that in most error cases we were branching to out: where the error conditon was reset to NFS3_OK. This erased the previous error condition. Resolution: Code change in rfs_link3(). Setting the status to NFS3_OK has been moved out of out:. 7. Holding a spinlock and calling binvalfree() causes the panic. Resolution: Code change. Release spinlock before calling binvalfree() in nfs_setattr3(). PHNE_20957: 1. A kernel variable has been changed to support NFS 32k read/write block size. Glance made reference to this variable and it fails to start when it can't find this variable even though Glance doesn't use this variable for NFS statistics. Resolution: Reintroduce this variable back to NFS kernel to allow glance to start correctly. PHNE_20628: 1. Only 10% of a dedicated file system was used by cachefs. This was because the value of a variable ftmp which is used to calculate the c_label.cl_maxblks was being calculated too small. This was because MAXBSIZE was used in the calculation of ftmp. MAXBSIZE in HP-UX is 64K unlike SUN. Resolution: Instead of MAXBSIZE now file system specific block size is used to calculate the value of ftmp. 2. When mail.aliases contains no space around ":", makemap, which is called by ypmake, fails. Resolution: Changed sed command in ypmake and Makefile to substitute a space in place of a colon for building the mail.aliases map. 3. rpc.lockd is not able to correctly identify the case where a lock is local or remote and take the appropriate action. Resolution: Made the change to remote_data(), the function that is used to determine if data being locked/unlocked is at remote side or not. Put in additional checking when strcmp() against two host names not the same, if short name of two hosts are the same, comparing IP addresses to determine the result. Also made the change to overlap() so that rpc.lockd wakes up and promotes the lock. 4. rpc.lockd retrieves/caches the port number of remote end after dealing with the LOCK, UNLOCK, TEST and CANCEL requests, however it only adds the monitor entry for LOCK requests. Resolution: Made the change to call add_mon() inside the function klm_prog() such that we add the monitor entry regardless of the KLM request. 5. rpc.statd has the dependency on the object files resided in rpc.lockd. Since rpc.lockd build environment has been changed, the Makefile file for rpc.statd should be changed accordingly. Resolution: Corrected the Makefile on rpc.statd dependency. 6. Modified Mount NFS manpage to mention 32k read/write block size support. Resolution: Modified Mount NFS manpage to mention 32k read/write block size support. 7. The automount config program for autofs can hang due to the presence of a static mount from an unresponsive NFS server. This can result in autofs startup problems. Resolution: Recompile existing code. Existing fixes for automountd libraries will be incorporated which prevent unnecessary stat() calls. 8. When autofs is ready to unmount a directory, it would wait indefinitely for the host to respond to its unmount request, appearing to hang. Resolution: Code to check (using nfsping) that host responds before attempting to send RPC unmount request or stat()/lstat() across the mountpoint. Also include additional logging (at new level 4) for stat()/lstat(). 9. As rpc.mountd is asked to mount and unmount over NFS, it "hashes-out" entries in /etc/rmtab to indicate they are no longer mounted. Each new mount creates a new entry. Over time and lots of mount activity, this file grows too large. Resolution: Implement a cleanup scheme whereby a threshold of deleted entries will trigger the rewriting of the /etc/rmtab. 10. The logging function called by rpc.mountd was updated previously but rpc.mountd was not re-linked to use it. Resolution: The new logging function is incorporated by the re-linking of rpc.mountd. 11. The "~" character was not allowed as part of spool file name, therefore any print request was rejected if the file name contained the "~" character. Resolution: Made a change to suspicious(), the routine used to check for suspicious characters in the print file name. Made a change to pr_init() to take away redundant checking and leave suspicious() to do the checking. Added more code on checking if a printer name is valid with valid_pr(). PHNE_20626: 1. Automountd is parsing executable maps erroneously. Resolution: Automountd fixed to parse executable maps correctly. 2. On a system which has a system setting of maxfiles > 2048, if replicated automounts are used, the automountd function nfs_cast() will return EBADF and fail to mount. Resolution: Limit the size of the select() block to FD_SETSIZE entries or less. 3. Showmount -a on an NFS server always prints an entry for an AutoFS mount point even after disconnecting from the client, if the client is PV3 (not PV2). Resolution: Fix bug in PV3 nfsunmount() which opened server connection incorrectly. PHNE_20313: 1. With PHNE_19426, autofs controlling cachefs indirect map will hang on mount Resolution: Improve detection logic to allow automountd detection logic to detect mount calling mount or unmount calling unmount. Change applied to AUTOFS_PROCESS_IS AUTOMOUNTED macro in kernel. 2. The timeo option in the mount command does not have any effect when set. Resolution: A change in the NFS kernel to make use of this option passed down by the NFS mount command. 3. Untar-ing a large quantity of files over NFS can be slow. NFS sometimes needs to invalidate it's client cache to ensure that it's cache is not stale (binvalfree). It is in this path that NFS makes some unnecessary calls to binvalfree, which slows down the Untar operation. Resolution: A performance enhancement has been made to the NFS kernel to avoid some calls to binvalfree. 4. NFS version 3 client is very slow when performing a write operation to a Celerra server. The Celerra server doesn't implement post attribute return on error which is part of the NFS version 3 protocol, but is not a required feature. What is required is that a client must handle this scenario correctly and this is what out NFS client has failed to do. Resolution: A change in the NFS path has been made to handle the scenario where a server does't return post attribute on error. 5. The 'maxcnodes' s a constant(= MAXCNODES ) the value of which is 500. Sometimes this is too low a value when a dedicated file system is used for Cahefs. Resolution: The value of 'maxcnodes' variable will now be a computed value which defaults to 50% of ninode. One can cahnge the value with adb. There is a feature, that if the user does not like the changed value, you can set maxcnodes=0x7fffffff and on the next Cachefs mount the value will be set to 50% of ninode again. 6. The command fuser does not work over a Cachefs mount point though fuser -c does. As a result the ServiceGuard scripts fail to work because fuser -k cannot kill the processes keeping the mount points busy. The root cause is that the v_nodeid field in the cnode is not set. Resolution: Set the v_nodeid field in the cnode with the fid returned in the attributes. Also one has to set the kernel parameter "pi_newmnttype". One can use adb to turn on the pi_newmnttype, or this can be done by the command onccompat -n. 7. diff(1) failed due to invalid name length returned by NFS pathconf(2) from HP Server on regular files. HP's local file system does not support pathconf(2) on regular files and when AIX generates pathconf(2) call on regular files, server replies with name length of zero. Resolution: When a file argument is passed in to nfs server code: rfs_pathconf(),it is now converted to the parent directory before calling and passing the value to the underlying filesystem pathconf() call. 8. MP_Spinlock was omitted in nfs3_do_bio() in hpnfs_vnops.c. This could have caused a panic when cred was decremented. Resolution: MP_Spinlock was added to nfs3_do_bio(). 9. 10.20 NFS-servers always do send an NFS3ERR_TOOSMALL reply as a last packet during an readdirplus-call. SUNs solstice PC-NFS-client and DEC-clients cannot handle this error message and fail while accessing the directory. Resolution: Code change. Remove nents==0 code from rfs_readdirplus3. 10. nfs_mount() routine frees mount info pointer and then calls nfs_inactive() which references one of the fields in mount info structure causing a kernel data page fault panic. Resolution: The order of freeing the pointers looks obvisously wrong. The reason kernel does not crash every time mount timesout is the following: The answer is in kmem_free(), FREE() and how they work. After kmem_free() returns the memory we just freed ends up on a free list. So referencing it does not cause a page fault everytime we go through through nfs_inactive3(), after freeing mi.We page fault if that memory gets allocated to some other process and the data is no longer valid. 11. Enhanced NFS version 3 to support the full 32k read/write block size. Resolution: Enhanced NFS version 3 to support the full 32k read/write block size. PHNE_20091: 1. When automountd receives a request to mount the local filesystem (e.g., "/net/myhost" from host "myhost"), it does not use the lofs file system mount, but uses an nfs loopback mount Resolution: Remove conditionals which disabled use of LOFS filesystem. PHNE_20021: 1. Internal testing with cachefs controlled by autofs will get a 'data page fault' panic in <30min. Resolution: In autofs, added a concurrency check on node before using (vnode_t*)vp->v_vfsmountedhere. PHNE_19426: 1. This turned out to be a server problem where the NFS server dropped the client request. This caused the client to retry in a infinite loop, which is normal. The reason this occurred is because the server corrupted the cache data entry. Resolution: A fix has been made in the NFS server code to prevent duplicate cache table corruption. 2. The timeout table for NFS version 3 wasn't correct. This leads to client timing out too quickly. Resolution: The timeout's table has been fixed in the NFS kernel to match Sun's timeout implementation of NFS. 3. Specifying both O_EXCL and O_TRUNC at file creation time caused NFS client to pass 0 file size to the server who treats the file as an existing file and tries to verify the credential which failed. Resolution: A fix has been implemented to not allow 0 file size to pass to the server so it will not verify the credential of a newly created file. 4. mknod of a character device with -1 minor number will cause the NFS client to create a FIFO file. Resolution: A new error message "Operation not supported" will be returned when the user attempts to create a file with the properties described above. 5. Connectivity problem can occur when all dynamic port numbers are in use. Resolution: Return error when no port can be allocated. 6. The NFS kernel doesn't support block size of less than 1k even though the mount commands allows it. Resolution: The kernel mount routine has been changed to allow the use of less than 1k block size. 7. Loading executable file or running memory map applications over NFS will fail when NFS read/write block size is not set to 4k increment. Resolution: A check in the NFS mount code to ensure that the buffer page is allocated at 4k increment. 8. AutoFS is not triggering re-mount === Running AutoFS with very short node timeout (e.g. "automount -t0") can cause failures to access files which are present. Resolution: Adjust the logic used to detect special requests from the "automountd" daemon. Include tests to avoid race conditions between autofs_proc and file lookups. Set a minimum hold time for autonodes so that they are not recycled immediately after being created. 9. AutoFS hangs even with PHNE_17200 === AutoFS with a short node timeout with a script using manual umounts in a tight loop can hang autofs after 10-15 minutes. Resolution: Adjust the logic used to detect special requests from the "automountd" daemon. Include tests to avoid race conditions between autofs_proc and file lookups. Set a minimum hold time for autonodes so that they are not recycled immediately after being created. 10. cp(1) fails to inactive direct mount === When a command is given to copy a file to the top of an unmounted direct mount point, 'cp' fails with "Operation not supported". Resolution: Add a pathconf() handler for direct mounts. 11. mv command fails in AutoFS direct mnt == When the 'mv' command is used to rename a file from the current directory and it is a direct mount point, it will fail if the direct mount is not already active (mounted), with error ENOSYS. Resolution: Add direct mount handler to auto_access() and auto_rename(). With changes, 'cd' triggers mount. PHNE_19073: 1. When replicated (multiple) servers are in a map file, automountd chooses the first server in the list, not the quickest to respond. Resolution: Fix the discovery code in nfs_cast to select the quickest responding server as documented. 2. AutoFS under 10.20 ACE2 ignores any use of the "port" qualifier if it is specified in the map. Resolution: Correctly interpret "port" option in map. 3. The ServiceGuard configuration is NFS mounting from the relocatable IP address. This problem occurs when the relocatable IP is owned by the same system on which the physical disks reside. This causes a loopback NFS mount to occur to a different server name than what is configured as `hostname` resulting in locks not being removed when they should be. Resolution: The residual locks which remained in the rpc.lockd queues are now removed when appropriate. 4. Logging format is not consistant with the rest of the onc product. Resolution: Changed Logging format to conform to rest of onc product. PHNE_19072: 1.Enhanced nfsconf to support Networking Ace bundle. PHNE_18961: 1. Setting MOUNTD_VER to 2 will force HPUX server to start rpc.mountd servicing only version 2 of NFS. This is a special feature introduced in 10.20 for backward compatibility reason. According to NFS specification, a client should contact rpc.mountd on the server to see which is the highest version it supports before attempting to use that version. This wasn't the case for some Sun's clients. Sun's clients attempt to contact nfsd instead of rpc.mountd for service. This is a problem. Since HP's nfsd always servicing both versions and rpc.mountd only servicing version 2, some Sun's client get confuse. HP's client doesn't have this problem because it is smart enough to fall back to version 2 if 3 is not available. Resolution: Setting MOUNTD_VER to 2 will now force HPUX server to start both rpc.mountd and nfsd servicing only version 2 of NFS. This solved the confusion for some Sun's clients. 2. When using NFS file locking/unlocking heavily, the kernel RPC on the client system leaks memory in chunks of 32 byte. Resolution: The memory leak is due to not deallocating a spinlock structure associated with the RPC client handle when the client handle is freed. This has been fixed PHNE_18962: 1. Setting MOUNTD_VER to 2 will force HPUX server to start rpc.mountd servicing only version 2 of NFS. This is a special feature introduced in 10.20 for backward compatibility reason. According to NFS specification, a client should contact rpc.mountd on the server to see which is the highest version it supports before attempting to use that version. This wasn't the case for some Sun's clients. Sun's clients attempt to contact nfsd instead of rpc.mountd for service. This is a problem. Since HP's nfsd always servicing both versions and rpc.mountd only servicing version 2, some Sun's client get confuse. HP's client doesn't have this problem because it is smart enough to fall back to version 2 if 3 is not available. Resolution: Setting MOUNTD_VER to 2 will now force HPUX server to start both rpc.mountd and nfsd servicing only version 2 of NFS. This solved the confusion for some Sun's clients. 2. When using NFS file locking/unlocking heavily, the kernel RPC on the client system leaks memory in chunks of 32 byte. Resolution: The memory leak is due to not deallocating a spinlock structure associated with the RPC client handle when the client handle is freed. This has been fixed PHNE_18915: 1. Setting MOUNTD_VER to 2 will force HPUX server to start rpc.mountd servicing only version 2 of NFS. This is a special feature introduced in 10.20 for backward compatibility reason. According to NFS specification, a client should contact rpc.mountd on the server to see which is the highest version it supports before attempting to use that version. This wasn't the case for some Sun's clients. Sun's clients attempt to contact nfsd instead of rpc.mountd for service. This is a problem. Since HP's nfsd always servicing both versions and rpc.mountd only servicing version 2, some Sun's client get confuse. HP's client doesn't have this problem because it is smart enough to fall back to version 2 if 3 is not available. Resolution: 1. Setting MOUNTD_VER to 2 will now force HPUX server to start both rpc.mountd and nfsd servicing only version 2 of NFS. This solved the confusion for some Sun's clients. Also, the mountd.1m manpage has been modified to document MOUNTD_VER option. PHNE_17842: 1. On does not recognize Autofs mount types Resolution: on now recognizes Autofs mount points 2. Previous fix required that nis.server and nfsconf be installed as a pair. Resolution: Code changed to remove this dependency. 3. Automounter checks for mount directory to begin with a /. NT systems don't have this. Resolution: Remove requirement that the dir path begin with a /. 4. Rpc.mountd matches host names case sensitive. Resolution: Libc change to innetgr() (see Patch Dependancies) 5. Stdhosts read buffer has length of 256 char. Resolution: Buffer length increased to 1024. 6. Ypmake can build netgroup map keys in uppercase. Resolution: ypmake converts to lower case netgroup keys. 7. Makefile script can build netgroup map keys in uppercase. Resolution: Makefile script converts to lower case netgroup keys. 8. Ypserv does not free file descriptors if client does not exit properly. Resolution: ypserv closes the tcp channel to the client after it forks the child process. 9. An invalid mount point with replicated servers causes automount to loop. Resolution: code introduced to correct looping behavior. 10.A second call to gethostbyname by rpc.statd is corrupting the values to its first call to it. This causes rpc.statd to take too much time to do its work without responding to rpc.lockd. Resolution: The change is to copy the values from the first call to gethostbyname in rpc.statd so that they will not be corrupted by later calls to it. 11. rpc.lockd does not include the code to support the version 4 share and freeall functions. Resolution: The change is to include the share and freeall functions for lock manager version 4. 12. rpc.lockd does not clean up a reclaim request correctly when a non-granted response is received. Resolution: The change is to clean up the message queue entry for all responses to a reclaim request. 13. rpc.lockd does not retransmit messages in a first-in/ first-out manner. Resolution: The change is to now retransmit messages in the correct order. 14.rpc.lockd processes an unlock request incorrectly by leaving an entry in the message queue that has an invalid pointer. Resolution: The change is to better handle the deletion of entries in the message queue (where certain requests may apply to several entries in that queue) and to not send out multiple reclaim requests for the same lock. 15.The nfsconf script has been enhanced to support the new patch structure. See the Special Installation Instructions for more details Resolution: Added support for the new MOUNT_VER,MOUNTD_VER, and AUTOFS variables in /usr/newconfig/etc/rc.config.d/nfsconf. 16.The nfs client start up script has been enhanced to support the new patch structure. See the Special Installation Instructions for more details Resolution: Enhanced to support AutoFS and Automounter 17.The nfs mount demon has been enhanced to support the new patch structure. See the Special Installation Instructions for more details. Resolution: Added support for the new MOUNTD_VER variable in /etc/rc.config.d/nfsconf. 18.The nfs mount command has been enhanced to support the new patch structure. See the Special Installation Instructions for more details Resolution: Added support for the new MOUNT_VER variable in /etc/rc.config.d/nfsconf. 19.The automount command has been enhanced to support the new patch structure. See the Special Installation Instructions for more details. Resolution: The /usr/sbin/automount command is now a shell script. This was done to support the new patch structure. 20.The automount man page has been enhanced to support the new patch structure. See the Special Installation Instructions for more details. Resolution: The man page now contains description on how to setup Automounter or AutoFS using a configurable variable (AUTOFS) in /etc/rc.config.d/nfsconf 21.The autofs deamon has been enhanced to support the new patch structure. See the Special Installation Instructions for more details Resolution: The man page now contains description on how to setup Automounter or AutoFS using a configurable variable (AUTOFS) in /etc/rc.config.d/nfsconf 22.The nfs mount man page has been enhanced to support the new patch structure. See the Special Installation Instructions for more details Resolution: Added support for the new MOUNT_VER variable in /etc/rc.config.d/nfsconf. Also added support for 24k rsize and wsize PHNE_17619: 1. The problem is that there are conditions in which read credentials are not set. That means that any reads performed as part of a write operation will fail because there are no read credentials available for them to pass and all work done on the server is as root. 2. Remount logic causes hangs 3. Enhanced NFS version 3 to support up to 24k read/ write block size. 4. Tunned the code to perform better in small block synchronous write. 5. A NFS PV3 client is unable to copy large files greater than 2GB from a NFS mounted file system to the local file system. 6. NFS3ERR_JUKEBOX is not handled in 10.20 ACE PV3 code 7. Fixed system hang/sleep in clntkudp_callit() at outbuf and not waking up. Also added statistcial data collection for sleep and wakeup calls. 8. The code in nfs_remove checks if a file is busy and if it has been renamed. If the test is true then the file will be removed. This can cause a busy file that has not been renamed removed. The 2 conditions should be checked separately, i.e. first check if a file is busy, if it is, then check if it's been renamed? Do nothing if it is; otherwise, rename it. Only when a file is not busy then it will be removed. 9. the code path to purge the buffer caches of a stale file handle who has large amount of delayed write data could be too long and causes kernel stack overflow. 10. When a root user can not write to the file, the file attributes are changed including the file size. The code closing the file does not check if the user closing the file has write permission before it sets the file attribute using the new one thus causing the file size gets reset to zero. 11. The problem occurs due to avoiding the read of the block when multiple processes are appending data to the same file block when nfs_no_read_before_write is turned on. Due to NFS client avoiding the read of the file block and initializing the buffer to NULLs,NULLs are written out. 12. The cachefs read and write path is not releasing credential correctly. PHNE_17620: 1. The problem is that there are conditions in which read credentials are not set. That means that any reads performed as part of a write operation will fail because there are no read credentials available for them to pass and all work done on the server is as root. 2. Remount logic causes hangs 3. Enhanced NFS version 3 to support up to 24k read/ write block size. 4. Tunned the code to perform better in small block synchronous write. 5. A NFS PV3 client is unable to copy large files greater than 2GB from a NFS mounted file system to the local file system. 6. NFS3ERR_JUKEBOX is not handled in 10.20 ACE PV3 code 7. Fixed system hang/sleep in clntkudp_callit() at outbuf and not waking up. Also added statistcial data collection for sleep and wakeup calls. 8. The code in nfs_remove checks if a file is busy and if it has been renamed. If the test is true then the file will be removed. This can cause a busy file that has not been renamed removed. The 2 conditions should be checked separately, i.e. first check if a file is busy, if it is, then check if it's been renamed? Do nothing if it is; otherwise, rename it. Only when a file is not busy then it will be removed. 9. the code path to purge the buffer caches of a stale file handle who has large amount of delayed write data could be too long and causes kernel stack overflow. 10. When a root user can not write to the file, the file attributes are changed including the file size. The code closing the file does not check if the user closing the file has write permission before it sets the file attribute using the new one thus causing the file size gets reset to zero. 11. The problem occurs due to avoiding the read of the block when multiple processes are appending data to the same file block when nfs_no_read_before_write is turned on. Due to NFS client avoiding the read of the file block and initializing the buffer to NULLs,NULLs are written out. 12. The cachefs read and write path is not releasing credential correctly. PHNE_17098: 1. Installation of PHNE_17055 inadvertently over- writes the customer modifiable version of ypmake. PHNE_17055: 1. Postinstall script for PHNE_16117 included nfsd as an ace_only file when it was in fact a common file. Can result in nfsd program being deleted on clients. PHNE_16924: A buffer cache entry is being released more than once causing corruption in the buffer cache hash lists. NOTE: Patch PHNE_16924 installs a patch for the networking ACE 2 software bundle (PHNE_13833) only if that bundle has been installed on the system. Otherwise, patch PHNE_16924 installs a patch for the standard release and its patches (represented by PHNE_13823). PHNE_16925: A buffer cache entry is being released more than once causing corruption in the buffer cache hash lists. NOTE: Patch PHNE_16925 installs a patch for the networking ACE 2 software bundle (PHNE_13834) only if that bundle has been installed on the system. Otherwise, patch PHNE_16925 installs a patch for the standard release and its patches (represented by PHNE_13824). PHNE_16117: 1. mknetid mknetid cores when a user is in more that 20 groups. 2. rpc.yppasswdd If a password contains a ":", it cannot be changed via NIS. 3. ypbind ypbind file sometimes doesn't get created. 4. ypmake When "ypmake mapname with NOPUSH=1" is issued on the NIS master, transferring the newly made map by ypxfr on the NIS slave would fail sometimes. 5. ypxfrd ypxfrd times out due to libndbm performance problem. 6. automount Automounter removes entry for filesystem if server down. 7. automountd AutoFS will not unmount LOFS mounts AutoFS will not unmount CacheFS filesystems Duplicate entries in /etc/mnttab error message in syslog not removed. 8. nfs.client nfs.client script does not kill biod daemons. rpc.lockd does not reclaim locks after NFS server reboots. 9. rpc.lockd rpc.lockd behaves incorrectly in the NLM_CANCEL case. Loss of UDP NFS file locking packets results in a growing msg queue. 10. rpc.pcnfsd rpc.pcnfsd allowed any user to change permissions on the spool directory. 11. /sbin/fs/autofs/mount The unmount timeout for autonodes 10 minutes. 12. exportfs reads and writes will fail if clients hostname resolves to more than one IP address. PHNE_15863: 1. An access of a kernel variable on an NFS client was not protected by a spinlock and thus conflicted with other accesses of the same variable causing the integrity of that variable to be compromised and leading to a case where a sleep could not be woken up. 2. An interrupt performing an operation on a socket on which NFS is attempting a socket buffer data drop (sbdrop) causes the socket operation to access a bad socket buffer address. 3. A read of a file that was truncated during the read operation causes an access of non-existent data. 4. With no biods running, a write of a stale file in which the writes are less than 8K bytes in length causes a recursive call stack that can get very large. 5. Before reading the entries of a directory, no check is performed to determine if the entity being read is a directory, which leads to the given syslog message. 6. The file open credentials are used by NFS and not the thread credentials. This can lead to a quota problem when the user that opened a file is not the user accessing the file. 7. When a utime() operation with a NULL timestamp is performed on an NFS file/directory, the NFS client uses the system time of the client to set file/directory modification and access times with SETATTR operations. However, WRITE operations use the system time of the server to set file/directory modification and access times. This causes inconsistencies when the client and server systems are in different time zones. 8. A SUN NFS client attempting to perform a utime() operation with a NULL timestamp on an HP NFS server file/directory is rejected due to a permissions error even though the process has write permissions but is not the file/directory owner. 9. When hierarchical maps are used, a umount of the mount points causes the autofs daemon to hang (this applies only to systems that have the ACE 2 software bundle installed). 10. Running Netscape from automounter paths causes hangs (this applies only to systems that have the ACE 2 software bundle installed). 11. A slow memory leak in rfs_readdirplus3() eventually starves the server of free memory (this applies only to systems that have the ACE 2 software bundle installed). 12. The calls from cachefs to do attribute lookups hang when trying to make a cachefs node (this applies only to systems that have the ACE 2 software bundle installed). 13. The nm tool is given incorrect file length data and reports a standard HPPA error (this applies only to systems that have the ACE 2 software bundle installed). 14. The system panics with data page fault on the NFS PV3 server when trying to remove a symbolic link (this applies only to systems that have the ACE 2 software bundle installed). 15. An application can lseek to EOF and then read past EOF without having an error status returned (this applies only to systems that have the ACE 2 software bundle installed). 16. The maximum file size field in the NFS PV3 protocol has been initialized incorrectly (this applies only to systems that have the ACE 2 software bundle installed). NOTE: Patch PHNE_15863 installs a patch for the networking ACE 2 software bundle (PHNE_13833) only if that bundle has been installed on the system. Otherwise, patch PHNE_15863 installs a patch for the standard release and its patches (represented by PHNE_13823). PHNE_15864: 1. An access of a kernel variable on an NFS client was not protected by a spinlock and thus conflicted with other accesses of the same variable causing the integrity of that variable to be compromised and leading to a case where a sleep could not be woken up. 2. An interrupt performing an operation on a socket on which NFS is attempting a socket buffer data drop (sbdrop) causes the socket operation to access a bad socket buffer address. 3. A read of a file that was truncated during the read operation causes an access of non-existent data. 4. With no biods running, a write of a stale file in which the writes are less than 8K bytes in length causes a recursive call stack that can get very large. 5. Before reading the entries of a directory, no check is performed to determine if the entity being read is a directory, which leads to the given syslog message. 6. The file open credentials are used by NFS and not the thread credentials. This can lead to a quota problem when the user that opened a file is not the user accessing the file. 7. When a utime() operation with a NULL timestamp is performed on an NFS file/directory, the NFS client uses the system time of the client to set file/directory modification and access times with SETATTR operations. However, WRITE operations use the system time of the server to set file/directory modification and access times. This causes inconsistencies when the client and server systems are in different time zones. 8. A SUN NFS client attempting to perform a utime() operation with a NULL timestamp on an HP NFS server file/directory is rejected due to a permissions error even though the process has write permissions but is not the file/directory owner. 9. When hierarchical maps are used, a umount of the mount points causes the autofs daemon to hang (this applies only to systems that have the ACE 2 software bundle installed). 10. Running Netscape from automounter paths causes hangs (this applies only to systems that have the ACE 2 software bundle installed). 11. A slow memory leak in rfs_readdirplus3() eventually starves the server of free memory (this applies only to systems that have the ACE 2 software bundle installed). 12. The calls from cachefs to do attribute lookups hang when trying to make a cachefs node (this applies only to systems that have the ACE 2 software bundle installed). 13. The nm tool is given incorrect file length data and reports a standard HPPA error (this applies only to systems that have the ACE 2 software bundle installed). 14. The system panics with data page fault on the NFS PV3 server when trying to remove a symbolic link (this applies only to systems that have the ACE 2 software bundle installed). 15. An application can lseek to EOF and then read past EOF without having an error status returned (this applies only to systems that have the ACE 2 software bundle installed). 16. The maximum file size field in the NFS PV3 protocol has been initialized incorrectly (this applies only to systems that have the ACE 2 software bundle installed). NOTE: Patch PHNE_15864 installs a patch for the networking ACE 2 software bundle (PHNE_13834) only if that bundle has been installed on the system. Otherwise, patch PHNE_15864 installs a patch for the standard release and its patches (represented by PHNE_13824). PHNE_15541: 1. automountd automountd changed to mount local filesystems using LOFS instead of loopback nfs. 2. rpc.statd core dumps during string compare operation. 3. If the transition links are removed the scripts autofs and autofs_setup fail. 4. If the transition links are removed the scripts autofs and autofs_setup fail. 5. rpcinfo -p does not report that NFS PV3 is running. PHNE_15041: 1. NFS performance over 100BT is poor. 2. Autofs panics system with data page fault (this applies only to systems that have the ACE 2 software bundle installed). 3. Autofs fails to work with 9.X archived directory path libraries (this applies only to systems that have the ACE 2 software bundle installed). 4. Autofs causes swlist to fail (this applies only to systems that have the ACE 2 software bundle installed). NOTE: Patch PHNE_15041 installs a patch for the networking ACE 2 software bundle (PHNE_13833) only if that bundle has been installed on the system. Otherwise, patch PHNE_15041 installs a patch for the standard release and its patches (represented by PHNE_13823). PHNE_15042: 1. NFS performance over 100BT is poor. 2. Autofs panics system with data page fault (this applies only to systems that have the ACE 2 software bundle installed). 3. Autofs fails to work with 9.X archived directory path libraries (this applies only to systems that have the ACE 2 software bundle installed). 4. Autofs causes swlist to fail (this applies only to systems that have the ACE 2 software bundle installed). NOTE: Patch PHNE_15042 installs a patch for the networking ACE 2 software bundle (PHNE_13834) only if that bundle has been installed on the system. Otherwise, patch PHNE_15042 installs a patch for the standard release and its patches (represented by PHNE_13824). PHNE_14071: 1. An uninitialized kernel variable on an NFS server causes an address to be decremented by one and thus leaves it not pointing to a word-aligned area. 2. An access of a kernel variable on an NFS client was not protected by a spinlock and thus conflicted with other accesses of the same variable causing the integrity of that variable to be compromised and leading to a case where a loop cannot be terminated. 3. A lack of synchronization within the RPC kernel layer causes an access of a kernel variable after its memory has already been freed. 4. The NFS server allows access of a previously released vnode when a file lock is unblocked. NOTE: Patch PHNE_14071 installs a patch for the networking ACE 2 software bundle (PHNE_13833) only if that bundle has been installed on the system. Otherwise, patch PHNE_14071 installs a patch for the standard release and its patches (represented by PHNE_13823). PHNE_14072: 1. An uninitialized kernel variable on an NFS server causes an address to be decremented by one and thus leaves it not pointing to a word-aligned area. 2. An access of a kernel variable on an NFS client was not protected by a spinlock and thus conflicted with other accesses of the same variable causing the integrity of that variable to be compromised and leading to a case where a loop cannot be terminated. 3. A lack of synchronization within the RPC kernel layer causes an access of a kernel variable after its memory has already been freed. 4. The NFS server allows access of a previously released vnode when a file lock is unblocked. NOTE: Patch PHNE_14072 installs a patch for the networking ACE 2 software bundle (PHNE_13834) only if that bundle has been installed on the system. Otherwise, patch PHNE_14072 installs a patch for the standard release and its patches (represented by PHNE_13824). PHNE_13833: New functionality to support networking features in 10.20. PHNE_13834: New functionality to support networking features in 10.20. PHNE_13823: 1. Processes within the RPC kernel layer are not releasing a lock which is needed by other NFS client processes to synchronize IO requests (which requires a flush of all outstanding client to server IO). 2. A spinlock is held by a kernel RPC process when it tries to acquire a beta semaphore. PHNE_13824: 1. Processes within the RPC kernel layer are not releasing a lock which is needed by other NFS client processes to synchronize IO requests (which requires a flush of all outstanding client to server IO). 2. A spinlock is held by a kernel RPC process when it tries to acquire a beta semaphore. PHNE_13731: 1. ypserv The amount of timeout given to the async service could be negative on a slow system which caused select() to function unexpectedly. Data gets lost but async service does not know since select() did not give the correct answer. ypserv finds the query has already been posted, so it decides not to query again. 2. rpc.pcnfsd rpc.pcnfsd does not allow logins with trusted systems. rpc.pcnfsd was enhanced to spawn a process to do lpstat -v. 3. namesvrs-nis.server The HP box has several maps which are non-existent on the IBM machines. This causes the nis.server script to fail as the maps are hard coded into the script. This is encountered when the slave server starts. 4. rpc.statd Problem is in the rpc.statd code which has an incorrect test for gethostbyname() causing problems in returning the correct parameter. 5. netgroup.4 Modified man page to make domain meaning clearer 6. ypclnt.3c Modified ypclnt man page to be more clear about free(). 7. pcnfsd.1m Man page updated to reflect changes in rpc.pcnfsd 8. yppasswdd.1m manpage references /var/adm/ptmp instead of /etc/ptmp. 9. Modified listen que to be 20 instead of 2. User must install dependent libc patch PHCO_13777 to take advantage of this fix. 10. Modified xdr routine to stop memory leak causing portmap to refuse to answer requests. Fix is in PHCO_13777 libc patch. PHNE_13835: New functionality to support networking features in 10.20 PHNE_13668: The NFS client prevents root from opening a file on the server. It will allow file creation, but not IO to an existing file. PHNE_13669: The NFS client prevents root from opening a file on the server. It will allow file creation, but not IO to an existing file. PHNE_13235: 1. NFS Clients may send serial IO requests out of order, causing performance problems for JFS on the Server. 2. NFS writes to a full disk used as a swap device will return an error which results in a call to panic() from nfs_prealloc(). 3. When retransmitting, the XID may not be properly reinitialized, allowing data corruption in the form of null-valued blocks of 8192 bytes (or less). PHNE_13236: 1. NFS Clients may send serial IO requests out of order, causing performance problems for JFS on the Server. 2. NFS writes to a full disk used as a swap device will return an error which results in a call to panic() from nfs_prealloc(). 3. When retransmitting, the XID may not be properly reinitialized, allowing data corruption in the form of null-valued blocks of 8192 bytes (or less). PHNE_12427: The reference count of the exported entry is not managed correctly, and may remain greater than 0 when unused. PHNE_12428: The reference count of the exported entry is not managed correctly, and may remain greater than 0 when unused. PHNE_11386: Hang in clnt_kudp.o PHNE_11387: Hang in clnt_kudp.o PHNE_11008: 1. Error codes kept in the rnode for an NFS client's file may get overwritten, and therefore not reported back to the caller when the file is closed. 2. The NFS server renaming procedures do not check for differing VxFS file systems when asking for a rename, which will cause a panic down in VxFS. 3. The server authorization program does not properly check for anonymous access when user IDs of -2 are used. 4. The netisr callout function did not protect against a race condition. null-valued blocks of 8192 bytes (or less). 5. The system does not initialize the vnode attributes when it sees a file size which is too large for the 10.20 file system, and returns an error. The server is making the directory anyway, with uninitialized (000) attributes. PHNE_11009: 1. Error codes kept in the rnode for an NFS client's file may get overwritten, and therefore not reported back to the caller when the file is closed. 2. The NFS server renaming procedures do not check for differing VxFS file systems when asking for a rename, which will cause a panic down in VxFS. 3. The server authorization program does not properly check for anonymous access when user IDs of -2 are used. 4. The netisr callout function did not protect against a race condition. PHNE_10894: 1. Enhancement to rpc.lockd to fix problem of forwarding unlocks to kernel contained a bug that caused rpc.lockd to send incorrect unlock range to the kernel. Applications failed with unexpected results due to this problem. 2. Rpc.mountd does not handle requests from an IBM machine. 3. The man page for pcnfsd does not list the entry for /etc/shells 4. Automount does not correctly support the "nodevs" mount option. 5. Rpc.rquotad has memory leak. PHNE_10515: 1. rpc.lockd forwards unlock to kernel when no match exists in queue 2. Rcp.yppasswdd doesn't handle unsupported functions properly. PHNE_9864: The system does not initialize the vnode attributes when it sees a file size which is too large for the 10.20 file system, and returns an error. The server is making the directory anyway, with uninitialized (000) attributes. PHNE_9465: 1. Exports file allows comments which are causing exportfs to parse as hotnames. 2. Get_myaddress man page has wrong information 3. Exportfs man page does not reflect uid changes to user nobody and anonymous access. if ypxfrd is not available. 5. Rpc.pcnfsd has problem with wlogin() when the server cannot resolve the client hostname. PHKL_9155: 1. NFS write performance can be improved by doing gather writes at the server. This patch implements the NFS portion of gather writes. 2. The maximum timeout values defined in RPC were very long, and neither RPC nor NFS values matched that of SUN. PHKL_9156: 1. NFS write performance can be improved by doing gather writes at the server. This patch implements the NFS portion of gather writes. 2. The maximum timeout values defined in RPC were very long, and neither RPC nor NFS values matched that of SUN. PHKL_8544: 1. The kernel's biod support code did not sufficently protect against MP race conditions. 2. The RPC processor affinity implementation used by nfsd's was not sufficently protected against MP race conditions. 3. Incorrect usage of the dnlc purge functions. PHKL_8545: 1. The kernel's biod support code did not sufficently protect against MP race conditions. 2. The RPC processor affinity implementation used by nfsd's was not sufficently protected against MP race conditions. 3. Incorrect usage of the dnlc purge functions. PHNE_8310: 1. Get_myaddress routine in ypwhich fails if X.25 is the only interface configured. 2. Enhancement request to log authentication info to wtmp file. 3. Makedbm wouldn't run on certain S800's due to compilation error. 4. rpc.rquotad doesn't do JFS systems. 5. rpc.mountd default was to run from non-privileged ports. 6. rpc.yppasswdd daemon would return errors if temp file was on separate partition from root rile. PHCO_9543: The problem is caused by a bug in /sbin/fs/nfs/umount. If a file system is mounted on over NFS, and the file system goes away for some reason, the file system will be reported as Stale, and there is no way to get rid of this without a reboot. To recreate the problem, make a directory on system A and export it. On system B (must be 10.20), mount the file system. Remove the directory on system A. Do a bdf on system B, and it should report "Stale NFS file handler" for the mounted file system. Doing a umount of the file system also reports this error, and the umount is not done. Even if the directory is recreated on system A, and exported, it cannot be umounted. The system would have to be rebooted. SR: 1653254474 1653256891 1653262436 1653272484 4701373233 4701379610 5003410472 5003416842 5003417998 5003426247 5003428847 5003431353 5003432111 5003432757 5003434654 4701379610 5003393884 1653215806 5003401034 5003371922 5003405118 5003336198 1653235291 1653218305 1653207654 5003373092 5003332296 5003373092 5003287649 5003323980 1653155622 1653153593 5003306993 1653146357 4701314765 5003283846 5003273565 5003282038 5003291245 1653154476 5003299255 5003293001 5003290833 5003301564 4701314765 1653159087 1653183277 5003335984 5003349878 5003355784 4701378117 4701392027 1653263020 5003414185 5003444588 5003420992 5003438572 5003407569 1653289660 5003450916 5003442434 1653283903 5003445486 5003441311 1653308254 5003459230 5003462127 5003446005 8606103364 8606106665 8606107366 8606105010 8606107068 5003459362 8606113678 8606125714 8606125899 8606126845 1653307181 8606106959 8606124938 5003460030 8606139829 8606128188 8606132942 8606104308 8606152534 8606124644 8606131496 1653270413 8606134248 8606131366 8606136063 8606134296 8606142896 8606145476 4701419580 4701415216 8606106630 5003445601 1653280412 5003433078 5003429753 5003428292 5003427963 5003425116 5003423590 5003423368 5003423111 5003419325 5003418962 5003417329 5003417071 5003406660 5003404616 5003402743 5003402677 5003398826 5003394056 5003368050 5003352534 5003344226 5003343277 5003340042 5003330894 5003327338 5003326090 5003324657 5003322370 5003321513 5003319665 5003319145 5003279927 5003279091 4701408047 4701400903 4701378117 4701351577 4701341669 4701314302 4701306837 4701306829 1653275800 1653272385 1653266577 1653249268 1653197632 1653192294 1653150599 1653146886 1653146308 1653134924 1653101337 1653281691 5003456574 1653275974 1653299602 5003456897 1653308254 5003467373 1653298828 5003458299 1653299826 5003462911 8606139585 8606140818 8606138879 1653275800 8606135856 8606159736 8606144704 4701408088 4701415216 4701423491 5003463455 5003467860 8606103830 8606106938 8606111693 8606111695 8606111990 8606112316 8606112426 8606125859 8606126038 8606127069 8606127184 8606130075 8606131940 8606132171 8606180865 8606197432 8606176017 8606193515 8606167148 Patch Files: /usr/conf/lib/libnfs.a /usr/conf/lib/libhp-ux.a(cachefs.o) /usr/conf/lib/libhp-ux.a(nfs.o) /usr/conf/lib/libhp-ux.a(nfs_iface.o) /usr/conf/lib/onc_debug.o /usr/conf/master.d/nfs /usr/sbin/automount /usr/sbin/rpc.statd /usr/sbin/exportfs /usr/sbin/ypxfr /usr/sbin/ypxfrd /usr/sbin/mknetid /usr/lib/netsvc/yp/ypserv /usr/bin/on /usr/lib/netsvc/yp/ypbind /usr/lib/netsvc/yp/rpc.yppasswdd /usr/sbin/rpc.rexd /usr/sbin/rpc.rquotad /usr/sbin/rpc.pcnfsd /usr/sbin/makedbm /usr/sbin/stdhosts /usr/bin/ypwhich /sbin/init.d/nis.server /usr/newconfig/var/yp/Makefile /usr/newconfig/namesvrs /usr/newconfig/var/yp/ypmake /usr/share/man/man1m.Z/exportfs.1m /usr/share/man/man1m.Z/pcnfsd.1m /usr/share/man/man4.Z/exports.4 /usr/share/man/man3.Z/secure_rpc.3c /usr/share/man/man3.Z/ypclnt.3c /usr/share/man/man1m.Z/yppasswdd.1m /usr/share/man/man4.Z/netgroup.4 /usr/share/man/man1m.Z/ypmake.1m /sbin/fs/nfs/mount /sbin/fs/nfs/umount /sbin/fs/cachefs/fsck /sbin/fs/cachefs/mount /sbin/fs/cachefs/umount /sbin/fs/autofs/mount /sbin/fs/autofs/umount /usr/sbin/onccompat /usr/sbin/cfsadmin /usr/sbin/cachefsstat /sbin/lib/mfsconfig.d/cachefs /usr/bin/nfsstat /usr/sbin/rpc.lockd /usr/sbin/rpc.mountd /sbin/init.d/nfs.client /sbin/init.d/autofs /sbin/init.d/autofs_setup /usr/lib/netsvc/fs/autofs/automount /usr/lib/netsvc/fs/automount/automount /usr/sbin/automountd /usr/sbin/nfsd /usr/share/man/man1m.Z/mount_nfs.1m /usr/share/man/man1m.Z/cfsadmin.1m /usr/share/man/man1m.Z/fsck_cachefs.1m /usr/share/man/man1m.Z/mount_cachefs.1m /usr/share/man/man1m.Z/cachefsstat.1m /usr/share/man/man1m.Z/automount.1m /usr/share/man/man1m.Z/automountd.1m /usr/share/man/man1m.Z/onccompat.1m /usr/newconfig/etc/rc.config.d/nfsconf /usr/share/man/man1m.Z/mountd.1m /usr/lib/netsvc/rstat/rpc.rstatd /usr/lib/netsvc/rusers/rpc.rusersd /usr/lib/netsvc/rwall/rpc.rwalld /usr/lib/netsvc/spray/rpc.sprayd what(1) Output: /usr/conf/lib/libnfs.a: svc_kudp.c $Date: 99/12/07 17:43:14 $ $Revision: 1.7 .112.5 $ PATCH_10.20 PHNE_20313 700/800 svc.c $Date: 98/11/13 13:37:28 $ $Revision: 1.8.112 .16 $ PATCH_10.20 PHNE_16924 kudp_fsend.c $Date: 99/08/13 15:42:23 $ $Revision: 1.4.112.3 $ PATCH_10.20 PHNE_19426 700/800 clnt_kudp.c $Date: 00/02/10 15:30:16 $ $Revision: 1 .9.112.30 $ PATCH_10.20 PHNE_20313 700/800 hpautofs.c $Date: 99/11/18 15:08:46 $ $Revision: 1. 1.112.4 $ PATCH_10.20 PHNE_20313 700/800 auto_subr.c $Date: 2001/06/07 13:38:57 $ $Revision: 1.1.112.12 $ PATCH_10.20 PHNE_24143 700/800 auto_vnops.c $Date: 2001/06/07 13:40:31 $ $Revision : 1.1.112.11 $ PATCH_10.20 PHNE_24143 700/80 0 auto_vfsops.c $Date: 00/12/15 15:41:06 $ $Revision: 1.1.112.3 $ PATCH_10.20 PHNE_22877 700/800 cachefs_vnops.c $Date: 00/06/07 16:10:58 $ $Revisio n: 1.1.112.9 $ PATCH_10.20 PHNE_21704 700/8 00 cachefs_vfsops.c $Date: 99/12/06 13:52:33 $ $Revisi on: 1.1.112.4 $ PATCH_10.20 PHNE _20313 700/ 800 cachefs_module.c $Date: 99/12/06 13:49:30 $ $Revisi on: 1.1.112.4 $ PATCH_10.20 PHNE _20313 700/ 800 cachefs_cnode.c $Date: 99/12/06 13:44:21 $ $Revisio n: 1.1.112.5 $ PATCH_10.20 PHNE_20313 700/80 0 hpnfs_vnops.c $Date: 00/03/16 19:35:42 $ $Revision: 1.1.112.30 $ PATCH_10.20 PHNE_21108 700/800 nfs_vfsops3.c $Date: 00/01/07 16:41:29 $ $Revision: 1.1.112.11 $ PATCH_10.20 PHNE_20313 700/800 nfs_vnops3.c $Date: 01/02/16 14:02:20 $ $Revision: 1.1.112.29 $ PATCH_10.20 PHNE_22877 700/800 nfs_subr3.c $Date: 01/01/03 12:00:45 $ $Revision: 1 .1.112.15 $ PATCH_10.20 PHNE_22877 700/800 nfs_server3.c $Date: 00/12/20 16:11:00 $ $Revision: 1.1.112.11 $ PATCH_10.20 PHNE_22877 700/800 nfs_export3.c $Date: 00/01/04 13:58:42 $ $Revision: 1.1.112.2 $ PATCH_10.20 PHNE_20313 700/800 klm_lckmgr.c $Revision: 1.5.112.3 $ klm_kprot.c $Revision: 1.1.112.2 $ nfs_vfsops.c $Date: 00/01/07 16:45:56 $ $Revision: 1.1.112.9 $ PATCH_10.2 0 PHNE_20313 700/800 nfs_vnops.c $Date: 01/02/16 13:59:27 $ $Revision: 1 .3.112.68 $ PATCH_10.20 PHNE_22877 700/800 nfs_subr.c $Date: 00/12/20 16:02:24 $ $Revision: 1. 1.112.33 $ PATCH_10.20 PHNE_22877 nfs_server.c $Date: 99/08/13 15:41:02 $ $Revision: 1.3.112.33 $ PATCH_10.20 PHNE_19426 700/800 nfs_fcntl.c $Revision: 1.1.112.18 $ /usr/conf/lib/libhp-ux.a(cachefs.o): None /usr/conf/lib/libhp-ux.a(nfs.o): None /usr/conf/lib/onc_debug.o: None /usr/conf/lib/libhp-ux.a(nfs_iface.o): None /usr/conf/master.d/nfs: $Revision: 1.2.113.3 $ /usr/share/man/man1m.Z/exportfs.1m: None /usr/share/man/man1m.Z/pcnfsd.1m: None /usr/share/man/man4.Z/exports.4: None /usr/share/man/man3.Z/secure_rpc.3c: None /usr/share/man/man1m.Z/ypmake.1m: None /usr/share/man/man3.Z/ypclnt.3c: None /usr/share/man/man1m.Z/yppasswdd.1m: None /usr/share/man/man4.Z/netgroup.4: None /usr/newconfig/namesvrs: None /sbin/init.d/nis.server: None /usr/newconfig/var/yp/Makefile: make.script PHNE_20628 /usr/sbin/stdhosts: stdhosts: PHNE_17842 /usr/sbin/automount: automount $Revision: 1.1.114.1 $ $Date: 99/03/09 14: 52:50 $ /usr/sbin/rpc.statd: sm_svc.c: PHNE_22288 $Revision: 1.19.114.14 $ $Date: 2000/11/07 17:39:53 $ sm_proc.c : $Revision: 1.11.114.8 $ $Date: 99/07/27 09:09:17 $ PHNE_19073 sm_statd.c: $Revision: 1.21.114.5 $ $Date: 2000/11/0 8 11:57:41 $ PHNE_22288 udp.c: PHNE_20628 $Revision: 1.1.114.5 $ $Date: 200 0/01/24 15:41:01 $ logging.c PHNE_22288 $Date: 2000/11/28 16:31:37 $ $R evision: 1.26.114.5 $ /usr/sbin/exportfs: PHNE_16117 10.20 exportfs.c: $Revision: 1.3.114 .3 $ $Date: 96/01/16 12:49:22 $ issubdir.c 1.2 90/07/23 4.1NFSSRC Copyr 1990 Su n Micro /usr/sbin/ypxfr: PHNE_9465 ypxfr: $Revision: 1.46.114.3 $ $Dat e: 96/12/09 14:47:1 8 $ /usr/sbin/ypxfrd: ypxfrd_subr.c(PHNE_16117) 1.3 92/06/05 4.1NFSSRC Co pyr 1990 Sun Micro ypserv_net_secure.c 1.2 92/06/05 4.1NFSSRC Copyr 1990 Sun Micro /usr/sbin/mknetid: mknetid.c(PHNE_16117) 1.2 90/07/23 4.1NFSSRC Copyr 1990 Sun Micro getname.c 1.3 90/07/24 4.1NFSSRC Copyr 1990 Su n Micro /usr/lib/netsvc/yp/ypbind: ypbind.c(PHNE_16117) 1.8 92/04/20 4.1NFSSRC logging.c PHNE_22288 $Date: 2000/11/28 16:31:37 $ $R evision: 1.26.114.5 $ /usr/newconfig/var/yp/ypmake: ypmake:(PHNE_20628)$Revision: 1.47.114.8 $ $Dat e: 2000/01/11 14:49:46 $ /usr/lib/netsvc/yp/ypserv: ypserv.c 1.4 92/06/05 4.1NFSSRC Copyr 1990 Su n Micro ypserv_ancil.c 1.4 90/07/23 4.1NFSSRC Copyr 1990 Su n Micro ypserv_map.c 1.3 92/06/05 4.1NFSSRC Copyr 1990 Su n Micro ypsrv_proc.c: PHNE_22288 $Revision 1.28.114.7 $ $Dat e: 2000/11/10 17:09:48 $ logging.c PHNE_22288 $Date: 2000/11/28 16:31:37 $ $R evision: 1.26.114.5 $ yp_cache.c: $Revision: 1.3.114.1 $ $Date: 95/10 /02 18:23:56 $ ypserv_dbmtrak.c 1.1 90/07/24 4.1NFSSRC Copyr 1990 SMI ypserv_net_secure.c 1.2 92/06/05 4.1NFSSRC Copyr 1990 Sun Micro ngethostbyname.c 1.2 92/04/08 4.1NFSSRC svc_run_as.c PHNE_22288 $Revision 1.2.114.4 $ $Date: 2000/11/10 17:15:36 $ rpc_as.c(PHNE_13731) 1.1 90/07/23 4.1NFSSRC Copyr ight 1989 Sun Micro /usr/lib/netsvc/yp/rpc.yppasswdd: PHNE_16117 10.2 rpc.yppasswdd: $Revision: 1.50.114. 5 $ $Date: 98/08/18 14:08:22 $ logging.c PHNE_22288 $Date: 2000/11/28 16:31:37 $ $R evision: 1.26.114.5 $ /usr/sbin/rpc.rexd: rexd.c 1.5 92/04/20 4.1NFSSRC Copyr 1990 Sun Micro logging.c PHNE_22288 $Date: 2000/11/28 16:31:37 $ $R evision: 1.26.114.5 $ publickey.c 1.3 90/07/19 4.1NFSSRC Copyr 1990 Su n Micro /usr/bin/on: on.c:PHNE_17842 $Revision: 1.28.114.2 $ $Date: 99/03 /08 11:19:34 $ publickey.c 1.3 90/07/19 4.1NFSSRC Copyr 1990 Su n Micro /usr/sbin/rpc.rquotad: PHNE_10894 rpc.rquotad $Revision: 1.9.114.6 $ logging.c PHNE_22288 $Date: 2000/11/28 16:31:37 $ $R evision: 1.26.114.5 $ /usr/sbin/rpc.pcnfsd: rpc.pcnfsd: PHNE_20628 $Revision: 1.3.114.13 $ $Date : 2000/03/15 10:55:06 $ pcnfsd_v2.c 1.6 - rpc.pcnfsd V2.0 (c) 1991 Sun Techn ology Enterprises, Inc. pcnfsd_misc.c: PHNE_20628 $Revision: 1.2.114.10 $ $D ate: 2000/03/15 09:30:17 $ pcnfsd_print.c: PHNE_20628 $Revision: 1.3.114.11 $ $ Date: 2000/03/15 10:53:20 $ /usr/sbin/makedbm: PHNE_8310 10.2 makedbm: $Revision: 1.35.114.2 $ $Dat e: 95/11/20 17:14:58 $ /usr/bin/ypwhich: PHNE_8310 10.20 ypwhich: $Revision: 1.37.114. 1 $ $Date: 95/10/02 18:18:11 $ /sbin/fs/nfs/mount: mount PHNE_22288 $Date: 2000/11/28 16:01:54 $ $Revis ion: 1.1.114.12 $ PATCH-PHCO_22448 for 10.20; for 10.30, 11.x compatib ility libc.a_ID@@ /main/r10dav/libc_dav/libc_dav_cpe//1 /ux/core/libs/libc/archive_pa1/libc.a_ID Sep 28 2000 14:12:52 /sbin/fs/nfs/umount: $Revision: 78.6 $ PATCH/10.20:PHCO_8764 libc.a_ID@@/main/r10dav/libc_d av/libc_dav_cpe/2 /ux/libc/libs/libc/archive_pa1/libc.a_ID Oct 2 1996 10:35:25 PATCH_10_20: /opt/langtools/lib/crt0.o umount.o 96/1 2/12 /sbin/fs/cachefs/fsck: HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R evision: 74.03 $ fsck: PHNE_13835 $Revision: 1.1.114.7 $ $Date : 98/02/09 15:40:51 $ /sbin/fs/cachefs/mount: HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R evision: 74.03 $ mount: PHNE_13835 $Revision: 1.1.114.7 $ $Date : 98/02/18 09:38:10 $ /sbin/fs/cachefs/umount: HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R evision: 74.03 $ umount: PHNE_13835 $Revision: 1.1.114.4 $ $Date : 98/02/09 15:41:09 $ /sbin/fs/autofs/mount: mount: PHNE_16117 $Revision: 1.1.114.5 $ $Date : 98/08/25 10:37:07 $ /sbin/fs/autofs/umount: umount: PHNE_13835 $Revision: 1.1.114.2 $ /usr/sbin/onccompat: onccompat: PHNE_13835 $Revision: 1.1.114.7 $ $Date : 98/02/09 15:40:51 $ /usr/sbin/cfsadmin: HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R evision: 74.03 $ cfsadmin: PHNE_20628 $Revision: 1.1.114.6 $ $Date : 98/02/09 15:40:05 $ /usr/sbin/cachefsstat: HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R evision: 74.03 $ cachefsstat: PHNE_13835 $Revision: 1.1.114.2 $ $Date : 98/02/09 15:40:26 $ /sbin/lib/mfsconfig.d/cachefs: $Revision: 78.3 $ /usr/bin/nfsstat: PHNE_13835 $Revision: 1.1.114.4 $ $Date: 98/02/ 05 10:58:53 $ /usr/sbin/rpc.lockd: prot_main.c: PHNE_20628 $Revision: 1.1.114.16 $ $Da te: 2000/01/24 15:40:07 $ prot_lock.c: PHNE_22288 $Revision: 1.1.114.18 $ $Da te: 2000/12/12 14:06:03 $ prot_alloc.c: PHNE_20628 $Revision: 1.1.114.4 $ $D ate: 2000/01/24 15:35:12 $ prot_priv.c: PHNE_22288 $Revision: 1.1.114.3 $ $Dat e: 2000/12/12 14:10:05 $ prot_share.c: PHNE_22288 $Revision: 1.1.114.6 $ $Da te: 2000/12/04 15:05:34 $ udp.c: PHNE_20628 $Revision: 1.1.114.5 $ $Date: 200 0/01/24 15:41:01 $ sm_monitor.c: PHNE_22288 $Revision 1.1.114.4 $ $Dat e: 2000/11/10 17:01:25 $ prot_libr.c: PHNE_20628 $Revision: 1.1.114.7 $ $Dat e: 2000/01/24 15:36:15 $ /usr/sbin/rpc.mountd: rpc.mountd.c: PHNE_24143 $Revision: 1.1.114.15 $ $Da te: 2001/06/06 12:19:29 $ issubdir.c 1.2 90/07/23 4.1NFSSRC Copyr 1990 Su n Micro logging.c PHNE_22288 $Date: 2000/11/28 16:31:37 $ $R evision: 1.26.114.5 $ /sbin/init.d/nfs.client: nfs.client $Revision: 1.2.114.5 $ $Date: 99/03/09 11 :24:41 $ /sbin/init.d/autofs: autofs: PHNE_15541 $Revision:1 /sbin/init.d/autofs_setup: None /usr/lib/netsvc/fs/autofs/automount: automount: 10.20 PHNE_22288 $Revision: 1.1.114.11 $ $Date: 2000/11/22 09:48:44 $ ns_generic.c: PHNE_22288 $Revision: 1.1.114.4 $ $Da te: 2000/11/22 11:03:54 $ ns_files.c: PHNE_20628 $Revision: 1.1.114.3 $ $Date : 2000/01/25 17:12:48 $ auto_mnttab.c: PHNE_20628 $Revision: 1.1.114.5 $ $D ate: 2000/02/02 13:56:23 $ /usr/lib/netsvc/fs/automount/automount: automount: PHNE_17842 $Revision: 1.11.114.10 $ $Date: 99/03/08 09:54:51 $ /usr/sbin/automountd: automountd: 10.20 PHNE_24143 $Revision: 1.1.114.16 $ $Date: 2001/06/06 12:26:49 $ autod_mount.c: PHNE_22288 $Revision: 1.1.114.12 $ $ Date: 2000/11/21 16:33:45 $ autod_nfs.c: PHNE_24143 $Revision: 1.1.114.19 $ $Da te: 2001/06/06 12:29:57 $ nfs_cast.c: PHNE_22288 $Revision: 1.1.114.10 $ $Dat e: 2000/11/22 10:47:07 $ ns_generic.c: PHNE_22288 $Revision: 1.1.114.4 $ $Da te: 2000/11/22 11:03:54 $ ns_files.c: PHNE_20628 $Revision: 1.1.114.3 $ $Date : 2000/01/25 17:12:48 $ auto_mnttab.c: PHNE_20628 $Revision: 1.1.114.5 $ $D ate: 2000/02/02 13:56:23 $ /usr/sbin/nfsd: nfsd: PHNE_18915 $Revision: 1.39.114.3 $Date: 98/05/ 21 01:20:17 $ /usr/share/man/man1m.Z/mount_nfs.1m: None /usr/share/man/man1m.Z/cfsadmin.1m: None /usr/share/man/man1m.Z/fsck_cachefs.1m: None /usr/share/man/man1m.Z/mount_cachefs.1m: None /usr/share/man/man1m.Z/cachefsstat.1m: None /usr/share/man/man1m.Z/automount.1m: None /usr/share/man/man1m.Z/automountd.1m: None /usr/share/man/man1m.Z/onccompat.1m: None /usr/newconfig/etc/rc.config.d/nfsconf: None /usr/share/man/man1m.Z/mountd.1m: None /usr/lib/netsvc/rstat/rpc.rstatd: rpc.rstatd.c 1.2 90/07/23 4.1NFSSRC Copyr 1990 Su n Micro logging.c PHNE_22288 $Date: 2000/11/28 16:31:37 $ $R evision: 1.26.114.5 $ rstatxdr.c 1.3 90/07/19 4.1NFSSRC Copyr 1990 Su n Micro /usr/lib/netsvc/rusers/rpc.rusersd: rpc.rusersd: $Revision: 1.35.114.1 $ $Date: 95/10 /02 18:19:01 $ logging.c PHNE_22288 $Date: 2000/11/28 16:31:37 $ $R evision: 1.26.114.5 $ rusersxdr.c 1.3 90/07/19 4.1NFSSRC Copyr 1990 Su n Micro /usr/lib/netsvc/rwall/rpc.rwalld: rpc.rwalld: $Revision: 1.30.114.1 $ $Date: 95/10 /02 18:19:03 $ logging.c PHNE_22288 $Date: 2000/11/28 16:31:37 $ $R evision: 1.26.114.5 $ /usr/lib/netsvc/spray/rpc.sprayd: rpc.sprayd: $Revision: 1.30.114.1 $ $Date: 95/10 /02 18:19:05 $ logging.c PHNE_22288 $Date: 2000/11/28 16:31:37 $ $R evision: 1.26.114.5 $ rstatxdr.c 1.3 90/07/19 4.1NFSSRC Copyr 1990 Su n Micro cksum(1) Output: 1156907548 648054 /usr/conf/lib/libnfs.a 566132716 191044 /usr/conf/lib/libhp-ux.a(cachefs.o) 3631930508 166548 /usr/conf/lib/libhp-ux.a(nfs.o) 3472542863 2012 /usr/conf/lib/libhp-ux.a(nfs_iface.o) 566132716 191044 /usr/conf/lib/onc_debug.o 1421096347 4241 /usr/conf/master.d/nfs 3426355003 499 /usr/sbin/automount 2774025204 53248 /usr/sbin/rpc.statd 2593520237 24576 /usr/sbin/exportfs 445794593 20480 /usr/sbin/mknetid 2402986248 20480 /usr/sbin/ypxfrd 908072788 17926 /usr/newconfig/var/yp/ypmake 699102934 32768 /usr/lib/netsvc/yp/ypbind 821998992 49152 /usr/sbin/ypxfr 271723303 77824 /usr/lib/netsvc/yp/ypserv 1573929190 28672 /usr/lib/netsvc/yp/rpc.yppasswdd 1075462856 69632 /usr/sbin/rpc.rexd 351027535 65536 /usr/bin/on 63392607 20480 /usr/sbin/rpc.rquotad 2373382730 53248 /usr/sbin/rpc.pcnfsd 676784799 20480 /usr/sbin/makedbm 4221851490 20480 /usr/bin/ypwhich 341089473 12609 /sbin/init.d/nis.server 2336576382 4038 /usr/newconfig/namesvrs 4245156863 3425 /usr/share/man/man1m.Z/exportfs.1m 3664912314 3850 /usr/share/man/man1m.Z/pcnfsd.1m 2551183873 2549 /usr/share/man/man1m.Z/yppasswdd.1m 2359928792 2977 /usr/share/man/man1m.Z/ypmake.1m 257139511 5514 /usr/share/man/man3.Z/secure_rpc.3c 2683349483 6590 /usr/share/man/man3.Z/ypclnt.3c 1318220241 3266 /usr/share/man/man4.Z/exports.4 2769284022 1642 /usr/share/man/man4.Z/netgroup.4 4102917048 258048 /sbin/fs/nfs/mount 2453477347 200704 /sbin/fs/nfs/umount 4187593876 221472 /sbin/fs/cachefs/fsck 1911629031 175972 /sbin/fs/cachefs/mount 2693312472 155252 /sbin/fs/cachefs/umount 1914448232 16384 /sbin/fs/autofs/mount 315639114 16384 /sbin/fs/autofs/umount 2922132449 20480 /usr/sbin/onccompat 1104422468 181084 /usr/sbin/cfsadmin 3414139120 67964 /usr/sbin/cachefsstat 2663171612 685 /sbin/lib/mfsconfig.d/cachefs 2446583780 32768 /usr/bin/nfsstat 3698466417 135168 /usr/sbin/rpc.lockd 1923549434 40960 /usr/sbin/rpc.mountd 3834898517 19351 /sbin/init.d/nfs.client 1936194839 1047 /sbin/init.d/autofs 3389973196 1799 /sbin/init.d/autofs_setup 2356037222 32768 /usr/lib/netsvc/fs/autofs/automount 157556886 86016 /usr/lib/netsvc/fs/automount/automount 1424160023 16384 /usr/sbin/nfsd 1021577856 69632 /usr/sbin/automountd 375752451 5662 /usr/share/man/man1m.Z/mount_nfs.1m 2879173239 3869 /usr/share/man/man1m.Z/cfsadmin.1m 2044996720 915 /usr/share/man/man1m.Z/fsck_cachefs.1m 2021764642 3278 /usr/share/man/man1m.Z/mount_cachefs.1m 3217179419 1161 /usr/share/man/man1m.Z/cachefsstat.1m 2856219467 13392 /usr/share/man/man1m.Z/automount.1m 2765411850 1604 /usr/share/man/man1m.Z/automountd.1m 1109082091 589 /usr/share/man/man1m.Z/onccompat.1m 2963309924 2524 /usr/share/man/man1m.Z/mountd.1m 2202558109 3699 /usr/newconfig/etc/rc.config.d/nfsconf 2626622420 12288 /usr/sbin/stdhosts 2463443847 14172 /usr/newconfig/var/yp/Makefile 4285097228 32768 /usr/lib/netsvc/rstat/rpc.rstatd 2696206177 24576 /usr/lib/netsvc/rusers/rpc.rusersd 3684578648 20480 /usr/lib/netsvc/rwall/rpc.rwalld 3062078968 20480 /usr/lib/netsvc/spray/rpc.sprayd Patch Conflicts: None Patch Dependencies: s700: 10.20: PHCO_22448 PHCO_20061 PHKL_16750 PHNE_19937 s800: 10.20: PHCO_22448 PHCO_20061 PHKL_16751 PHNE_19936 Hardware Dependencies: None Other Dependencies: None Supersedes: PHCO_9543 PHNE_8310 PHKL_8545 PHKL_8544 PHKL_9156 PHKL_9155 PHNE_9465 PHNE_9864 PHNE_10515 PHNE_10894 PHNE_11009 PHNE_11008 PHNE_11387 PHNE_11386 PHNE_12428 PHNE_12427 PHNE_13236 PHNE_13235 PHNE_13669 PHNE_13668 PHNE_13835 PHNE_13731 PHNE_13824 PHNE_13823 PHNE_13834 PHNE_13833 PHNE_14072 PHNE_14071 PHNE_15042 PHNE_15041 PHNE_15541 PHNE_15864 PHNE_15863 PHNE_16117 PHNE_16925 PHNE_16924 PHNE_17055 PHNE_17098 PHNE_17620 PHNE_17619 PHNE_17842 PHNE_18915 PHNE_18962 PHNE_18961 PHNE_19072 PHNE_19073 PHNE_19426 PHNE_20021 PHNE_20091 PHNE_20313 PHNE_20626 PHNE_20628 PHNE_20957 PHNE_21108 PHNE_21375 PHNE_21704 PHNE_22117 PHNE_22892 PHNE_22288 PHNE_22893 PHNE_22877 Equivalent Patches: None Patch Package Size: 3790 KBytes Installation Instructions: Please review all instructions and the Hewlett-Packard SupportLine User Guide or your Hewlett-Packard support terms and conditions for precautions, scope of license, restrictions, and, limitation of liability and warranties, before installing this patch. ------------------------------------------------------------ 1. Back up your system before installing a patch. 2. Login as root. 3. Copy the patch to the /tmp directory. 4. Move to the /tmp directory and unshar the patch: cd /tmp sh PHNE_24143 5a. For a standalone system, run swinstall to install the patch: swinstall -x autoreboot=true -x match_target=true \ -s /tmp/PHNE_24143.depot By default swinstall will archive the original software in /var/adm/sw/patch/PHNE_24143. If you do not wish to retain a copy of the original software, you can create an empty file named /var/adm/sw/patch/PATCH_NOSAVE. WARNING: If this file exists when a patch is installed, the patch cannot be deinstalled. Please be careful when using this feature. It is recommended that you move the PHNE_24143.text file to /var/adm/sw/patch for future reference. To put this patch on a magnetic tape and install from the tape drive, use the command: dd if=/tmp/PHNE_24143.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: PHNE_17619: PHNE_17620: PHNE_17842: After installation of this patch, the NFS configuration file will control the behavior of the system, and can be modified by the system administrator. The values set by this patch (and the resulting system behavior) are as follows: For systems not previously running NFS Version 3 either via patch installation or by installation of the ACE/HWE Networking Bundles (B6378AA or B6379AA), the NFS configuration file will contain AUTOFS=0 MOUNT_VER=2 MOUNTD_VER=2 This indicates that only the Automounter may be used (as previously set by the AUTOMOUNT variable in this file) and that the AutoFS product will not be used. In addition, the default client protocol requested at mount time will be PV2 (MOUNT_VER=2), and only PV2 will be supported by the server (MOUNTD_VER=2). For systems currently running NFS Version 3 either via patch installation or by installation of the ACE/HWE Networking Bundles (B6378AA or B6379AA), the NFS configuration file will contain AUTOFS=1 MOUNT_VER=3 MOUNTD_VER=3 This indicates that AutoFS will be used, if the previously defined AUTOMOUNT variable is set to 1. In addition, the default client protocol requested at mount time will be PV3, and the default protocol supported for exported file systems will be PV3. PV2 will be supported as well in both instances. The system administrator may modify these variables as is deemed appropriate, but selecting PV3 or AutoFS should not be attempted unless all patches included in the Networking Bundle have been installed. These patches have been listed in the April 15th DataComm Newsletter, and are defined by the "SET_700_10.20_NFS_ACE2" patch set, for s700 systems, or the "SET_800_10.20_NFS_HWE" patch set for s800 systems. When converting from automounter to AutoFS, it is neces- sary to first verify that all map files have execute access ("x") turned off. AutoFS will treat any map file with execute access as an executable map, not a regular map. Automounter ignores these bits, AutoFS does not! When converting to AutoFS, these maps will fail until their execute bits are cleared. The namesvrs file, Makefile, nfsconf, and the ypmake script are delivered to the /usr/newconfig directory to prevent overwriting of a user configurable file. After customizing, the namesvrs file, Makefile, nfsconf, and the ypmake script the customer is required to move all four to where they belong in the file system, replacing the old ones. The installer is responsible for saving off the old files or risk losing them. A performance enhancement which was originally introduced in PHNE_15863/4 addressed a problem where an NFS client sent READ calls over the wire prior to sending WRITESs even in cases where the READ was not necessary. Part of the fix for this problem was to introduce a new kernel variable called "nfs_no_read_before_write" By default, the no_read_before_write behavior, which avoids redundant read request to an NFS Server when appending to a file, is on. To turn it off, the system manager must do the following using adb: echo "nfs_no_read_before_write/W 0" | \ adb -k -w /stand/vmunix /dev/mem One good reason to turn this flag off is when there are multiple processes on a single client writing to the same file over an nfs mount point without holding a lock. ------------------- A performance enhancement which was originally introduced in PHNE_15863/4 addressed a problem where an NFS client sent READ calls over the wire prior to sending WRITESs even in cases where the READ was not necessary. Part of the fix for this problem was to introduce a new kernel variable called "nfs_no_read_before_write" By default, the no_read_before_write behavior, which avoids redundant read request to an NFS Server when appending to a file, is on. To turn it off, the system manager must do the following using adb: echo "nfs_no_read_before_write/W 0" | \ adb -k -w /stand/vmunix /dev/mem One good reason to turn this flag off is when there are multiple processes on a single client writing to the same file over an nfs mount point without holding a lock.