ONCplus Release Notes (762806-001, March 2014)
Table 1 ONCplus Enhancements and Software Defect Fixes (continued)
ONCplus VersionDescriptionCR ID
B.11.31.13
The ‘ls –ls’ command returns an incorrect number of used blocks when it is
executed on an NFS system.QXCR1001025914
B.11.31.13
The statd and automountd daemons incorrectly accept requests sent from a
non-loopback address.QXCR1001052992
B.11.31.13The gssd daemon may run into a loop under certain conditions.QXCR1001090660
B.11.31.13
Attempting a forced unmount may result in NFS client system to hang when
many write requests are in progress on the system.QXCR1001092363
B.11.31.13The NFS client may panic when the nfs_acl_dup_res_impl function is executed.QXCR1001098196
B.11.31.13Attempting an “autofs –unmount” may slow down the NFS client system.QXCR1001099929
B.11.31.13Adding a host to a netgroup may not work.QXCR1001099945
B.11.31.13
The pcnfsd daemon may hang when multiple Auth requests are sent to the
wlogin function.QXCR1001105312
B.11.31.13
When the NFS v3 and v4 open/write 32bit API is executed without the
O_LARGEFILE parameter, the file size can exceed 2 GB.QXCR1001106195
B.11.31.13
The nfsmapid daemon may dump core when the DNS server is a windows
server.QXCR1001114093
B.11.31.13
On an NFS protocol v4 system, the default ACLs for the set and get directories
may fail with the error “acl failed for file "x",Invalid argument".QXCR1001115636
B.11.31.13
On an NFS client system, when a single find command is used to find and
remove a 0 MB file, the system may panic and display the message "panic:
b_spinner_cpsema bad?”.QXCR1001124632
B.11.31.13
The default parameter for the clnt_clts_max_endpoints function has been
modified to support the reserving of ports for application usage.QXCR1001127328
B.11.31.13
The locking mechanism for the e_cnt member of the endpnt_type function has
been modified to restrict the maximum number of endpoints.QXCR1001127336
B.11.31.13
The ‘mount -o vers=4,proto=tcp...’ command may fail when a firewall is
present.QXCR1001131929
B.11.31.13
A high priority thread may get into a loop by waiting for a lock that is held
by a lower priority thread, which may result in a non-pingable hang.QXCR1001044409
B.11.31.13
NFS client may hang in a loopback environment if UFC filecache is set to very
low (say 1%).QXCR1001059162
B.11.31.11
Executing the open() system call thread over NFSv3 mount may result in system
hang.QXCR1001010420
B.11.31.11
On an HP-UX 11i v3 NFS client system, NFSv3 server-crash recovery does
not work.QXCR1001059767
B.11.31.11
The ls -l command may hang on an NFS-mounted filesystem running
ONCplus B.11.31.09.QXCR1001052004
B.11.31.11
Under certain circumstances, the rpc.lockd daemon mistakenly closes the
“listen” fd on the T_DISCONNECT event.QXCR1001080581
B.11.31.11
NFSv4 server sends the same write verifier across reboots, resulting in data
corruption.QXCR1001090034
B.11.31.11NFS/VM ASSERT panic occurs during debug kernel testing.QXCR1001051156
B.11.31.11Support for reverse name lookup in NFS.QXCR1001055571
B.11.31.11
NFS server panics when a write request is performed on a file on read-only
mount.QXCR1001058072
Enhancements and fixes in ONCplus to date 11