 |
» |
|
|
|
|
|
|
|
|
|
Patch Name: PHNE_28103
Patch Description: s700_800 11.11 ONC/NFS General Release/Performance Patch
Creation Date: 03/01/15
Post Date: 03/02/05
Warning: 03/12/05 - This Critical Warning has been issued by HP.
- PHNE_27218 introduced behavior that under rare circumstances
can result in non-responsive ONC 1.2 AutoFS-managed
file systems. Any file system managed by ONC 1.2
AutoFS may experience this behavior.
- The behavior is also exhibited by superseding patches
PHNE_28103 and PHNE_28568.
- Details about this behavior are:
- The first indication of this behavior is that a command
will hang while attempting to access a non-responding
AutoFS-managed file system.
- The file system will not appear to be mounted.
- When enabled, automount logging will not show any
activity for this file system after the behavior has
occurred, regardless of how many attempts are made to
access it.
- AutoFS itself does NOT hang, so other AutoFS-managed file
systems will act properly.
- No failure messages will be displayed via dmesg(1M) or
in /var/adm/syslog/syslog.log.
- The behavior is most easily recognized by examining the
autonode an_mntflags value, using the nfsshow utility,
q4, or p4. The nfsshow utility, which is available from
HP, is the easiest tool to use. If the autonode
an_mntflags value is 0x185, then this behavior is the
cause of the non-responsive file system:
an_mntflags=MF_MNTPNT|MF_WAITING_MOUNT|MF_CHECKED|
MF_TRIGGER(0x185)
- The behavior has been observed in configurations with the
default timer setting, which is 300 seconds.
- This behavior is corrected in PHNE_28983, which is
released. To avoid this behavior, HP recommends that
PHNE_28983 be installed on systems using AutoFS.
- PHNE_28103 is included in the following Support Plus
Patch Bundles:
Jun 2003: GOLDBASE11i,B.11.11.0306.4
Sep 2003: GOLDBASE11i,B.11.11.0306.4
Hardware Platforms - OS Releases:
s700: 11.11
s800: 11.11
Products: N/A
Filesets:
NFS.KEY-CORE,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
NFS.NFS-64ALIB,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
NFS.NFS-64SLIB,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
NFS.NFS-CLIENT,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
NFS.NFS-CORE,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
NFS.NFS-ENG-A-MAN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
NFS.NFS-PRG,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
NFS.NFS-SERVER,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
NFS.NFS-SHLIBS,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
NFS.NIS-CLIENT,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
NFS.NIS-CORE,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
NFS.NIS-SERVER,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
NFS.NISPLUS-CORE,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
NFS.NFS-KRN,fr=B.11.11,fa=HP-UX_B.11.11_32,v=HP
NFS.NFS-KRN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP
Automatic Reboot?: Yes
Status: General Superseded With Warnings
Critical:
Yes
PHNE_28103: HANG
PHNE_27218: PANIC MEMORY_LEAK CORRUPTION HANG
PHNE_26388: PANIC
PHNE_25627: ABORT PANIC MEMORY_LEAK HANG
PHNE_25625: ABORT
PHNE_24910: ABORT PANIC CORRUPTION HANG
PHNE_24035: ABORT CORRUPTION HANG
PHNE_23502: ABORT PANIC HANG
PHNE_22878: PANIC HANG
Category Tags:
defect_repair enhancement general_release critical panic
halts_system corruption memory_leak manual_dependencies
Path Name: /hp-ux_patches/s700_800/11.X/PHNE_28103
Symptoms:
PHNE_28103:
( SR:8606276016 CR:JAGae40093 )
The rpc.yppasswdd process dies.
( SR:8606274502 CR:JAGae38579 )
RPC does not function properly.
( SR:8606288394 CR:JAGae52325 )
Incorrect permissions for the log file.
( SR:8606281883 CR:JAGae45826 )
The netdir_getbyname() routine using NIS can hang under
certain circumstances.
( SR:8606276334 CR:JAGae40412 )
Problem with ypxfrd.
( SR:8606286563 CR:JAGae50502 )
Incorrect configuration for AutoFS.
( SR:8606274555 CR:JAGae38632 )
Showmount dumps the core with SIGSEGV.
PHNE_27218:
( SR:8606249576 CR:JAGae15966 )
A client's attempt to acquire a lock may result in a delay
or a hang.
( SR:8606249559 CR:JAGae15949 )
The '-p' option for rpc.mountd described in the man page
does not function as described.
( SR:8606180770 CR:JAGad49991 )
Blocked lock requests on a client system hang.
( SR:8606233931 CR:JAGae03154 )
After the AutoFS client unmount timer expires, if the
unmount of the parent file system fails and the remount of
hierarchical mount points fails, then zero entries are found
while accessing the hierarchical mount points under the
parent file system. Once this condition occurs the failed
hierarchical mounts will not retry mounting.
( SR:8606234034 CR:JAGae03255 )
The nfsconfcol script is not removing the target data files
before writing to them.
( SR:8606256845 CR:JAGae21158 )
The /var/adm/automount.log file is shipped incorrectly.
( SR:8606256846 CR:JAGae21159 )
The /var/spool/rexd directory is shipped incorrectly.
( SR:8606259831 CR:JAGae24149 )
A client system hangs when trying to lock a file.
( SR:8606255006 CR:JAGae19335 )
Exported directories cannot be mounted.
( SR:8606277106 CR:JAGae41178 )
Under heavy load, file systems mounted with AutoFS never get
unmounted, even after the system load has decreased.
( SR:8606257688 CR:JAGae21991 )
Client hangs when trying to lock a remote file.
( SR:8606260873 CR:JAGae25195 )
Large files become corrupt when writing across NFS mounts.
( SR:8606242021 CR:JAGae09276 )
1. Many "dup_remove_pending: WARNING: duplicate request
cache size (210) > XID_CACHE_SIZE (200), continuing"
messages in syslog.log and automount.log.
2. Many "Rmdir: err=247, mnt='<mount-point-dir>'" messages
in automount.log.
( SR:8606226778 CR:JAGad95840 )
If an AutoFS mounted filesystem using a simple direct map is
manually unmounted, a panic may result if that filesystem is
referenced simultaneously (e.g. by two or more ls commands).
The panic string is:
"Data page fault".
The panic stack trace is:
panic+0x14
report_trap_or_int_and_panic+0x80
trap+0xdb8
nokgdb+0x8
nfs3_root+0x68
hpauto_trigger_mount+0x20c
auto_access+0x30
chdirec_seg+0x5c
chdirec+0x14
chdir+0x34
syscall+0x29c
$syscallrtn+0x0
( SR:8606248269 CR:JAGae14669 )
If a client's /var/statmon/sm directory contents are
destroyed, future lock requests hang.
( SR:8606245329 CR:JAGae11799 )
A system hangs or panics when issuing a "ln" command.
( SR:8606264317 CR:JAGae28647 )
This product update is a member of a set needed to enable
the optional HP-UX Device IDs feature. Upon installation,
the HP-UX Device IDs bundle (DevIDs11i) will install the
full set of product updates (including this one) necessary
to enable the Device IDs feature.
If the HP-UX Device IDs product (DeviceIDs11i) is not
installed, this product update to HP-UX will have no
impact on your system.
( SR:8606265228 CR:JAGae29556 )
Spinlock deadlock panic due to a lock being held too long.
( SR:8606259713 CR:JAGae24031 )
AutoFS problem.
( SR:8606234968 CR:JAGae04152 )
When automountd gets a stale NFS file handle error for a
direct mount point, it removes the corresponding AutoFS
direct map entry for that mount point from the file
/etc/mnttab. Automountd needs to be stopped and restarted to
get back the direct AutoFS mount point.
( SR:8606235172 CR:JAGae04352 )
The NFS mount operation returns an incorrect error message
when all ports are in use. The error message is:
nfs mount: bindresvport: t_errno = 8
nfs mount: get_fh: Couldn't bind to a reserved port.
return = -1
( SR:8606245876 CR:JAGae12335 )
System panics when the mount of an exported file system that
contains an extraneous or missing "/" fails. The panic
string is: rm_autonode: No entry for <address>
( SR:8606257219 CR:JAGae21525 )
Accessing a TCP AutoFS mount point causes the system to
hang.
( SR:8606244127 CR:JAGae10618 )
If rpc.lockd and rpc.statd are restarted and the
/var/statmon/sm directory is destroyed on the server, the
client's rpc.lockd takes 35 minutes to recover.
( SR:8606264087 CR:JAGae28412 )
When a 64-bit RPC application uses UNIX authentication
flavor, the RPC server does not properly decode the client
credentials.
( SR:8606271227 CR:JAGae35462 )
The "ls" command will hang when users try to access a dead
server after some systems with mounted directories are shut
down.
( SR:8606147221 CR:JAGad16564 )
Problem with privileged groups.
( SR:8606248870 CR:JAGae15267 )
The "cd" command to an AutoFS direct offset mount directory
hangs, and automountd cannot be killed by pressing CTRL-C to
stop the "cd" command.
( SR:8606232532 CR:JAGae01767 )
AutoFS mounted directories are empty.
( SR:8606254087 CR:JAGae18419 )
The rpcbind process increases in size and stops responding
to client requests. This requires rpcbind needs to be killed
and restarted.
PHNE_26388:
( SR:8606248624 CR:JAGae15022 )
AutoFS causes a system panic with the panic string
"rm_autonode: No entry for <<address>>".
PHNE_25627:
( SR:8606230660 CR:JAGad99710 )
A server stub generated by rpcgen logs error messages to
/dev/console.
( SR:8606188628 CR:JAGad57842 )
The man page for nsswitch.conf does not reflect ldap as an
additional database source for nss backends.
( SR:8606228306 CR:JAGad97363 )
A file has an unusual timestamp when created with open(2)
using O_EXCL flag.
( SR:8606224657 CR:JAGad93745 )
File lock recovery fails when the server reboots if the
server has multiple network interfaces and the client has
mounted the file system with an interface name different
than the server's hostname.
( SR:8606218377 CR:JAGad87526 )
A multi-threaded server leaks file descriptors under heavy
load if clients are running on the same box.
( SR:8606186978 CR:JAGad56188 )
Partially cached large binaries are removed at unmount time
by CacheFS.
( SR:8606225370 CR:JAGad94457 )
The system panics due to a data page fault on the NFS server
when processing a TCP client mount request.
( SR:8606230685 CR:JAGad99735 )
Excessive warning messages being logged:
WARNING: filegrp_destroy_metadata:
fileno 61 slot 7-5 fgp 41f2c1d0 not allocated.
( SR:8606219527 CR:JAGad88667 )
On a client system, the old automounter is trying to access
a non-existent entry in the NIS map and that is generating
an excessive number of packets over the network which causes
slow response time.
( SR:8606226735 CR:JAGad95797 )
The inetd is unable to resolve services.
( SR:8606237277 CR:JAGae06322 )
NFS PV2 client does not properly show the quota exceeded
error.
( SR:8606221217 CR:JAGad90351 )
The "ll" command hangs in the case of an automounted file
system if the server is down.
( SR:8606221909 CR:JAGad91027 )
System panic occurs while autofs is unmounting the idle
autofs mount points. The panic string is "spinlocks held
with M_WAITOK".
( SR:8606221102 CR:JAGad90236 )
Reactivating a user account that has been disabled on a
trusted NIS+ clients fails.
( SR:8606172908 CR:JAGad42168 )
When an HANFS package is manually failed over back-and-forth
between two different cluster server nodes within a period
of time shorter than five minutes, then on any NFS client
which have the HANFS package filesystem mounted over TCP,
NFS access to that filesystem can appear hung for a
relatively long period of time - usually more than four
minutes, with no apparent response from the server. Also
the NFS client issues the error message "NFS server XXXXXXX
not responding still trying", about every 30 seconds.
( SR:8606226170 CR:JAGad95241 )
A "umount" of an NFS mounted file system using CacheFS
causes an RPC error.
( SR:8606229377 CR:JAGad98430 )
AutoFS mounted file systems never get unmounted.
( SR:8606204999 CR:JAGad74175 )
The ttsyncd process loops, occupying much of the CPU usage
and causing the system to slow down.
( SR:8606225120 CR:JAGad94209 )
rpc.rusersd core dumps if more than 180 users have logged
in.
PHNE_25625:
( SR:8606245747 CR:JAGae12206 )
rpc.lockd core dumps with a SIGBUS error during heavy NFS
file locking.
PHNE_24910:
( SR:8606184366 CR:JAGad53575 )
Instruction page fault where the instruction address being
accessed is 0.
( SR:8606201620 CR:JAGad70794 )
On SUN's NIS clients, it is possible to specify a list of
available NIS servers for a given domain. HP's NIS clients
do not provide this functionality.
( SR:8606147778 CR:JAGad17120 )
RPC client call rejection from an RPC server because of
unsupported RPC protocol version can result in an error
incorrectly indicating a non-response from the RPC server.
For example, an NFS operation results in "NFS server
<server name> not responding still trying" error.
( SR:8606216548 CR:JAGad85717 )
A password expires unexpectedly in an NIS+ environment.
( SR:8606205779 CR:JAGad74954 )
The automountd (AUTOFS) hangs/cores while attempting to
automount exported FS and reports 100% CPU utilization.
( SR:8606205013 CR:JAGad74189 )
The mount option 'grpid' does not return the correct 'gid'
value on NFS PV2 and PV3.
( SR:8606212242 CR:JAGad81430 )
When a customer specifies a user name with leading blank
characters as an argument to nispasswd and passwd(1),
nispasswd modifies the username to include those leading
blanks in the NIS+ passwd table and trusted table.
( SR:8606187776 CR:JAGad56985 )
An NFS/TCP client panics while under heavy NFS load. Problem
has been seen most often while client performed 100 NFS/TCP
mounts in succession.
( SR:8606220062 CR:JAGad89203 )
The ovcmsgrd process aborts and produces a core file when
the Network Node Manager managed processes are started with
"ovstart opc".
( SR:8606219558 CR:JAGad88698 )
During the login process, NIS+/trusted clients force NIS+
users to modify their password when their password is
expired but fail to un-expire the password when their
password is changed. Users will always be forced to modify
their password as soon as it has expired.
( SR:8606213087 CR:JAGad82274 )
NFS PV3 allows the file to be opened with mandatory lock
(02760) permission, while NFS only supports advisory lock.
( SR:8606199444 CR:JAGad68631 )
The yppasswd command updates fields other than the user
password field in an NIS map.
( SR:8606198866 CR:JAGad68055 )
Can not cache large files (> 2GB) with cachefs mount.
( SR:8606169485 CR:JAGad38760 )
NFS/TCP client does not handle out-of-order streams messages
correctly while attempting to connect to the server and can
result in a client panic.
PHNE_24035:
( SR:8606196567 CR:JAGad65770 )
AutoFS cannot unmount a cachefs type file system.
( SR:8606208446 CR:JAGad77633 )
NFS file lock recovery fails because rpc.statd matches the
wrong hostname.
( SR:8606207461 CR:JAGad76637 )
rpcbind crashes with signal 10, Bus error (SIGBUS).
( SR:8606164133 CR:JAGad33433 )
The ypxfr command fails with the error message:
"ypxfr: bind_to_server clntudp_create error: RPC unknown
host".
( SR:8606184904 CR:JAGad54106 )
rpc.lockd can cause a user process to hang, if a loopback
mount is specified with an alias hostname.
( SR:8606207826 CR:JAGad77003 )
The nisplus.server script does not kill the rpc.nispasswdd
process when performing the "/sbin/init.d/nisplus.server
stop" command.
( SR:8606181688 CR:JAGad50904 )
On a system with active lofs mounts managed by AutoFS, the
"/sbin/shutdown" command may hang when the file systems are
unmounted.
( SR:8606160777 CR:JAGad30096 )
AutoFS can not unmount hfs or cdrom file system types.
( SR:8606168123 CR:JAGad37405 )
An NFS/TCP client operation receives "NFS server not
responding still trying" messages while attempting to access
the server, even though the server system is up. In this
case, NFS/TCP on the server shows many TCP connections for
local address port 2049 in a CLOSE_WAIT state when
performing a "netstat -an" command.
( SR:8606203242 CR:JAGad72416 )
A process sequentially reading a large file across an NFS
mount runs extremely slow if, at the same time, there is
another process sequentially writing a large file to an
NFS mounted directory, and one or more biods are running on
the system.
( SR:8606152534 CR:JAGad21864 )
AutoFS can mishandle unmounts when a server is down, which
may appear as bdf command anomalies.
( SR:8606202370 CR:JAGad71544 )
NFS locks remain when killing NFS loopback mounted client
applications.
( SR:8606204523 CR:JAGad73705 )
There is no support for cachefs.
( SR:8606176017 CR:JAGad45257 )
AutoFS directories are empty under heavy NFS load.
( SR:8606193515 CR:JAGad62727 )
Duplicate entries for direct AutoFS mounts show up in the
/etc/mnttab file.
( SR:8606186548 CR:JAGad55752 )
An RPC server running in TCP multithreaded mode develops a
file descriptor leak when clients are on the same machine as
the server. Eventually the server fails to process the
clients' requests when the process limit is attained.
( SR:8606146332 CR:JAGad15675 )
The I/O throughput on a locked file is low compared to the
throughput on an unlocked file.
PHNE_23502:
( SR:8606183171 CR:JAGad52387 )
UDP packets sent by remote users can cause RPC applications
to abort.
( SR:8606160596 CR:JAGad29916 )
The /var/adm/automount.log file fills up the /var file
system.
( SR:8606178618 CR:JAGad47845 )
The rename() system call always fails when trying to rename
a directory in a cachefs-mounted file system, if the target
directory name exists. 'errno' gets set to EPERM ("Not
Owner").
( SR:8606128739 CR:JAGac86286 )
File corruption over NFS when NFS file server is TOC'ed.
( SR:8606140609 CR:JAGad09968 )
Core dump occurs when user belongs to more than 16 groups.
( SR:8606159451 CR:JAGad28779 )
A multithreaded process can hang when performing NFS file
operations and concurrently writing core, forking, using a
debugger, or undergoing job control. A similar situation
arises in any process where a user can issue a CTRL-Z, send
a SIGSTOP, or use a debugger. These hung processes also
carry the potential of hanging the system.
( SR:8606180764 CR:JAGad49985 )
rpc.lockd causes user process to hang.
( SR:8606180765 CR:JAGad49986 )
rpc.lockd causes user process to hang.
( SR:8606175862 CR:JAGad45102 )
Mount points of automounter directories are not visible when
executing the "ls" command.
( SR:8606175781 CR:JAGad45021 )
The "du" output is eight times higher over NFS with an HP
server / Sun Client configuration when compared to an HP
server / HP Client configuration.
( SR:8606172747 CR:JAGad42007 )
Changing an NIS+ user's password with nispasswd() or
passwd() while the system is in trusted mode without
specifying the dot "." notation (non fully qualified domain)
results in an incorrect sub-domain being created.
( SR:8606165859 CR:JAGad35150 )
Data page fault panic while copying a file using NFS V3
between an HP-UX client and an NT InterDrive server where
the target filesystem is full.
( SR:8606199460 CR:JAGaa35208 )
The libnsl library uses a large amount of BSS and DATA
memory.
( SR:8606174017 CR:JAGad43270 )
rpc.lockd drops the lock request from the same process for a
different file.
( SR:8606185238 CR:JAGad54440 )
Partial record unlocking in NFS does not work properly.
( SR:8606173363 CR:JAGad42623 )
The "man nfsstat" command does not display all of the
statistical data fields.
( SR:8606178998 CR:JAGad48223 )
Unnecessary NFS read before write is causing severe
decreases in write performance.
( SR:8606176384 CR:JAGad45622 )
The boot process of a Linux client fails due to rpc.mountd
not allowing AUTH_NULL authentication.
( SR:1653311530 CR:JAGab46804 )
Unable to use fsirand() on JFS file system.
( SR:8606169796 CR:JAGad39062 )
Data page fault panic due to bad machine name length in NFS
request.
( SR:8606171662 CR:JAGad40926 )
exportfs sometimes does not work correctly when invalid host
names are present in a host list in the /etc/exports file.
( SR:8606179200 CR:JAGad48424 )
rpc.lockd core dumps when the user process is interrupted
with CTRL-C.
( SR:8606169011 CR:JAGad38290 )
The automount process hangs, making automounter mount points
inaccessible.
( SR:8606179951 CR:JAGad49173 )
getservbyname() using NIS returns NULL when trying to
resolve service aliases.
( SR:8606167053 CR:JAGad36339 )
An NFS/TCP client operation receives "NFS server not
responding still trying" messages while attempting to access
the server, even though the server system is up. The server
displays "vmunix: WARNING: tcpd_thread_create: thread_create
failed: 11" messages in /var/adm/syslog/syslog.log.
PHNE_23248:
( SR:8606188447 CR:JAGad57655 )
autofs does not appear to remove inactive mounts from
/etc/mnttab.
PHNE_22878:
( SR:8606127276 CR:JAGac68822 )
A failing mount request may return a wrong error code.
( SR:8606168603 CR:JAGad37881 )
Loading binary via CacheFS is slower than via NFS.
( SR:8606166823 CR:JAGad36110 )
NFS client panics when the server is down.
( SR:8606168604 CR:JAGad37882 )
Periodically the CacheFS umount command hangs.
( SR:8606135856 CR:JAGad04988 )
Panic occurs when trying to umount a ufs filesystem which is
still in the process of mounting.
( SR:8606160808 CR:JAGad30127 )
When mounting an NFS directory with the quota option, the
quota does not get enforced.
( SR:8606168606 CR:JAGad37884 )
No visible increase in performance while reloading an
application binary.
( SR:8606166314 CR:JAGad35601 )
The 'kill' and 'stop' NFS processes on a client do not work.
( SR:8606145476 CR:JAGad14812 )
Remote locking of a file occasionally leads to a system
hang.
( SR:8606155843 CR:JAGad25155 )
NIS fails to return all groups for id/group command when
concurrent access is allowed to maps.
( SR:8606146885 CR:JAGad16228 )
The "rpcinfo -u" command fails when the nfsd unregisters
a running nfsd process on startup.
( SR:8606159736 CR:JAGad29062 )
Unexpected delay in unmounting of Autofs mounts.
( SR:8606158230 CR:JAGad27560 )
Occasionally umount may cause panic within
nfs3_close/nfs_close.
( SR:8606145517 CR:JAGad14853 )
If NFS is stopped and restarted, the nfsd processes do not
get re-registered with rpcbind, and rpcinfo commands fail.
( SR:8606169239 CR:JAGad38515 )
Cachefsstat is not returning the correct statistics.
( SR:8606157592 CR:JAGad26923 )
Newkey does not recognize the root password of the remote
machine and returns an error, "ERROR, passwd differs from
login passwd".
Defect Description:
PHNE_28103:
( SR:8606276016 CR:JAGae40093 )
The rpc.yppasswdd process dumps the core.
Resolution:
rpc.yppasswdd has been modified to correct the problem.
( SR:8606274502 CR:JAGae38579 )
RPC does not function properly.
Resolution:
RPC has been modified to correct the problem.
( SR:8606288394 CR:JAGae52325 )
Incorrect permissions for the log file.
Resolution:
Automount has been modified to set the proper permissions
for the default log file.
( SR:8606281883 CR:JAGae45826 )
When netdir_getbyname() calls ypmatch a hang can result
under certain circumstances.
Resolution:
The logic in ypmatch has been modified.
( SR:8606276334 CR:JAGae40412 )
ypxfrd picks up files with the wrong pathname.
Resolution:
Code changes were made to check for the wrong pathname. Some
restrictions regarding invalid domain and map names are now
enforced. The domain and map names of "." and ".." and those
containing "/" are now rejected.
( SR:8606286563 CR:JAGae50502 )
Incorrect configuration for AutoFS.
Resolution:
The AutoFS code has been modified to address the problem.
( SR:8606274555 CR:JAGae38632 )
Showmount dumps the core with SIGSEGV.
Resolution:
Code has been added to address the problem.
PHNE_27218:
( SR:8606249576 CR:JAGae15966 )
To obtain the port information of client's rpc.lockd, a
server needs to communicate with the client's portmapper.
A file descriptor is allocated on the server and it polls to
check whether replies arrive from the client's portmapper.
For this polling process, the file descriptor should be
registered with the polling list. However, file descriptors
with values that are multiples of 32 do not get registered,
and thus the server does not get the port information.
Resolution:
Fixed the routine that registers the file descriptors.
( SR:8606249559 CR:JAGae15949 )
The '-p' option for rpc.mountd described in the man page is
obsolete.
Resolution:
Modify the man page to indicate that the '-p' option for
rpc.mountd is obsolete.
( SR:8606180770 CR:JAGad49991 )
The client currently does not retransmit the blocked lock
requests. As a result, if the NLM_GRANTED_MSG sent by the
server is lost and it doesn't retry the request, the blocked
lock requests on the client will wait forever.
Resolution:
The client lockd is modified to retransmit the blocked lock
requests. If the NLM_GRANTED_MSG is lost and the server does
not retry then the retransmission of the blocked lock
requests will prevent the hangs on the client.
( SR:8606233931 CR:JAGae03154 )
The parent file system has inconsistent hierarchical mount
points when the automount daemon cannot remount them at the
time the unmount of the parent file system fails. The
unmount of the parent file system can fail if a process is
accessing that file system at the same time the automount
daemon is trying to unmount it. The automount daemon could
not remount the hierarchical mount points due to
unavailability of the remote mount daemon (i.e. the remote
mount daemon is not running).
Resolution:
The automount daemon has been modified so that it informs
the AutoFS client whether or not it could remount the
hierarchical mount points when the unmount of the parent
file system fails. AutoFS has been modified to act based on
the return value from the automount daemon. AutoFS sends a
remount request for the autonode if the automount daemon
could not remount the hierarchical mount points under the
parent file system.
( SR:8606234034 CR:JAGae03255 )
The nfsconfcol script is not removing the target and
temporary data files before writing data to them. If the
script aborts, the files may be wrong.
Resolution:
Remove the target and temporary data files before writing to
them.
( SR:8606256845 CR:JAGae21158 )
The /var/adm/automount.log file is shipped incorrectly.
Resolution:
The /var/adm/automount.log file is now shipped properly.
( SR:8606256846 CR:JAGae21159 )
The /var/spool/rexd directory is shipped incorrectly.
Resolution:
The /var/spool/rexd directory is now shipped properly.
( SR:8606259831 CR:JAGae24149 )
When rpc.lockd starts after a crash, it sends a crash
notification to rpc.statd. If rpc.statd is not yet
registered with rpcbind, rpc.lockd does not re-try the crash
notification, and crash recovery does not take place. This
causes apparent hangs to clients trying to lock files.
Resolution:
Modified the rpc.lockd code to retry the crash notification
to rpc.statd 20 times, due to the delay in rpc.statd
registration.
( SR:8606255006 CR:JAGae19335 )
While performing multiple concurrent exportfs operations,
the /etc/xtab file's modification time remains the same.
This leads to incorrect mount and showmount output, and at
least one of the exported directories cannot all be mounted.
Resolution:
Changed the logic so that rpc.mountd considers both the
modification time and the file size of the /etc/xtab file to
update the output of the mount and showmount commands.
( SR:8606277106 CR:JAGae41178 )
There is a race condition in the AutoFS kernel code where
two threads executing the same code can cause one of the
threads to wait forever. The thread that waits forever
causes the AutoFS mounted file system to be busy,
preventing it from ever being unmounted.
Resolution:
The AutoFS kernel code was modified to prevent this race
condition. The race condition is avoided by changing the
conditions for which a thread will block when executing
this particular AutoFS kernel code.
( SR:8606257688 CR:JAGae21991 )
If a kill signal is delivered to a thread sending an unlock
request on a single CPU machine, the thread enters a tight
loop in order to clean up the locking information on the
server. This causes the thread to hold the CPU and the
machine hangs.
Resolution:
When the interrupt error (EINTR) returns to the kernel lock
manager due to signals, the kernel lock manager makes the
next RPC call uninterruptible, which causes threads to sleep
during the RPC calls and releases the CPU.
( SR:8606260873 CR:JAGae25195 )
The number of bytes to be written to a file is stored as a
signed long value. On 32-bit clients, this value overflows
when a file is greater than 2.5 GB, and the file becomes
corrupted.
Resolution:
Modified the code so that variable overflow does not occur.
( SR:8606242021 CR:JAGae09276 )
1. If there are multiple mount requests for a non-existent
server, then the automount daemon tries to move these
pending requests to cache. When this operation causes the
cache size to exceed a certain threshold value, the
automount daemon prints "dup_remove_pending: WARNING:
duplicate request cache size (210) > XID_CACHE_SIZE (200),
continuing" to the syslog.log file
2. When a mount request fails, the automount daemon first
removes the child node, and then tries to remove the parent
node. If the parent node is mounted or if there are other
files in the parent directory, the automount daemon logs
"Rmdir: err=247, mnt='<mount point-directory>'" to the
/var/adm/automount.log file.
Resolution:
1. The trace level must now be set to 10 (instead of greater
than 0) to log the message "dup_remove_pending: WARNING:
duplicate request cache size (210) > XID_CACHE_SIZE (200),
continuing" to /var/adm/automount.log. It will be logged to
/var/adm/syslog/syslog.log only if the verbose option is
enabled.
2. The trace level must now be set to 10 (instead of greater
than 0) to log the message "Rmdir: err=247,
mnt='<mount point-directory>'" to /var/adm/automount.log.
( SR:8606226778 CR:JAGad95840 )
After a manual unmount, two accesses take place
simultaneously. One access is forced to initiate a mount,
and before that mount completes, the other access
dereferences a pointer that hasn't been set yet. This
causes a data page fault which results in the panic.
Resolution:
Added a condition to check for a mount-in-progress which
makes the second access follow an existing code path to wait
for the first mount to complete.
( SR:8606248269 CR:JAGae14669 )
If the /var/statmon/sm contents are destroyed on the client,
the client's rpc.statd will not know which servers to notify
that the client has crashed and recovered. Since the server
never receives notification of the client system reboot, it
will continue holding onto locks for this client that are
now "stale". The server will also send any replies to new
lock requests to the old lockd port number on the client. In
most cases, the new instance of lockd on the client will not
be listening on the same port as the previous instance so it
will not receive these lock replies. The result is that
future lock requests from this client will hang, causing the
applications issuing these lock requests to hang.
Resolution:
The clear_locks(1M) command is provided to allow a root user
to forcibly notify the NFS server's rpc.lockd to discard all
locks and cached port information for a specified client.
This tool should only be used in cases where a client system
experienced a state change (i.e. re-installed or had
rpc.lockd or rpc.statd killed and re-started) and was not
able to successfully notify the server system using the
normal lockd/statd recovery mechanism.
( SR:8606245329 CR:JAGae11799 )
When a server does not support a PV3 link system call from a
client, the server returns an error message which hangs or
panics the client system.
Resolution:
When the server returns the error message for the PV3 link
system call, the client now releases a semaphore to avoid
the deadlock/hang.
( SR:8606264317 CR:JAGae28647 )
This product update contains minor enhancements required to
enable the HP-UX Device IDs feature.
When AutoFS unmounts a filesystem, it obtains the device id
from the filesystem server. If that server is slow, or not
responding, there may be a delay of 15 seconds or more. On
systems with many AutoFS managed filesystems and many slow
or non-responding servers, the cumulative delay may be quite
significant.
Resolution:
HP-UX is implementing Device IDs in the /etc/mnttab file.
AutoFS will now make use of the Device IDs and not query
each server when performing unmounts.
( SR:8606265228 CR:JAGae29556 )
System panics if all the entries in duplicate cache are
marked DUP_INPROGRESS, when a new duplicate cache request
arrives after reaching cache maximum limit.
Resolution:
Duplicate cache requests will return an error if cache
reaches maximum limit and all entries are marked
DUP_INPROGRESS.
( SR:8606259713 CR:JAGae24031 )
AutoFS problem.
Resolution:
Fixed the AutoFS problem.
( SR:8606234968 CR:JAGae04152 )
The unmount module of automountd is unable to find the
difference between the mount points with ESTALE errors and
the mount points that are to be unmounted. As a result,
apart from unmounting the mount points that are to be
unmounted, mount points with ESTALE errors are also
unmounted. Because of this, corresponding direct AutoFS
entries for those mount points are removed from the file
/etc/mnttab.
Resolution:
In automountd, the unmount module, which finds the mount
points that are to be unmounted, is modified so that it is
able to find the difference between the mount points with
ESTALE errors and the mount points that are to be unmounted.
( SR:8606235172 CR:JAGae04352 )
During an NFS mount operation, the client performs a bind
operation. When all ports are in use, the error message
returned is "system error" (t_errno = 8) instead of "address
busy" (t_errno = 23).
Resolution:
Return the error message "address busy" instead of "system
error" when all ports are busy.
( SR:8606245876 CR:JAGae12335 )
When an automount daemon's mount request fails, it counts
the number of slashes in the exported file system (e.g.
/dir/) to remove the directories that are created at
the time of mounting. In the /etc/exports a missing leading
"/" entry (e.g. export/dir/subdir) or an entry that contains
an extra "/" (e.g. /export/dir/) can result in automountd
counting too many "/"s. Since the automount daemon counts
the slashes from the exported file system (/etc/xtab), the
automount daemon counts one extra slash. This causes the
automount daemon to unlink an extra autonode, which is
supposed to be unlinked by AutoFS. AutoFS tries to unlink
the autonode that has already been unlinked by the automount
daemon, which causes the panic.
Resolution:
The automount daemon now ignores the trailing slashes, and
thus does not try to unlink the autonode that AutoFS
unlinks.
( SR:8606257219 CR:JAGae21525 )
Access to a TCP AutoFS mounted directory hangs because the
unmount from the previous access failed. This was due to the
connect address structure not being fully initialized during
binding to the port when the connection was established.
Resolution:
Modified the code to completely initialize the connect
address structure.
( SR:8606244127 CR:JAGae10618 )
If /var/statmon/sm directory is destroyed on server side,
rpc.lockd does not notify clients that the server has
crashed and recovered. If a client tries to contact the
server, it cannot get the new port number until 35 minutes
have elapsed since the last contact with the server's
rpc.lockd. This is because when the time value is checked to
verify if the port number is valid, the time value is
converted to microseconds, and this results in an overflow
condition that causes the delay.
Resolution:
When verifying if the port number is valid, only compare the
time value in seconds, and thus the overflow and the delay
do not occur.
( SR:8606264087 CR:JAGae28412 )
When a 64-bit RPC application uses UNIX authentication, the
client credentials are decoded incorrectly because the XDR
stream pointer is not positioned properly in the XDR stream.
Thus 64-bit RPC applications fail.
Resolution:
Modified libnsl to decode the UNIX credentials properly for
64-bit applications that use UNIX authentication.
( SR:8606271227 CR:JAGae35462 )
A hang occurs when an ls attempts to access directories from
a dead server. AutoFS will send mount requests for all the
autonodes under the same parent directory (e.g. /net) when
any one of the subdirectory tries (e.g. /net/serverx) has
failed during a mount request. If there are a lot of entries
(100+) under the same parent directory, then it will take a
long time to respond to the ls command.
Resolution:
AutoFS does not send out a mount request if the file system
was already mounted.
( SR:8606147221 CR:JAGad16564 )
Problem with privileged groups.
Resolution:
Fixed problem with privileged groups.
( SR:8606248870 CR:JAGae15267 )
For direct offset mounts, the "cd" command calls auto_lookup
in the AutoFS kernel for the offset directory. At this
moment, the parent directory is at the mounting status and
waiting for this lookup to be completed. But the auto_lookup
routine sleeps when the parent directory is mounting, so the
"cd" command hangs until the user presses CTRL-C. The CTRL-C
kills the kernel thread and leaves automountd in an
unknown status, so users cannot kill automountd.
Resolution:
The auto_lookup routine was modified to check if the calling
process is automountd and the autonode has child nodes
linked to it (which means it is a direct offset mount). If
it is direct offset mount, then auto_lookup does not sleep
and thus the lookup completes.
( SR:8606232532 CR:JAGae01767 )
The AutoFS code could send a mount request for an AutoFS
mount point that already had a mount in progress. This led
to the creation of corrupt AutoFS autonodes which showed up
as empty directories.
Resolution:
Modified AutoFS to check for mounts in progress before
sending a mount request.
( SR:8606254087 CR:JAGae18419 )
On the server, a transport handle is created for each client
portmap request. If the request is invalid, rpcbind ignores
the request and does not destroy the transport handle. Thus,
the size of rpcbind increases. Eventually rpcbind reaches a
limit and stops responding.
Resolution:
Rpcbind was modified to destroy the transport handle when it
finds that the connection oriented rpc request is invalid.
PHNE_26388:
( SR:8606248624 CR:JAGae15022 )
There was a race condition in the AutoFS code which could
result in an autonode hierarchy being removed twice. When
this happens the system panics.
Resolution:
The code which could cause the hierarchy to be removed a
second time has been removed.
PHNE_25627:
( SR:8606230660 CR:JAGad99710 )
Excessive error messages are logged to the console device.
Resolution:
Open the null special file instead of the console and
redirect the stderr and stdout to the null special file.
( SR:8606188628 CR:JAGad57842 )
Additional source support for nss backends from the ldap
directory server has been released since March 2000. The man
page for nsswitch.conf needs to have ldap added as an
additional source for nss backends.
Resolution:
The ldap information was added to the nsswitch.conf man
page.
( SR:8606228306 CR:JAGad97363 )
An unusual timestamp is set for files created with exclusive
mode flag O_EXCL on pv3 mounted file systems for Linux or
Network Appliance servers. These servers do not support
exclusive mode for creating files and the client does not
correct the timestamp.
Resolution:
The client resets the unusual timestamp returned by the
server to the correct 'server time'.
( SR:8606224657 CR:JAGad93745 )
The server's statd process sends a notify message with its
hostname only. If the client mounted the file system using
an interface name different than the server hostname, then
it will reject the notify message since its monitor entry
does not match the server hostname. As a result the client
file lock recovery will not take place.
Resolution:
The server's statd process was modified to build a list of
all local interface names during startup and send a notify
message to all the names in the list when a reboot occurs.
The client accepts the notify message matching with its
monitor entry and notifies the lockd. The lockd recovers all
the locks on the server.
( SR:8606218377 CR:JAGad87526 )
When an RPC server receives the last packet from the client,
it should flag the connection as dead and close the file
descriptor. The XPRT flag was set on the parent, but
checking is performed on the child's XPRT flag. The
SVC_FAILED flag was copied to the parent's XPRT flag and not
to the child's XPRT flag. The server develops a file
descriptor leak and eventually fails to process the client
requests when the process limit is reached.
Resolution:
Change to copy the parent XPRT flag to the child XPRT flag
once the connection is dead.
( SR:8606186978 CR:JAGad56188 )
CacheFS uses an array of 32 slots to keep track of the
segments of a file that have been cached. In case of demand
paging, data is brought in non-contiguously and up to 8K of
data is brought in each time. For a large binary, nocache
(not to cache) flag will be turned on if more than 32 slots
are needed. At unmount time, the cached partial file for
this binary will be nullified and subsequent access to this
binary will be made through the back file system.
Resolution:
The pagein block size is changed so that up to 32K of data
can be transferred from the back file system at a time.
Added code to merge adjacent allocation map entries.
Introduced a new CacheFS mount option "rpages" so that if
set, a binary will be read and populated in the cache the
first time it is loaded.
( SR:8606225370 CR:JAGad94457 )
The system panics with a "Data Page Fault" message when
trying to service a TCP mount request from a client. This
occurs because the kernel thread table is full on the
server.
Resolution:
Added code to the TCP mount service to reject the mount
request when the kernel thread table is full on the server.
( SR:8606230685 CR:JAGad99735 )
When a 32-bit user space application exists with a 64-bit
kernel, the syslog.log file fills up with
filegrp_destroy_metadata warnings. This is because the
cachefs_metadata data structure is different between the
user and kernel space.
Resolution:
The size of the data structure is made equal in both the
user and kernel space by adding padding bytes to the user
space data structure.
( SR:8606219527 CR:JAGad88667 )
The performance problem is caused by the automounter
generating a tremendous number of NIS packets over the
network. This is caused by a series of infinite recursive
calls to access a non-existent entry in the NIS map.
Resolution:
Infinite recursive calls were stopped by implementing a
function that checks whether the file causing the problem
was already opened.
( SR:8606226735 CR:JAGad95797 )
An HP-UX server does not allow a blank entry in the map,
where as a Solaris server does. When the /etc/services map
contains blank lines, a Solaris server creates blank entries
in the map. When the master server is Solaris and the slave
server is HP-UX, then the slave server clients are unable to
resolve the services after the blank entry in the map.
Resolution:
The check for a blank entry is removed on the server side.
( SR:8606237277 CR:JAGae06322 )
An NFS client does not return an error message when a users'
write(cp) operation exceeds its assigned quota limit on a
server's PV2 mounted file system.
Resolution:
If an NFS client exceeds the quota limit assigned on a
server's PV2 mounted file system during a write operation,
it will get a quota exceeded error message.
( SR:8606221217 CR:JAGad90351 )
If "control-c" is pressed within 75 seconds of issuing an
"ll" command across an automounted file system when the
server is down, the command is interrupted properly.
However, if another "ll" command is performed at least 75
seconds after the first "ll" command, the command hangs
forever. In both cases, a "server not found" message should
be returned and terminate the "ll" command if the command
is not manually terminated with "control-c" in 75 seconds.
Resolution:
Remove the stale autonode from the autonode list in autofs
after a forced remount.
( SR:8606221909 CR:JAGad91027 )
The system is running short of memory while autofs is trying
to get the memory to form the unmount list. autofs is
holding the spinlock and M_WAITOK is being passed as an
argument to the memory allocation function. When the system
is running short of memory, the memory allocation function
does not allow a spinlock to be held with M_WAITOK, and the
system panics.
Resolution:
While autofs is trying to get the memory to form the unmount
list, M_NOWAIT is passed instead of M_WAITOK as an argument
to the memory allocation function.
( SR:8606221102 CR:JAGad90236 )
The user account being reactivated remains locked on
trusted NIS+ clients.
Resolution:
NIS+ locks are now detected in the PAM module instead of the
NIS+ backend library.
( SR:8606172908 CR:JAGad42168 )
If an HANFS package has been failed back to its original
server in a period of less than five minutes after it was
failed over to a new node, and a given client has been
trying to access the package over TCP the entire time, then
the TCP connection the client will try to communicate over
will still exist on the original server host, but its state
will be stale relative to the client's TCP connection
endpoint. This results in multiple retransmissions over TCP,
timeouts in client-side RPC, and RPC call retries by NFS.
Resolution:
Have the client's RPC monitor its TCP connections more
intelligently, and initiate brand new TCP connections over a
different port when it receives indication that transport
has failed due to a peer reset by the server.
( SR:8606226170 CR:JAGad95241 )
Umount code was un-mounting the wrong entry in the mnttab.
Resolution:
Corrected umount behavior with CacheFS mounts.
( SR:8606229377 CR:JAGad98430 )
The AutoFS code would incorrectly set the MF_MOUNTED flag
for an AutoFS autonode. This could happen during an AutoFS
force remount or an AutoFS unmount operation.
Resolution:
Change AutoFS code to correctly set the MF_MOUNTED flag for
AutoFS force remount and AutoFS unmount operations.
( SR:8606204999 CR:JAGad74175 )
When the NIS+ server becomes busy and an NIS+ client
contacts the server, the client should create another handle
to contact the server since the server is invalid. When this
repeats more than a few iterations, the client uses the same
handle to contact the server again and again, even though
the server is busy. This is because the checking for a valid
server is done only if the number of failures is less than
the hard-coded limit.
Resolution:
Check whether or not the NIS+ server handle is valid before
checking for the number of failed iterations.
( SR:8606225120 CR:JAGad94209 )
rpc.rusersd supports a maximum of 180 users. rpc.rusersd
code did not check for this limit and thus caused the
program to abort when memory outside of the structures that
kept track of the user information was accessed.
Resolution:
In rpc.rusersd code, a check is made on the number of users
whose information is read and stored. If that number exceeds
180, further reading of user information is stopped.
PHNE_25625:
( SR:8606245747 CR:JAGae12206 )
rpc.lockd can core dump, with PHNE_24035 or PHNE_24910
installed, if a local variable has not been initialized.
Resolution:
Changed routine to initialize the local variable.
PHNE_24910:
( SR:8606184366 CR:JAGad53575 )
NFS incorrectly handles a case where the server thread
receiving requests from a client does not have its interface
setup before an incoming request is sent to it. This causes
an uninitialized function pointer to be called leading to
the execution of an instruction at address 0.
Resolution:
NFS now checks that the thread interface exists before
attempting to send a request to it. If it does not exist,
then the request is held until it does exist.
( SR:8606201620 CR:JAGad70794 )
HP NIS clients do not have the ability to switch binding
from their original server to an alternate server when the
original is not responding.
Resolution:
Modified the ypinit script to include a new option "-c" for
construction of an NIS servers list. The NIS servers list is
constructed by invoking "ypinit -c" and is stored in
/var/yp/binding/<domain_name>/ypservers. The list of NIS
servers should be in the order of preference that ypbind can
try to bind. The fix for JAGad70794 is not enabled unless
the ypinit script is copied from /usr/newconfig/usr/sbin to
/usr/sbin/. To backup the current ypinit script and enable
the new ypinit script, do the following steps:
mv /usr/sbin/ypinit /usr/sbin/ypinit.bak
cp -p /usr/newconfig/usr/sbin/ypinit /usr/sbin/ypinit
When disabling the fix for JAGad70794 and migrating back to
the previous ypinit script, the file
/var/yp/binding/<domain_name>/ypservers will need to be
deleted:
mv /usr/sbin/ypinit.bak /usr/sbin/ypinit
rm /var/yp/binding/<domain_name>/ypservers
( SR:8606147778 CR:JAGad17120 )
RPC client incorrectly handles a reply from an RPC server
rejecting an RPC call with call reject status RPC_MISMATCH
when the call specifies an unsupported RPC protocol version.
Resolution:
Fix RPC client rejected call error handler to correctly
route the reply handling of an RPC call rejected for
RPC_MISMATCH.
( SR:8606216548 CR:JAGad85717 )
The shadow password field is modified when a user changes
the password in an NIS+ trusted environment. The new value
causes getpwent to assume that password aging is enabled.
This also occurs when a new NIS+ user is added with SAM.
This is because certain values in the shadow password field
are interpreted incorrectly.
Resolution:
If an invalid character is encountered in the shadow
password field, set the field value so that password aging
is disabled.
( SR:8606205779 CR:JAGad74954 )
The problem occurs when /etc/exports contains either a large
number of -access options for an exported file system or a
large number of exported file systems. The recursive nature
of XDR calls causes the process to be unable to extend
thread stack size, which leads to the hanging/coring of
automountd.
Resolution:
Increase the default RPC thread stack size at time of thread
creation.
( SR:8606205013 CR:JAGad74189 )
The mount option 'grpid' does not return the correct 'gid'
value for the 'touch' command on HFS file systems, or for
'mkdir' command on HFS and VxFS file systems.
Resolution:
Modified NFS client code to set correct 'gid' value when
the file system is mounted with the 'grpid' mount option.
( SR:8606212242 CR:JAGad81430 )
The function called by passwd and nispasswd to search for an
entry in any NIS+ table skips any leading blank characters
in the search value. Then, passwd/nispasswd obtains the new
password from the user and updates the NIS+ tables with the
user name containing leading blanks.
Resolution:
Modified the function to include the leading blanks in the
search value.
( SR:8606187776 CR:JAGad56985 )
NFS/TCP operation on an NFS/TCP client can cause the system
to panic. Problem occurs when an uninitialized pointer
variable has garbage in it. The code attempts to free the
storage pointed to by that garbage.
Resolution:
Modified the code to initialize that variable to NULL.
Before attmpting to free the storage, the code now checks
the pointer's value against NULL.
( SR:8606220062 CR:JAGad89203 )
A thread walks off its stack due to a very large local stack
variable in svc_run.c, thereby resulting in the corruption
of unrelated memory.
Resolution:
The local declaration of the large stack variable is
unnecessary, and thus has been removed, since a global
declaration of the variable already exists.
( SR:8606219558 CR:JAGad88698 )
Default system attributes are not assigned to NIS+ users
that logon to trusted NIS+ clients for the first time.
Resolution:
The NIS+ name service switch library, libnss_nisplus.1, was
modified to set system default attributes for NIS+ users
that have never logged on to the trusted NIS+ client.
( SR:8606213087 CR:JAGad82274 )
The NFS server is not checking the permission bit before
performing file operations.
Resolution:
Modified NFS server code to return an error if the lock mode
bit is set incorrectly by checking the value before
performing file operations.
( SR:8606199444 CR:JAGad68631 )
There are some command-line options for yppasswdd:
"-nogecos -noshell -nopw -nohome". If these options are
used, then those fields may not be changed remotely using
passwd(1). The -nohome option was not documented in the
yppasswdd man page.
Resolution:
Added the -nohome option to the yppasswdd man page.
( SR:8606198866 CR:JAGad68055 )
Reading a large file (> 2GB) across a cachefs mount point
does not populate the cache because some of the data types
used are not 64-bit.
Resolution:
Modified code to enable caching large files (> 2GB).
( SR:8606169485 CR:JAGad38760 )
An NFS/TCP operation on an NFS/TCP client can cause the NFS
client to panic. Problem occurs when an NFS server requests
an orderly release of the connection while an NFS client is
setting the TCP_NODELAY option. The panic occurs when the
orderly release request from the NFS server arrives after
the NFS client has sent the TCP_NODELAY request to the
transport but before the transport has replied.
Resolution:
The NFS/TCP client code was modified to ignore orderly
release messages when waiting for a reply to a TCP_NODELAY
request.
PHNE_24035:
( SR:8606196567 CR:JAGad65770 )
The unmount command failed for a mounted cachefs type file
system when trying to unmount with AutoFS automountd. The
cachefs unmount command was missing a parameter that unmount
included.
Resolution:
Added the new parameter for the cachefs unmount command.
( SR:8606208446 CR:JAGad77633 )
The server's rpc.statd process sends the notify message to
the client's rpc.statd process with the server's hostname.
When the client's rpc.statd tries to match the hostname with
its monitor entry it checks for four possible names used to
mount the server: short name, long name, alias name, and IP
address. The current algorithm to check the short name and
long name in one step matches the wrong monitor entry, thus
causing problems in file lock recovery.
Resolution:
Separated the short name and long name checking into two
steps, checking only for short name and then checking for
long name.
( SR:8606207461 CR:JAGad76637 )
rpcbind and other RPC/XDR applications can be adversely
affected with SIGBUS.
Resolution:
Added code to address the problem.
( SR:8606164133 CR:JAGad33433 )
After a map transfer, ypxfr sends a YPPROC_CLEAR to the
local ypserv if ypxfr is not invoked with a "-c" option. If
the local host name is greater than 8 characters then the
call to bind_to_server() fails with the error "ypxfr:
bind_to_server clntudp_create error: RPC unknown host".
Resolution:
Increased the size of the array local_host_name from 8 to
MAXHOSTNAMELEN characters.
( SR:8606184904 CR:JAGad54106 )
rpc.lockd doesn't use NLM messages in the case of a loopback
mount with a hostname and directly modifies msg_q entries.
In the case of a loopback mount with an alias hostname, the
lockd mistakenly treats it as a loopback mount with a
hostname and modifies the msg_q entries which causes the
process to hang, as lockd doesn't find the entry when NLM
messages are received.
Resolution:
Added checking for whether the loopback mount is with a
hostname or alias hostname. Do not modify msg_q entries in
the case of a loopback mount with an alias hostname.
( SR:8606207826 CR:JAGad77003 )
The nisplus.server script does not stop the rpc.nispasswdd
process. The process name contains 14 characters, but the
"ps -e" command only returns 13 characters. Thus, if the
"/sbin/init.d/nisplus.server stop" command is issued, the
rpc.nispasswdd process continues to run. A subsequent
"/sbin/init.d/nisplus.server start" command will start a
second instance of this process.
Resolution:
Modified the nisplus.server script so that it obtains the
full 14-character process name for rpc.nispasswdd and the
process is killed properly.
( SR:8606181688 CR:JAGad50904 )
There is a window of time between the "Stop NFS client
subsystem" and "Unmount file systems" steps during system
shutdown. If there are active lofs mounts managed by AutoFS,
and an autofs unmount request is sent during this window,
shutdown will hang at the "Unmount file systems" step. This
is because automountd is killed at the "Stop NFS client
subsystem" step and thus cannot process mount and unmount
requests. The unmount request pends forever.
Resolution:
In the nfs.client script, prior to killing automountd,
increase the AutoFS unmount timeout to a very large value so
that no detrimental unmount requests are initiated before
shutdown concludes.
( SR:8606160777 CR:JAGad30096 )
The AutoFS automountd caused the unmount command to fail for
mounted hfs and cdrom type file systems.
Resolution:
Added the new parameter for the hfs and cdrom unmount
commands.
( SR:8606168123 CR:JAGad37405 )
NFS/TCP incorrectly handles the case where incoming messages
are being processed for a stream, as that stream is being
closed by the nfsd associated with TCP. In this case,
replies to messages being processed do not get sent down the
stream due to the close. However, the stream cannot complete
the close until all the messages have had replies sent.
Thus, the nfsd associated with TCP hangs in its close.
Resolution:
NFS/TCP changed to not wait for all messages to have replies
sent before closing a stream. No data is lost since messages
are retransmitted if the client didn't receive a reply.
( SR:8606203242 CR:JAGad72416 )
If there are biods running in the system, asynchronous reads
are done by the kernel on behalf of the reader process, and
asynchronous writes are done on behalf of the writer
process. The problem with this is that asynchronous write
requests will be enqueued faster than asynchronous read
requests, thus monopolizing the biods, and hence causing
starvation for the asynchronous read requests.
Resolution:
Modified the NFS read logic to avoid doing read-ahead
(asynchronous reads) if the biods are "too busy". However,
this fix is disabled by default. In order to enable it, the
kernel parameter 'async_read_avoidance_enabled' must be set
to one, by patching the vmunix file and rebooting, or by
patching the kernel image in memory. To patch the vmunix
file (survives a reboot), use this command:
echo 'async_read_avoidance_enabled?W 0d1' |
adb -w -k /stand/vmunix /dev/kmem
To patch the in-memory kernel (does not survive a reboot),
use this command:
echo 'async_read_avoidance_enabled/W 0d1' |
adb -w -k /stand/vmunix /dev/kmem
A kernel regeneration will require these steps to be done
again.
( SR:8606152534 CR: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:
Fix automountd so it returns the correct error code to the
kernel during unmount operations.
( SR:8606202370 CR:JAGad71544 )
When one process is holding a lock on a file, another
process is waiting for the lock on the same file, and the
two processes are killed at the same time, the lock remains
held by one of the processes.
Resolution:
In the CANCEL request handling routine local_cancel(), code
was added to delete the lock upon a CANCEL request if the
lock is found in the granted queue. This prevents the lock
from remaining after the process is killed.
( SR:8606204523 CR:JAGad73705 )
Until this patch, there was no support for cachefs for this
release of HP-UX.
Resolution:
Fixed numerous problems in the cachefs code so that cachefs
is now supported for this release of HP-UX. In order to
support cachefs, a new dependency is created on the mountall
command which is included in PHCO_24777. Both this patch and
PHCO_24777 must be installed on the system before enabling
cachefs.
( SR:8606176017 CR:JAGad45257 )
Due to a race condition in AutoFS, autonodes are getting
created with NULL mount flags. The affected AutoFS mount
points show empty directories. A system reboot is required
to clear the condition.
Resolution:
Modified the code to eliminate the race condition.
( SR:8606193515 CR:JAGad62727 )
For direct mounts, AutoFS did not wait for mounts to
complete when the direct mount point was accessed. This
triggered 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.
( SR:8606186548 CR:JAGad55752 )
File descriptors used by the TCP connections are released
too soon so that they confuse the polling thread to create
more file descriptors. The incorrectly created file
descriptors are never closed.
Resolution:
Modified code to keep the file descriptors until the RPC
service routine is totally complete.
( SR:8606146332 CR:JAGad15675 )
The code does synchronous I/O when the file is locked. This
means that the biods are bypassed and the I/O is performed
by the calling thread.
Resolution:
Do not set the RNOCACHE flag for a whole-file lock. Also,
flush the buffer cache for each lock/unlock request. Thus,
fresh data is read at lock time and all data is written
before releasing the lock. Note that for partial locks, the
behavior remains unchanged. This fix is disabled by default.
In order to enable it, the kernel flag 'nfs_new_lock_code'
needs to be turned on, by either patching the vmunix file
and rebooting, or by patching the kernel image in memory.
To patch the vmunix file (survives a reboot), use the
following commands:
echo 'nfs_new_lock_code?W 0d1' |
adb -w -k /stand/vmunix /dev/kmem
To patch the in-memory kernel (does not survive a reboot),
use the following commands:
echo 'nfs_new_lock_code/W 0d1' |
adb -w -k /stand/vmunix /dev/kmem
A kernel regeneration will require these steps be done
again.
PHNE_23502:
( SR:8606183171 CR:JAGad52387 )
Remote users can cause denial of RPC services.
Resolution:
In __svcauth_sys(), change the local variables strlen,
gid_len, and i from type integer to unsigned integer.
( SR:8606160596 CR:JAGad29916 )
Automountd will log "Rmdir" error messages to
/var/adm/automount.log even if automountd was started
without the "-T" option.
Resolution:
Add code to check for tracing before logging the error
message.
( SR:8606178618 CR:JAGad47845 )
Function nfs3rename() is implementing the "unlink-open-file"
semantics for the target name (when it exists), without
checking that it should only do so if the target is not a
directory.
Resolution:
Modify function nfs3rename() to only implement the
"unlink-open-file" semantics if the target name is not a
directory.
( SR:8606128739 CR:JAGac86286 )
The NFS server is TOC'ed when copying a file that is 25MB or
greater from an NFS client hard mounting to an NFS server.
After the NFS server comes back and the copy completes,
doing a cksum on both the local and remote file shows
different values for each file. Data is missing from the
remote file.
Resolution:
Record the write verifier before collecting the buffers, as
opposed to recording at sending time. Clear all of the
buffers' links every time when the buffers are not used.
( SR:8606140609 CR:JAGad09968 )
The function authunix_create() calls abort() if more than 16
groups are passed in args (gids).
Resolution:
Replaced abort() code with return(NULL). This prevents code
from dumping.
( SR:8606159451 CR:JAGad28779 )
Any thread sleeping interruptibly over interruptible NFS
mounts is susceptible to deadlock.
Resolution:
NFS threads are placed in a "nonstop" mode in sections of
code where non-interruptible resources are being held during
interruptible sleeps. There are five other patches which
must be installed to enable the "nonstop" mode: PHKL_24253,
PHKL_24254, PHKL_24255, PHKL_24256, and PHKL_24257.
( SR:8606180764 CR:JAGad49985 )
rpc.lockd rejects NLM_GRANTED_MSG when it is received out of
order with NLM_LOCK_RES (blocked).
Resolution:
Modified the processing algorithm for NLM_GRANTED_MSG. When
NLM_GRANTED_MSG is received ahead of NLM_LOCK_RES (blocked),
it is treated as if NLM_LOCK_RES (granted) was received.
( SR:8606180765 CR:JAGad49986 )
rpc.lockd ignores NLM_GRANTED_MSG when it is received out of
order with NLM_UNLOCK_RES.
Resolution:
Modified the processing algorithm for NLM_GRANTED_MSG. When
NLM_GRANTED_MSG is received ahead of NLM_UNLOCK_RES it is
treated as if NLM_UNLOCK_RES was received.
( SR:8606175862 CR:JAGad45102 )
When automounter triggers new mounts a symbolic link is
added to the automounter vnode. After the link was added the
modification time of the vnode was not being updated. Since
the modification time of the vnode never changed the rddir
cache was never invalidated.
Resolution:
Add code in the automounter to update the modification time
of the automounter vnodes whenever new symbolic links are
added.
( SR:8606175781 CR:JAGad45021 )
The calculation for determining the size of a file was using
an incorrect constant value.
Resolution:
NFS PV3 calculates the size occupied by a file. This
calculation was based on MAXBSIZE, which is 8192 instead of
DEV_BSIZE which is 1024. So it was eight times too high.
Changed this to base the calculation on DEV_BSIZE.
( SR:8606172747 CR:JAGad42007 )
When in trusted mode, the passwd change should always create
a fully qualified domain name even if one was not passed in
to the command.
Resolution:
New code was added to libnss_nisplus.1 to fully qualify
domain names if they are passed non-fully qualified.
( SR:8606165859 CR:JAGad35150 )
NFS incorrectly handles a return from a write operation
having a 0 status (NFS3_OK) and a count of bytes written
that is not reflective of the number of bytes actually
written (that is, a large negative number). By not rejecting
such values, it attempts to use the count of bytes written
to offset into memory causing the panic. A negative count of
bytes written is allowed because it is cast as signed.
Resolution:
NFS interprets the count of bytes written as unsigned, thus
eliminating any negative values.
( SR:8606199460 CR:JAGaa35208 )
Two very large global array variables in svc_run.c are being
allocated on the stack.
Resolution:
Removed the explicit initialization of global arrays.
( SR:8606174017 CR:JAGad43270 )
rpc.lockd puts the lock requests in msg_q while waiting for
a response from the server. If a process lock request for
file 'f1' is waiting in msg_q, subsequent lock requests from
the same process are ignored even if it is for a different
file. This can happen with multi-threaded processes where
two threads can send lock requests for two different files.
Resolution:
Added checking for the file handle in determining the
uniqueness of the lock. This enables lockd to distinguish
between requests from the same process for different files.
( SR:8606185238 CR:JAGad54440 )
When a client tries to unlock the first part of a locked
area in an NFS file, the whole lock is removed in the
server.
Resolution:
Fixed the delete_reclock() function to use the proper
argument when calling the delete_kernel_lock() function.
( SR:8606173363 CR:JAGad42623 )
The nfsstat man page does not have a description for the
badverfs, cantconn, nomem, interrupts, and cantsend fields.
Resolution:
Added these fields to the nfsstat man page.
( SR:8606178998 CR:JAGad48223 )
Server reads are occurring unnecessarily when a client is
only doing writes.
Resolution:
Removed the read operation that occurred before the write
operation.
( SR:8606176384 CR:JAGad45622 )
When booting a diskless Linux client, the process fails when
mounting the root file system. This happens because the
mount request uses the AUTH_NULL authentication type and
rpc.mountd does not allow this. The mount request fails with
a "permission denied" error.
Resolution:
Allowed rpc.mountd to accept mount requests with AUTH_NULL
authentication type.
( SR:1653311530 CR:JAGab46804 )
The manpage does not mention that fsirand is not supported
on a JFS file system.
Resolution:
Added a line to the "fsirand" man page stating that the
command is only supported on HFS filesystems.
( SR:8606169796 CR:JAGad39062 )
NFS incorrectly handles a machine name length that is
negative by not rejecting such a value and then attempting
to use it as an offset into an array. A negative machine
name length is allowed because it is declared as signed.
Resolution:
NFS interprets the machine name length as unsigned, thus
eliminating any negative values.
( SR:8606171662 CR:JAGad40926 )
Invalid host names in a root option's host list are not
handled correctly. They cause invalid entries to be created
in the root access host list for the corresponding
filesystem. The same type of defect occurs for the 'rw'
option.
Resolution:
Changed the logic that processes the 'root' and 'rw'
options, in order to completely ignore invalid host names.
( SR:8606179200 CR:JAGad48424 )
rpc.lockd logs messages to a log file by calling the LOG_MSG
function. The LOG_MSG function is being called with
incorrect parameters in lockd when it is logging message
related to CTRL-C interrupt processing.
Resolution:
Corrected the parameters being passed to the LOG_MSG
function.
( SR:8606169011 CR:JAGad38290 )
If an automounter map contains a mount point which is a
symbolic link that points to a non-existant directory,
automounter will hang.
Resolution:
During automounter initialization, add a check which will
ignore these invalid map entries and log an error message
to syslog.
( SR:8606179951 CR:JAGad49173 )
getservbyname() first searches the NIS map servi.bynp, which
can only resolve official service names. getservbyname()
never gets to call YP_ALL as a last resort to parse through
the other NIS map services.byname for the service alias.
Resolution:
If getservbyname() cannot resolve the service name passed to
it, call YP_ALL and parse through the NIS map
services.byname.
( SR:8606167053 CR:JAGad36339 )
NFS/TCP incorrectly handles the case where a new thread
cannot be created by the NFS TCP kernel daemon (nfsktcpd).
In such cases, it allows data to come in to be processed
though there is no thread to do such. On the close of the
data stream, the nfsd associated with TCP hangs waiting
for the incoming data to be processed.
Resolution:
NFS/TCP immediately closes the data stream when its
associated thread cannot be created, unless the reason for
the failure is that the maximum number of threads threshold
for nfsktcpd has been reached. In this case, the maximum
number of threads for nfsktcpd is dynamically increased
so that the thread can be created.
PHNE_23248:
( SR:8606188447 CR:JAGad57655 )
Automounted file systems do not behave properly with
PHNE_22878 installed. After the autofs timeout expires,
the file system should unmount automatically. This does not
happen properly, and duplicate entries appear in the
/etc/mnttab file every time the file system is accessed
after a timeout.
Resolution:
Corrected the logic in libautofs.a so that the automounted
file systems are unmounted properly and the /etc/mnttab
entries are removed.
PHNE_22878:
( SR:8606127276 CR:JAGac68822 )
The mount function returns the ENOENT error, without
checking the existence of the file in the mount table, when
the realpath() function does not find the path entry for the
file.
Resolution:
The function call "mount_enoent_error" is added to check the
existence of the file or the existence of the file name
entry in the mount table and return the error appropriately,
when the realpath() in the mount function fails with the
ENOENT error.
( SR:8606168603 CR:JAGad37881 )
CacheFS uses smaller block size and therefore smaller number
of pages to page in, than the underlying NFS block size.
Resolution:
Increased the maximum number of pages to page in.
( SR:8606166823 CR:JAGad36110 )
NFS function hpnfs_delay was coded incorrectly such that the
callout table could run out of entries under extremely high
loads and when the server is down.
Resolution:
Used a different address for each thread to wait on.
( SR:8606168604 CR:JAGad37882 )
Unlocking statements are missing in the kernel source code.
Also, there is a problem with unmounting in the user space.
Resolution:
Adding unlocking statements in kernel space unmount code
and correcting user space code to unmount proper mount
points.
( SR:8606135856 CR:JAGad04988 )
Race condition between mount and umount with ufs
filesystems.
Resolution:
Check VFS_MOUNTING flag in make_unmount_list and
get_hierarchical_mounts.
( SR:8606160808 CR:JAGad30127 )
The automountd code simply was not parsing the quota option
out of the options string.
Resolution:
Added a hasmntopt call to check for the quota option and set
the quota flag as needed.
( SR:8606168606 CR:JAGad37884 )
The error return values were not checked correctly and
CacheFS did not populate cache from subsequent page in
calls.
Resolution:
Corrected the corresponding error-checking statements.
( SR:8606166314 CR:JAGad35601 )
By masking SIGKILL and SIGSTOP it is not possible to kill an
NFS client process if the server goes down. Also, SIGKILL
and SIGSTOP are non-maskable signals in HP-UX, hence they
should not be masked.
Resolution:
Unmask SIGKILL and SIGSTOP in masked_sigs in the routine,
nfs_subr.c.
( SR:8606145476 CR:JAGad14812 )
When a client crashes and does recovery 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:
In recovery, server releases the lock information held by
the crashed client after waking up a client waiting for the
lock.
( SR:8606155843 CR:JAGad25155 )
When more than two processes execute the "id/group" command
simultaneously, the ypserv fails to return group information
to all processes.
Resolution:
A local data structure is defined where a buffer is
allocated to keep the nextkey or firstkey.
( SR:8606146885 CR:JAGad16228 )
The nfsd does a pmap_unset on startup before it looks for
running nfsd's. This leads to the situation where the new
nfsd's are running, but somewhere in the subseqeuent code
are conditions which are preventing nfsd from
re-registering. The formerly running nfsd's are not
completely useless, but all SG monitor scripts, which are
using "rpcinfo -u" will fail.
Resolution:
Modified the return errno from EINVAL to EIDRM which will
be used in nfsd.c.
( SR:8606159736 CR: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.
( SR:8606158230 CR:JAGad27560 )
Panic occurs when vfs lock is improperly unlocked and an
attempt to unlock it occurs.
Resolution:
Code modified to check the return value of vfs_lock and if
it is busy, sleep for some time and try to acquire the lock
again.
( SR:8606145517 CR:JAGad14853 )
When NFS is stopped and re-started, the nfsd transport table
can reach a state where the table is full and the new nfsd
daemons start faster than the old nfsd daemons stop. The
only way to get the table to a correct state is to reboot
the system.
Resolution:
Fixed the code that controls the nfsd transport table.
( SR:8606169239 CR:JAGad38515 )
The buffer cache does not return correct structure to
cacheFS, which leads to incorrect CacheFS statistics.
Resolution:
Do not count buffer cache results in CacheFS statistics,
read them from the local disk.
( SR:8606157592 CR:JAGad26923 )
In changing a public/secret key pair for the privileged user
of a given hostname on the master server with "newkey", this
command fails with error message, "ERROR, passwd differs
from login passwd". "Newkey" prompts for the root password
of the given hostname, but compares the given password
with the root password of the master server.
Resolution:
The prompt to ask the root password of the given hostname
is inserted if the password supplied is different from that
of the master server.
Enhancement:
No (superseded patches contained enhancements)
PHNE_28103:
Enhancements were delivered in a patch this one has
superseded. Please review the Defect Description
text for more information.
PHNE_27218:
This product update contains minor enhancements
required to enable the HP-UX Device IDs product.
JAGae14669 allows a root user to forcibly notify the
NFS server's rpc.lockd to discard all locks and
cached port information for a specified client.
SR:
1653311530 8606127276 8606128739 8606135856 8606140609
8606145476 8606145517 8606146332 8606146885 8606147221
8606147778 8606152534 8606155843 8606157592 8606158230
8606159451 8606159736 8606160596 8606160777 8606160808
8606164133 8606165859 8606166314 8606166823 8606167053
8606168123 8606168603 8606168604 8606168606 8606169011
8606169239 8606169485 8606169796 8606171662 8606172747
8606172908 8606173363 8606174017 8606175781 8606175862
8606176017 8606176384 8606178618 8606178998 8606179200
8606179951 8606180764 8606180765 8606180770 8606181688
8606183171 8606184366 8606184904 8606185238 8606186548
8606186978 8606187776 8606188447 8606188628 8606193515
8606196567 8606198866 8606199444 8606199460 8606201620
8606202370 8606203242 8606204523 8606204999 8606205013
8606205779 8606207461 8606207826 8606208446 8606212242
8606213087 8606216548 8606218377 8606219527 8606219558
8606220062 8606221102 8606221217 8606221909 8606224657
8606225120 8606225370 8606226170 8606226735 8606226778
8606228306 8606229377 8606230660 8606230685 8606232532
8606233931 8606234034 8606234968 8606235172 8606237277
8606242021 8606244127 8606245329 8606245747 8606245876
8606248269 8606248624 8606248870 8606249559 8606249576
8606254087 8606255006 8606256845 8606256846 8606257219
8606257688 8606259713 8606259831 8606260873 8606264087
8606264317 8606265228 8606271227 8606274502 8606274555
8606276016 8606276334 8606277106 8606281883 8606286563
8606288394
Patch Files:
NFS.KEY-CORE,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/sbin/newkey
NFS.NFS-64ALIB,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/lib/pa20_64/libnsl.a
NFS.NFS-64SLIB,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/lib/pa20_64/libnsl.1
/usr/lib/pa20_64/libnss_nis.1
/usr/lib/pa20_64/libnss_nisplus.1
NFS.NFS-CLIENT,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/sbin/fs/cachefs/fsck
/sbin/fs/cachefs/mount
/sbin/fs/cachefs/umount
/sbin/init.d/nfs.client
/usr/lib/netsvc/fs/autofs/automount
/usr/lib/netsvc/fs/autofs/automountd
/usr/lib/netsvc/fs/automount/automount
/usr/sbin/cfsadmin
NFS.NFS-CORE,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/sbin/fs/nfs/mount
/sbin/fs/nfs/umount
/sbin/init.d/nfs.core
/usr/sbin/clear_locks
/usr/sbin/nfsconfcol
/usr/sbin/rpc.lockd
/usr/sbin/rpc.statd
/usr/sbin/setoncenv
NFS.NFS-ENG-A-MAN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/share/man/man1.Z/domainname.1
/usr/share/man/man1m.Z/cfsadmin.1m
/usr/share/man/man1m.Z/clear_locks.1m
/usr/share/man/man1m.Z/fsirand.1m
/usr/share/man/man1m.Z/mount_cachefs.1m
/usr/share/man/man1m.Z/mountd.1m
/usr/share/man/man1m.Z/nfsstat.1m
/usr/share/man/man1m.Z/rpc.mountd.1m
/usr/share/man/man1m.Z/setoncenv.1m
/usr/share/man/man1m.Z/ypbind.1m
/usr/share/man/man1m.Z/ypinit.1m
/usr/share/man/man1m.Z/yppasswdd.1m
/usr/share/man/man1m.Z/ypserv.1m
/usr/share/man/man1m.Z/ypxfrd.1m
/usr/share/man/man4.Z/nsswitch.conf.4
/usr/share/man/man4.Z/switch.4
NFS.NFS-PRG,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/bin/rpcgen
/usr/lib/libnsl.a
NFS.NFS-SERVER,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/lib/netsvc/rusers/rpc.rusersd
/usr/sbin/exportfs
/usr/sbin/nfsd
/usr/sbin/rpc.mountd
NFS.NFS-SHLIBS,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/lib/libnsl.1
/usr/lib/libnss_nis.1
NFS.NIS-CLIENT,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/sbin/init.d/nis.client
/usr/lib/netsvc/yp/ypbind
NFS.NIS-CORE,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/bin/domainname
/usr/sbin/ypxfr
NFS.NIS-SERVER,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/lib/netsvc/yp/rpc.yppasswdd
/usr/lib/netsvc/yp/ypserv
/usr/newconfig/usr/sbin/ypinit
/usr/sbin/ypxfrd
NFS.NISPLUS-CORE,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/sbin/init.d/nisplus.server
/usr/lib/libnss_nisplus.1
NFS.NFS-KRN,fr=B.11.11,fa=HP-UX_B.11.11_32,v=HP:
/usr/conf/lib/libautofs.a
/usr/conf/lib/libcachefs.a
/usr/conf/lib/libnfs.a
/usr/conf/lib/librpc.a
NFS.NFS-KRN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP:
/usr/conf/lib/libautofs.a
/usr/conf/lib/libcachefs.a
/usr/conf/lib/libnfs.a
/usr/conf/lib/librpc.a
what(1) Output:
NFS.KEY-CORE,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/sbin/newkey:
newkey.c $Date: 2001/02/21 17:16:16 $Revision: r11.1
1/1 PATCH_11.11 (PHNE_22878)
NFS.NFS-64ALIB,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/lib/pa20_64/libnsl.a:
stubs.c $Date: 2001/11/15 14:55:32 $Revision: r11.11
/1 PATCH_11.11 (PHNE_24910)
read_config.c $Date: 2001/05/31 10:27:05 $Revision:
r11.11/1 PATCH_11.11 (PHNE_23502)
nis_rpc.c $Date: 2002/04/16 10:59:37 $Revision: r11.
11/1 PATCH_11.11 (PHNE_25627)
nis_subr.c $Date: 2001/11/15 14:55:32 $Revision: r11
.11/1 PATCH_11.11 (PHNE_24910)
auth_sys.c $Date: 2001/05/29 13:43:18 $Revision: r11
.11/1 PATCH_11.11 (PHNE_23502)
clnt_perror.c $Date: 2002/12/19 16:30:04 $Revision:
r11.11/1 PATCH_11.11 (PHNE_28103)
rpc_comdata.c $Date: 2001/05/29 13:43:40 $Revision:
r11.11/1 PATCH_11.11 (PHNE_23502)
svc_auth_sys.c $Date: 2002/08/01 17:09:23 $Revision:
r11.11/3 PATCH_11.11 (PHNE_27218)
svc_run.c $Date: 2002/04/16 11:00:14 $Revision: r11.
11/3 PATCH_11.11 (PHNE_25627)
svc_vc.c $Date: 2002/08/01 17:09:35 $Revision: r11.1
1/4 PATCH_11.11 (PHNE_27218)
xdr_array.c $Date: 2002/09/06 11:32:29 $Revision: r1
1.11/1 PATCH_11.11 (PHNE_27218)
xdr_rec.c $Date: 2001/08/13 16:52:30 $Revision: r11.
11/2 PATCH_11.11 (PHNE_24035)
yp_bind.c $Date: 2002/12/19 16:30:16 $Revision: r11.
11/1 PATCH_11.11 (PHNE_28103)
yp_match.c $Date: 2002/12/19 16:30:27 $Revision: r11
.11/1 PATCH_11.11 (PHNE_28103)
NFS.NFS-64SLIB,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/lib/pa20_64/libnsl.1:
stubs.c $Date: 2001/11/15 14:55:32 $Revision: r11.11
/1 PATCH_11.11 (PHNE_24910)
read_config.c $Date: 2001/05/31 10:27:05 $Revision:
r11.11/1 PATCH_11.11 (PHNE_23502)
nis_rpc.c $Date: 2002/04/16 10:59:37 $Revision: r11.
11/1 PATCH_11.11 (PHNE_25627)
nis_subr.c $Date: 2001/11/15 14:55:32 $Revision: r11
.11/1 PATCH_11.11 (PHNE_24910)
auth_sys.c $Date: 2001/05/29 13:43:18 $Revision: r11
.11/1 PATCH_11.11 (PHNE_23502)
clnt_perror.c $Date: 2002/12/19 16:30:04 $Revision:
r11.11/1 PATCH_11.11 (PHNE_28103)
rpc_comdata.c $Date: 2001/05/29 13:43:40 $Revision:
r11.11/1 PATCH_11.11 (PHNE_23502)
svc_auth_sys.c $Date: 2002/08/01 17:09:23 $Revision:
r11.11/3 PATCH_11.11 (PHNE_27218)
svc_run.c $Date: 2002/04/16 11:00:14 $Revision: r11.
11/3 PATCH_11.11 (PHNE_25627)
svc_vc.c $Date: 2002/08/01 17:09:35 $Revision: r11.1
1/4 PATCH_11.11 (PHNE_27218)
xdr_array.c $Date: 2002/09/06 11:32:29 $Revision: r1
1.11/1 PATCH_11.11 (PHNE_27218)
xdr_rec.c $Date: 2001/08/13 16:52:30 $Revision: r11.
11/2 PATCH_11.11 (PHNE_24035)
yp_bind.c $Date: 2002/12/19 16:30:16 $Revision: r11.
11/1 PATCH_11.11 (PHNE_28103)
yp_match.c $Date: 2002/12/19 16:30:27 $Revision: r11
.11/1 PATCH_11.11 (PHNE_28103)
/usr/lib/pa20_64/libnss_nis.1:
getservent.c $Date: 2001/05/29 13:45:22 $Revision: r
11.11/1 PATCH_11.11 (PHNE_23502)
/usr/lib/pa20_64/libnss_nisplus.1:
getpwnam.c $Date: 2001/11/15 14:55:32 $Revision: r11
.11/1 PATCH_11.11 (PHNE_24910)
ngetprpwent.c $Date: 2002/04/16 11:01:33 $Revision:
r11.11/3 PATCH_11.11 (PHNE_25627)
NFS.NFS-CLIENT,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/sbin/fs/cachefs/fsck:
subr.c $Date: 2001/11/15 14:55:32 $Revision: r11.11/
1 PATCH_11.11 (PHNE_24910)
res.c $Date: 2001/11/15 14:55:32 $Revision: r11.11/2
PATCH_11.11 (PHNE_24910)
fsck.c $Date: 2002/04/16 10:58:17 $Revision: r11.11/
3 PATCH_11.11 (PHNE_25627)
/sbin/fs/cachefs/mount:
subr.c $Date: 2001/11/15 14:55:32 $Revision: r11.11/
1 PATCH_11.11 (PHNE_24910)
mount.c $Date: 2002/04/16 10:59:04 $Revision: r11.11
/3 PATCH_11.11 (PHNE_25627)
/sbin/fs/cachefs/umount:
subr.c $Date: 2001/11/15 14:55:32 $Revision: r11.11/
1 PATCH_11.11 (PHNE_24910)
umount.c $Date: 2001/08/13 16:52:30 $Revision: r11.1
1/2 PATCH_11.11 (PHNE_24035)
/sbin/init.d/nfs.client:
nfs.client $Date: 2002/08/01 17:11:27 $Revision: r11
.11/2 PATCH_11.11 (PHNE_27218)
/usr/lib/netsvc/fs/autofs/automount:
auto_mnttab.c $Date: 2002/08/01 17:08:43 $Revision:
r11.11/1 PATCH_11.11 (PHNE_27218)
/usr/lib/netsvc/fs/autofs/automountd:
autod_main.c $Date: 2002/08/01 17:08:53 $Revision: r
11.11/1 PATCH_11.11 (PHNE_27218)
autod_mount.c $Date: 2002/09/19 15:03:03 $Revision:
r11.11/5 PATCH_11.11 (PHNE_27218)
autod_nfs.c $Date: 2002/12/19 16:29:52 $Revision: r1
1.11/3 PATCH_11.11 (PHNE_28103)
auto_mnttab.c $Date: 2002/08/01 17:08:43 $Revision:
r11.11/1 PATCH_11.11 (PHNE_27218)
/usr/lib/netsvc/fs/automount/automount:
auto_main.c $Date: 2002/12/19 16:29:41 $Revision: r1
1.11/2 PATCH_11.11 (PHNE_28103)
auto_look.c $Date: 2002/04/16 10:51:48 $Revision: r1
1.11/2 PATCH_11.11 (PHNE_25627)
auto_node.c $Date: 2002/04/16 10:53:35 $Revision: r1
1.11/2 PATCH_11.11 (PHNE_25627)
auto_mount.c $Date: 2002/12/19 16:29:29 $Revision: r
11.11/1 PATCH_11.11 (PHNE_28103)
/usr/sbin/cfsadmin:
subr.c $Date: 2001/11/15 14:55:32 $Revision: r11.11/
1 PATCH_11.11 (PHNE_24910)
cfsadmin.c $Date: 2001/11/15 14:55:32 $Revision: r11
.11/2 PATCH_11.11 (PHNE_24910)
NFS.NFS-CORE,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/sbin/fs/nfs/mount:
bindresvport.c $Date: 2002/08/01 17:09:56 $Revision:
r11.11/1 PATCH_11.11 (PHNE_27218)
/sbin/fs/nfs/umount:
umount.c $Date: 2002/04/16 11:04:40 $Revision: r11.1
1/1 PATCH_11.11 (PHNE_25627)
bindresvport.c $Date: 2002/08/01 17:09:56 $Revision:
r11.11/1 PATCH_11.11 (PHNE_27218)
/sbin/init.d/nfs.core:
nfs.core $Date: 2002/08/01 17:11:07 $Revision: r11.1
1/1 PATCH_11.11 (PHNE_27218)
/usr/sbin/clear_locks:
clear_locks.c $Date: 2002/08/01 17:09:46 $Revision:
r11.11/1 PATCH_11.11 (PHNE_27218)
/usr/sbin/nfsconfcol:
nfsconfcol $Date: 2002/08/01 17:11:17 $Revision: r11
.11/1 PATCH_11.11 (PHNE_27218)
/usr/sbin/rpc.lockd:
prot_lock.c $Date: 2001/08/13 16:52:30 $Revision: r1
1.11/3 PATCH_11.11 (PHNE_24035)
prot_pnlm.c $Date: 2002/08/01 17:10:36 $Revision: r1
1.11/1 PATCH_11.11 (PHNE_27218)
prot_msg.c $Date: 2002/08/01 17:10:26 $Revision: r11
.11/2 PATCH_11.11 (PHNE_27218)
prot_proc.c $Date: 2002/03/28 15:18:32 $Revision: r1
1.11/3 PATCH_11.11 (PHNE_25625)
prot_priv.c $Date: 2001/02/21 17:20:30 $Revision: r1
1.11/1 PATCH_11.11 (PHNE_22878)
prot_share.c $Date: 2001/08/28 11:58:50 $Revision: r
11.11/1 PATCH_11.11 (PHNE_24035)
sm_monitor.c $Date: 2002/08/01 17:10:46 $Revision: r
11.11/2 PATCH_11.11 (PHNE_27218)
pmap.c $Date: 2002/08/01 17:10:16 $Revision: r11.11/
1 PATCH_11.11 (PHNE_27218)
udp.c $Date: 2002/08/27 12:41:33 $Revision: r11.11/2
PATCH_11.11 (PHNE_27218)
svc_dg1.c $Date: 2001/08/28 11:59:21 $Revision: r11.
11/1 PATCH_11.11 (PHNE_24035)
/usr/sbin/rpc.statd:
sm_svc.c $Date: 2002/04/16 11:04:01 $Revision: r11.1
1/2 PATCH_11.11 (PHNE_25627)
sm_proc.c $Date: 2002/04/16 11:02:21 $Revision: r11.
11/2 PATCH_11.11 (PHNE_25627)
sm_statd.c $Date: 2002/04/16 11:03:30 $Revision: r11
.11/2 PATCH_11.11 (PHNE_25627)
udp.c $Date: 2002/08/27 12:41:33 $Revision: r11.11/2
PATCH_11.11 (PHNE_27218)
pmap.c $Date: 2002/08/01 17:10:16 $Revision: r11.11/
1 PATCH_11.11 (PHNE_27218)
/usr/sbin/setoncenv:
setoncenv.c $Date: 2001/06/01 14:42:38 $Revision: r1
1.11/1 PATCH_11.11 (PHNE_23502)
NFS.NFS-ENG-A-MAN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/share/man/man1.Z/domainname.1:
None
/usr/share/man/man1m.Z/cfsadmin.1m:
None
/usr/share/man/man1m.Z/clear_locks.1m:
None
/usr/share/man/man1m.Z/fsirand.1m:
None
/usr/share/man/man1m.Z/mount_cachefs.1m:
None
/usr/share/man/man1m.Z/mountd.1m:
None
/usr/share/man/man1m.Z/nfsstat.1m:
None
/usr/share/man/man1m.Z/rpc.mountd.1m:
None
/usr/share/man/man1m.Z/setoncenv.1m:
None
/usr/share/man/man1m.Z/ypbind.1m:
None
/usr/share/man/man1m.Z/ypinit.1m:
None
/usr/share/man/man1m.Z/yppasswdd.1m:
None
/usr/share/man/man1m.Z/ypserv.1m:
None
/usr/share/man/man1m.Z/ypxfrd.1m:
None
/usr/share/man/man4.Z/nsswitch.conf.4:
None
/usr/share/man/man4.Z/switch.4:
None
NFS.NFS-PRG,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/bin/rpcgen:
rpc_svcout.c $Date: 2002/04/16 11:06:10 $Revision: r
11.11/1 PATCH_11.11 (PHNE_25627)
/usr/lib/libnsl.a:
stubs.c $Date: 2001/11/15 14:55:32 $Revision: r11.11
/1 PATCH_11.11 (PHNE_24910)
read_config.c $Date: 2001/05/31 10:27:05 $Revision:
r11.11/1 PATCH_11.11 (PHNE_23502)
nis_rpc.c $Date: 2002/04/16 10:59:37 $Revision: r11.
11/1 PATCH_11.11 (PHNE_25627)
nis_subr.c $Date: 2001/11/15 14:55:32 $Revision: r11
.11/1 PATCH_11.11 (PHNE_24910)
auth_sys.c $Date: 2001/05/29 13:43:18 $Revision: r11
.11/1 PATCH_11.11 (PHNE_23502)
clnt_perror.c $Date: 2002/12/19 16:30:04 $Revision:
r11.11/1 PATCH_11.11 (PHNE_28103)
rpc_comdata.c $Date: 2001/05/29 13:43:40 $Revision:
r11.11/1 PATCH_11.11 (PHNE_23502)
svc_auth_sys.c $Date: 2002/08/01 17:09:23 $Revision:
r11.11/3 PATCH_11.11 (PHNE_27218)
svc_run.c $Date: 2002/04/16 11:00:14 $Revision: r11.
11/3 PATCH_11.11 (PHNE_25627)
svc_vc.c $Date: 2002/08/01 17:09:35 $Revision: r11.1
1/4 PATCH_11.11 (PHNE_27218)
xdr_array.c $Date: 2002/09/06 11:32:29 $Revision: r1
1.11/1 PATCH_11.11 (PHNE_27218)
xdr_rec.c $Date: 2001/08/13 16:52:30 $Revision: r11.
11/2 PATCH_11.11 (PHNE_24035)
yp_bind.c $Date: 2002/12/19 16:30:16 $Revision: r11.
11/1 PATCH_11.11 (PHNE_28103)
yp_match.c $Date: 2002/12/19 16:30:27 $Revision: r11
.11/1 PATCH_11.11 (PHNE_28103)
NFS.NFS-SERVER,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/lib/netsvc/rusers/rpc.rusersd:
rpc.ruserd.c $Date: 2002/04/16 11:05:40 $Revision: r
11.11/1 PATCH_11.11 (PHNE_25627)
/usr/sbin/exportfs:
exportfs.c $Date: 2001/05/29 13:45:42 $Revision: r11
.11/1 PATCH_11.11 (PHNE_23502)
/usr/sbin/nfsd:
nfsd.c $Date: 2001/08/28 11:58:31 $Revision: r11.11/
3 PATCH_11.11 (PHNE_24035)
/usr/sbin/rpc.mountd:
rpc.mountd.c $Date: 2002/08/01 17:10:06 $Revision: r
11.11/3 PATCH_11.11 (PHNE_27218)
NFS.NFS-SHLIBS,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/lib/libnsl.1:
stubs.c $Date: 2001/11/15 14:55:32 $Revision: r11.11
/1 PATCH_11.11 (PHNE_24910)
read_config.c $Date: 2001/05/31 10:27:05 $Revision:
r11.11/1 PATCH_11.11 (PHNE_23502)
nis_rpc.c $Date: 2002/04/16 10:59:37 $Revision: r11.
11/1 PATCH_11.11 (PHNE_25627)
nis_subr.c $Date: 2001/11/15 14:55:32 $Revision: r11
.11/1 PATCH_11.11 (PHNE_24910)
auth_sys.c $Date: 2001/05/29 13:43:18 $Revision: r11
.11/1 PATCH_11.11 (PHNE_23502)
clnt_perror.c $Date: 2002/12/19 16:30:04 $Revision:
r11.11/1 PATCH_11.11 (PHNE_28103)
rpc_comdata.c $Date: 2001/05/29 13:43:40 $Revision:
r11.11/1 PATCH_11.11 (PHNE_23502)
svc_auth_sys.c $Date: 2002/08/01 17:09:23 $Revision:
r11.11/3 PATCH_11.11 (PHNE_27218)
svc_run.c $Date: 2002/04/16 11:00:14 $Revision: r11.
11/3 PATCH_11.11 (PHNE_25627)
svc_vc.c $Date: 2002/08/01 17:09:35 $Revision: r11.1
1/4 PATCH_11.11 (PHNE_27218)
xdr_array.c $Date: 2002/09/06 11:32:29 $Revision: r1
1.11/1 PATCH_11.11 (PHNE_27218)
xdr_rec.c $Date: 2001/08/13 16:52:30 $Revision: r11.
11/2 PATCH_11.11 (PHNE_24035)
yp_bind.c $Date: 2002/12/19 16:30:16 $Revision: r11.
11/1 PATCH_11.11 (PHNE_28103)
yp_match.c $Date: 2002/12/19 16:30:27 $Revision: r11
.11/1 PATCH_11.11 (PHNE_28103)
/usr/lib/libnss_nis.1:
getservent.c $Date: 2001/05/29 13:45:22 $Revision: r
11.11/1 PATCH_11.11 (PHNE_23502)
NFS.NIS-CLIENT,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/sbin/init.d/nis.client:
nis.client $Date: 2002/08/01 17:11:37 $Revision: r11
.11/2 PATCH_11.11 (PHNE_27218)
/usr/lib/netsvc/yp/ypbind:
ypbind.c $Date: 2001/11/15 14:55:32 $Revision: r11.1
1/1 PATCH_11.11 (PHNE_24910)
NFS.NIS-CORE,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/bin/domainname:
domainname.c $Date: 2002/12/19 16:30:38 $Revision: r
11.11/1 PATCH_11.11 (PHNE_28103)
/usr/sbin/ypxfr:
ypxfr.c $Date: 2001/08/13 16:52:30 $Revision: r11.11
/1 PATCH_11.11 (PHNE_24035)
NFS.NIS-SERVER,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/lib/netsvc/yp/rpc.yppasswdd:
rpc.ypassd.c $Date: 2002/09/19 12:56:41 $Revision: r
11.11/1 PATCH_11.11 (PHNE_27218)
/usr/lib/netsvc/yp/ypserv:
ypserv_map.c $Date: 2002/12/19 16:31:00 $Revision: r
11.11/1 PATCH_11.11 (PHNE_28103)
ypserv_dbmtrak.c $Date: 2002/04/16 11:06:43 $Revisio
n: r11.11/2 PATCH_11.11 (PHNE_25627)
/usr/newconfig/usr/sbin/ypinit:
ypinit $Date: 2002/12/19 16:30:49 $Revision: r11.11/
2 PATCH_11.11 (PHNE_28103)
/usr/sbin/ypxfrd:
ypxfrd_subr.c $Date: 2002/12/19 16:31:12 $Revision:
r11.11/1 PATCH_11.11 (PHNE_28103)
NFS.NISPLUS-CORE,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/sbin/init.d/nisplus.server:
nisplus.server $Date: 2002/08/01 17:11:48 $Revision:
r11.11/2 PATCH_11.11 (PHNE_27218)
/usr/lib/libnss_nisplus.1:
getpwnam.c $Date: 2001/11/15 14:55:32 $Revision: r11
.11/1 PATCH_11.11 (PHNE_24910)
ngetprpwent.c $Date: 2002/04/16 11:01:33 $Revision:
r11.11/3 PATCH_11.11 (PHNE_25627)
NFS.NFS-KRN,fr=B.11.11,fa=HP-UX_B.11.11_32,v=HP:
/usr/conf/lib/libautofs.a:
hpautofs.c $Date: 2002/08/14 17:24:17 $Revision: r11
.11/3 PATCH_11.11 (PHNE_27218)
auto_vnops.c $Date: 2002/08/01 17:06:56 $Revision: r
11.11/7 PATCH_11.11 (PHNE_27218)
auto_vfsops.c $Date: 2001/02/21 17:12:20 $Revision:
r11.11/1 PATCH_11.11 (PHNE_22878)
auto_subr.c $Date: 2002/10/11 13:42:35 $Revision: r1
1.11/9 PATCH_11.11 (PHNE_27218)
/usr/conf/lib/libcachefs.a:
hpcachefs.c $Date: 2001/11/15 14:55:32 $Revision: r1
1.11/2 PATCH_11.11 (PHNE_24910)
cachefs_vnops.c $Date: 2002/04/16 10:45:09 $Revision
: r11.11/4 PATCH_11.11 (PHNE_25627)
cachefs_vfsops.c $Date: 2002/04/16 10:44:32 $Revisio
n: r11.11/4 PATCH_11.11 (PHNE_25627)
cachefs_subr.c $Date: 2002/04/16 10:43:47 $Revision:
r11.11/3 PATCH_11.11 (PHNE_25627)
cachefs_strict.c $Date: 2001/08/13 16:52:30 $Revisio
n: r11.11/1 PATCH_11.11 (PHNE_24035)
cachefs_singlewrc.c $Date: 2001/08/13 16:52:30 $Revi
sion: r11.11/1 PATCH_11.11 (PHNE_24035)
cachefs_resource.c $Date: 2001/11/15 14:55:32 $Revis
ion: r11.11/2 PATCH_11.11 (PHNE_24910)
cachefs_noopc.c $Date: 2001/08/13 16:52:30 $Revision
: r11.11/1 PATCH_11.11 (PHNE_24035)
cachefs_module.c $Date: 2001/08/13 16:52:30 $Revisio
n: r11.11/1 PATCH_11.11 (PHNE_24035)
cachefs_log.c $Date: 2001/11/15 14:55:32 $Revision:
r11.11/1 PATCH_11.11 (PHNE_24910)
cachefs_fscache.c $Date: 2002/04/16 10:43:13 $Revisi
on: r11.11/3 PATCH_11.11 (PHNE_25627)
cachefs_filegrp.c $Date: 2001/08/13 16:52:30 $Revisi
on: r11.11/1 PATCH_11.11 (PHNE_24035)
cachefs_dir.c $Date: 2001/11/15 14:55:32 $Revision:
r11.11/2 PATCH_11.11 (PHNE_24910)
cachefs_cod.c $Date: 2001/08/13 16:52:30 $Revision:
r11.11/1 PATCH_11.11 (PHNE_24035)
cachefs_cnode.c $Date: 2001/11/15 14:55:32 $Revision
: r11.11/2 PATCH_11.11 (PHNE_24910)
/usr/conf/lib/libnfs.a:
klm_lckmgr.c $Date: 2002/09/06 12:30:43 $Revision: r
11.11/3 PATCH_11.11 (PHNE_27218)
nfs_vnops.c $Date: 2001/11/15 14:55:32 $Revision: r1
1.11/4 PATCH_11.11 (PHNE_24910)
nfs_subr.c $Date: 2001/05/29 13:35:59 $Revision: r11
.11/2 PATCH_11.11 (PHNE_23502)
nfs_dispatch.c $Date: 2001/02/21 17:04:14 $Revision:
r11.11/1 PATCH_11.11 (PHNE_22878)
nfs3_server.c $Date: 2002/08/01 17:07:39 $Revision:
r11.11/2 PATCH_11.11 (PHNE_27218)
nfs_common.c $Date: 2001/05/29 13:35:26 $Revision: r
11.11/1 PATCH_11.11 (PHNE_23502)
nfs_client.c $Date: 2001/05/29 13:34:40 $Revision: r
11.11/1 PATCH_11.11 (PHNE_23502)
nfs3_vnops.c $Date: 2002/08/01 17:07:50 $Revision: r
11.11/6 PATCH_11.11 (PHNE_27218)
hpnfs_vnops.c $Date: 2002/08/01 17:07:28 $Revision:
r11.11/5 PATCH_11.11 (PHNE_27218)
hpnfs_util.c $Date: 2001/02/26 13:19:29 $Revision: r
11.11/1 PATCH_11.11 (PHNE_22878)
/usr/conf/lib/librpc.a:
tcp_svc.c $Date: 2002/04/16 10:50:55 $Revision: r11.
11/2 PATCH_11.11 (PHNE_25627)
svc_gen.c $Date: 2001/02/21 17:08:51 $Revision: r11.
11/1 PATCH_11.11 (PHNE_22878)
svc_cots.c $Date: 2002/08/01 17:08:31 $Revision: r11
.11/2 PATCH_11.11 (PHNE_27218)
svc_clts.c $Date: 2002/08/01 17:08:21 $Revision: r11
.11/1 PATCH_11.11 (PHNE_27218)
svc_authu.c $Date: 2001/05/29 13:38:14 $Revision: r1
1.11/1 PATCH_11.11 (PHNE_23502)
rpcmod.c $Date: 2001/11/15 14:55:32 $Revision: r11.1
1/2 PATCH_11.11 (PHNE_24910)
rpc_tcp.c $Date: 2001/05/29 13:41:02 $Revision: r11.
11/1 PATCH_11.11 (PHNE_23502)
rpc_prot.c $Date: 2001/11/15 14:55:32 $Revision: r11
.11/1 PATCH_11.11 (PHNE_24910)
clnt_gen.c $Date: 2002/08/01 17:08:10 $Revision: r11
.11/1 PATCH_11.11 (PHNE_27218)
clnt_cots.c $Date: 2002/04/16 10:48:41 $Revision: r1
1.11/3 PATCH_11.11 (PHNE_25627)
clnt_clts.c $Date: 2001/05/29 13:37:41 $Revision: r1
1.11/1 PATCH_11.11 (PHNE_23502)
NFS.NFS-KRN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP:
/usr/conf/lib/libautofs.a:
hpautofs.c $Date: 2002/08/14 17:24:17 $Revision: r11
.11/3 PATCH_11.11 (PHNE_27218)
auto_vnops.c $Date: 2002/08/01 17:06:56 $Revision: r
11.11/7 PATCH_11.11 (PHNE_27218)
auto_vfsops.c $Date: 2001/02/21 17:12:20 $Revision:
r11.11/1 PATCH_11.11 (PHNE_22878)
auto_subr.c $Date: 2002/10/11 13:42:35 $Revision: r1
1.11/9 PATCH_11.11 (PHNE_27218)
/usr/conf/lib/libcachefs.a:
hpcachefs.c $Date: 2001/11/15 14:55:32 $Revision: r1
1.11/2 PATCH_11.11 (PHNE_24910)
cachefs_vnops.c $Date: 2002/04/16 10:45:09 $Revision
: r11.11/4 PATCH_11.11 (PHNE_25627)
cachefs_vfsops.c $Date: 2002/04/16 10:44:32 $Revisio
n: r11.11/4 PATCH_11.11 (PHNE_25627)
cachefs_subr.c $Date: 2002/04/16 10:43:47 $Revision:
r11.11/3 PATCH_11.11 (PHNE_25627)
cachefs_strict.c $Date: 2001/08/13 16:52:30 $Revisio
n: r11.11/1 PATCH_11.11 (PHNE_24035)
cachefs_singlewrc.c $Date: 2001/08/13 16:52:30 $Revi
sion: r11.11/1 PATCH_11.11 (PHNE_24035)
cachefs_resource.c $Date: 2001/11/15 14:55:32 $Revis
ion: r11.11/2 PATCH_11.11 (PHNE_24910)
cachefs_noopc.c $Date: 2001/08/13 16:52:30 $Revision
: r11.11/1 PATCH_11.11 (PHNE_24035)
cachefs_module.c $Date: 2001/08/13 16:52:30 $Revisio
n: r11.11/1 PATCH_11.11 (PHNE_24035)
cachefs_log.c $Date: 2001/11/15 14:55:32 $Revision:
r11.11/1 PATCH_11.11 (PHNE_24910)
cachefs_fscache.c $Date: 2002/04/16 10:43:13 $Revisi
on: r11.11/3 PATCH_11.11 (PHNE_25627)
cachefs_filegrp.c $Date: 2001/08/13 16:52:30 $Revisi
on: r11.11/1 PATCH_11.11 (PHNE_24035)
cachefs_dir.c $Date: 2001/11/15 14:55:32 $Revision:
r11.11/2 PATCH_11.11 (PHNE_24910)
cachefs_cod.c $Date: 2001/08/13 16:52:30 $Revision:
r11.11/1 PATCH_11.11 (PHNE_24035)
cachefs_cnode.c $Date: 2001/11/15 14:55:32 $Revision
: r11.11/2 PATCH_11.11 (PHNE_24910)
/usr/conf/lib/libnfs.a:
klm_lckmgr.c $Date: 2002/09/06 12:30:43 $Revision: r
11.11/3 PATCH_11.11 (PHNE_27218)
nfs_vnops.c $Date: 2001/11/15 14:55:32 $Revision: r1
1.11/4 PATCH_11.11 (PHNE_24910)
nfs_subr.c $Date: 2001/05/29 13:35:59 $Revision: r11
.11/2 PATCH_11.11 (PHNE_23502)
nfs_dispatch.c $Date: 2001/02/21 17:04:14 $Revision:
r11.11/1 PATCH_11.11 (PHNE_22878)
nfs3_server.c $Date: 2002/08/01 17:07:39 $Revision:
r11.11/2 PATCH_11.11 (PHNE_27218)
nfs_common.c $Date: 2001/05/29 13:35:26 $Revision: r
11.11/1 PATCH_11.11 (PHNE_23502)
nfs_client.c $Date: 2001/05/29 13:34:40 $Revision: r
11.11/1 PATCH_11.11 (PHNE_23502)
nfs3_vnops.c $Date: 2002/08/01 17:07:50 $Revision: r
11.11/6 PATCH_11.11 (PHNE_27218)
hpnfs_vnops.c $Date: 2002/08/01 17:07:28 $Revision:
r11.11/5 PATCH_11.11 (PHNE_27218)
hpnfs_util.c $Date: 2001/02/26 13:19:29 $Revision: r
11.11/1 PATCH_11.11 (PHNE_22878)
/usr/conf/lib/librpc.a:
tcp_svc.c $Date: 2002/04/16 10:50:55 $Revision: r11.
11/2 PATCH_11.11 (PHNE_25627)
svc_gen.c $Date: 2001/02/21 17:08:51 $Revision: r11.
11/1 PATCH_11.11 (PHNE_22878)
svc_cots.c $Date: 2002/08/01 17:08:31 $Revision: r11
.11/2 PATCH_11.11 (PHNE_27218)
svc_clts.c $Date: 2002/08/01 17:08:21 $Revision: r11
.11/1 PATCH_11.11 (PHNE_27218)
svc_authu.c $Date: 2001/05/29 13:38:14 $Revision: r1
1.11/1 PATCH_11.11 (PHNE_23502)
rpcmod.c $Date: 2001/11/15 14:55:32 $Revision: r11.1
1/2 PATCH_11.11 (PHNE_24910)
rpc_tcp.c $Date: 2001/05/29 13:41:02 $Revision: r11.
11/1 PATCH_11.11 (PHNE_23502)
rpc_prot.c $Date: 2001/11/15 14:55:32 $Revision: r11
.11/1 PATCH_11.11 (PHNE_24910)
clnt_gen.c $Date: 2002/08/01 17:08:10 $Revision: r11
.11/1 PATCH_11.11 (PHNE_27218)
clnt_cots.c $Date: 2002/04/16 10:48:41 $Revision: r1
1.11/3 PATCH_11.11 (PHNE_25627)
clnt_clts.c $Date: 2001/05/29 13:37:41 $Revision: r1
1.11/1 PATCH_11.11 (PHNE_23502)
cksum(1) Output:
NFS.KEY-CORE,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
3999036456 36864 /usr/sbin/newkey
NFS.NFS-64ALIB,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
172888053 1521380 /usr/lib/pa20_64/libnsl.a
NFS.NFS-64SLIB,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
1394155462 702624 /usr/lib/pa20_64/libnsl.1
4019216443 46216 /usr/lib/pa20_64/libnss_nis.1
611609937 67016 /usr/lib/pa20_64/libnss_nisplus.1
NFS.NFS-CLIENT,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
1596387762 36864 /sbin/fs/cachefs/fsck
3875629890 28672 /sbin/fs/cachefs/mount
3447884840 24576 /sbin/fs/cachefs/umount
2566529755 13346 /sbin/init.d/nfs.client
588328630 40960 /usr/lib/netsvc/fs/autofs/automount
3706058791 81920 /usr/lib/netsvc/fs/autofs/automountd
405157150 98304 /usr/lib/netsvc/fs/automount/automount
3126123163 32768 /usr/sbin/cfsadmin
NFS.NFS-CORE,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
1364294430 40960 /sbin/fs/nfs/mount
4112044337 20480 /sbin/fs/nfs/umount
662308930 6802 /sbin/init.d/nfs.core
3995465168 16384 /usr/sbin/clear_locks
1583805599 15772 /usr/sbin/nfsconfcol
1282358685 122880 /usr/sbin/rpc.lockd
3300721418 53248 /usr/sbin/rpc.statd
2191049311 16384 /usr/sbin/setoncenv
NFS.NFS-ENG-A-MAN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
4164568363 1241 /usr/share/man/man1.Z/domainname.1
2108615074 4196 /usr/share/man/man1m.Z/cfsadmin.1m
3514638686 1312 /usr/share/man/man1m.Z/clear_locks.1m
1368509260 1030 /usr/share/man/man1m.Z/fsirand.1m
640950612 3197 /usr/share/man/man1m.Z/mount_cachefs.1m
192063376 1796 /usr/share/man/man1m.Z/mountd.1m
625941768 2450 /usr/share/man/man1m.Z/nfsstat.1m
192063376 1796 /usr/share/man/man1m.Z/rpc.mountd.1m
3930660271 1263 /usr/share/man/man1m.Z/setoncenv.1m
1152346362 5528 /usr/share/man/man1m.Z/ypbind.1m
2507991603 2468 /usr/share/man/man1m.Z/ypinit.1m
1132126127 2762 /usr/share/man/man1m.Z/yppasswdd.1m
1152346362 5528 /usr/share/man/man1m.Z/ypserv.1m
1152346362 5528 /usr/share/man/man1m.Z/ypxfrd.1m
1242602182 7162 /usr/share/man/man4.Z/nsswitch.conf.4
1242602182 7162 /usr/share/man/man4.Z/switch.4
NFS.NFS-PRG,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
1889318060 81920 /usr/bin/rpcgen
889148715 784440 /usr/lib/libnsl.a
NFS.NFS-SERVER,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
2803572766 20480 /usr/lib/netsvc/rusers/rpc.rusersd
3804881169 28672 /usr/sbin/exportfs
2028567896 32768 /usr/sbin/nfsd
1151253361 49152 /usr/sbin/rpc.mountd
NFS.NFS-SHLIBS,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
578320606 724992 /usr/lib/libnsl.1
4019003958 45056 /usr/lib/libnss_nis.1
NFS.NIS-CLIENT,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
3747782824 8232 /sbin/init.d/nis.client
55339465 36864 /usr/lib/netsvc/yp/ypbind
NFS.NIS-CORE,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
1706001636 12288 /usr/bin/domainname
1589991886 40960 /usr/sbin/ypxfr
NFS.NIS-SERVER,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
3177846680 24576 /usr/lib/netsvc/yp/rpc.yppasswdd
3033578396 65536 /usr/lib/netsvc/yp/ypserv
7324339 15372 /usr/newconfig/usr/sbin/ypinit
2068940848 20480 /usr/sbin/ypxfrd
NFS.NISPLUS-CORE,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
4243020329 6892 /sbin/init.d/nisplus.server
1417290590 65536 /usr/lib/libnss_nisplus.1
NFS.NFS-KRN,fr=B.11.11,fa=HP-UX_B.11.11_32,v=HP:
1911339592 54570 /usr/conf/lib/libautofs.a
959718182 180660 /usr/conf/lib/libcachefs.a
4120527433 362252 /usr/conf/lib/libnfs.a
3112363220 162432 /usr/conf/lib/librpc.a
NFS.NFS-KRN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP:
2408431123 107720 /usr/conf/lib/libautofs.a
1950096688 349956 /usr/conf/lib/libcachefs.a
3013286552 784246 /usr/conf/lib/libnfs.a
3524731689 334412 /usr/conf/lib/librpc.a
Patch Conflicts: None
Patch Dependencies:
s700: 11.11: PHCO_24777
s800: 11.11: PHCO_24777
Hardware Dependencies: None
Other Dependencies:
Fix for JAGad28779 depends on PM patches PHKL_24253,
PHKL_24254, PHKL_24255, PHKL_24256, and PHKL_24257.
Supersedes:
PHNE_27218 PHNE_26388 PHNE_25627 PHNE_25625 PHNE_24910 PHNE_24035
PHNE_23502 PHNE_23248 PHNE_22878
Equivalent Patches: None
Patch Package Size: 7510 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_28103
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHNE_28103.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHNE_28103. If you do not wish to retain a
copy of the original software, include the patch_save_files
option in the swinstall command above:
-x patch_save_files=false
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHNE_28103.text file is
available in the product readme:
swlist -l product -a readme -d @ /tmp/PHNE_28103.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHNE_28103.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
The fix for JAGae40412 requires the ypinit script to be
copied from /usr/newconfig/usr/sbin to /usr/sbin/. To backup
the current ypinit script and enable the new ypinit script,
do the following steps:
mv /usr/sbin/ypinit /usr/sbin/ypinit.bak
cp -p /usr/newconfig/usr/sbin/ypinit /usr/sbin/ypinit
PHNE_24035:
The fix for JAGad15675 is disabled by default. In order to
enable the fix, the kernel parameter 'nfs_new_lock_code'
must be changed from the default value of 0 to 1. This can
be done by either patching the vmunix file and rebooting, or
patching the kernel image in memory. To patch the vmunix
file (survives a reboot), use the following command:
echo 'nfs_new_lock_code?W 0d1' |
adb -w -k /stand/vmunix /dev/kmem
To patch the in-memory kernel (does not survive a reboot),
use the following command:
echo 'nfs_new_lock_code/W 0d1' |
adb -w -k /stand/vmunix /dev/kmem
A kernel regeneration will require these steps be done
again to enable the fix.
The fix for JAGad72416 is disabled by default. In order to
enable the fix, the kernel parameter
'async_read_avoidance_enabled' must be changed from the
default value of 0 to 1. This can be done by either patching
the vmunix file and rebooting, or patching the kernel image
in memory. To patch the vmunix file (survives a reboot), use
the following command:
echo 'async_read_avoidance_enabled?W 0d1' |
adb -w -k /stand/vmunix /dev/kmem
To patch the in-memory kernel (does not survive a reboot),
use the following commands:
echo 'async_read_avoidance_enabled/W 0d1' |
adb -w -k /stand/vmunix /dev/kmem
A kernel regeneration will require these steps to be done
again to enable the fix.
PHNE_23502:
To resolve the process hang/deadlock due to unkillable
processes defect (JAGad28779), PHKL_24253, PHKL_24254,
PHKL_24255, PHKL_24256, and PHKL_24257 must also be
installed along with this patch. All six of these patches
may be installed independently. If all six patches are not
installed, the fix will not be enabled.
|
Printable version
