|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
HP-UX series 700 11.X patch digest
From: IT Resource Center (support_feedback
us-support2-mail.external.hp.com)
Date: Sun May 18 2003 - 16:20:49 CDT
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
HP Support Information Digests
===============================================================================
o IT Resource Center World Wide Web Service
---------------------------------------------------
If you subscribed through the IT Resource Center and would
like to be REMOVED from this mailing list, access the
IT Resource Center on the World Wide Web at:
http://support.itrc.hp.com/
Login using your IT Resource Center User ID and Password.
Then select Support Information Digests (located under
Maintenance and Support). You may then unsubscribe from the
appropriate digest.
To download a patch referenced below, access the
IT Resource Center on the World Wide Web at:
http://support.itrc.hp.com/
Login using your IT Resource Center User ID and Password.
Then select Individual Patches (under Maintenance and Support)
to access the patch. You may also download a patch via anonymous
ftp(1) from ftp.itrc.hp.com.
===============================================================================
Digest Name: weekly HP-UX series 700 11.X patch digest
Created: Sun May 18 7:05:55 EDT 2003
Table of Contents:
Document ID Title
--------------- -----------
PHSS_28732 s700_800 11.X OV OB4.10 patch - CS packet
PHNE_28636 s700_800 11.00 EISA 100BT cumulative patch
PHNE_28795 s700_800 11.22 Cumulative Mux and Pty Patch
PHNE_28567 s700_800 11.00 ONC/NFS General Release/Performance Patch
PHSS_28949 s700_800 11.X OV ITO7.1X Msg/Act AIX Agent A.07.20
PHNE_28568 s700_800 11.11 ONC/NFS General Release/Performance Patch
PHCO_29085 s700_800 11.04 (VVOS) wall(1M) patch
PHCO_28961 s700_800 11.04 (VVOS) PAM support for OpenSSH
PHSS_28917 s700_800 11.00 X/Motif 64bit Runtime Patch
PHSS_28875 s700_800 11.11 X/Motif Runtime Patch
PHSS_28874 s700_800 11.00 X/Motif 32bit Runtime Patch
PHSS_28681 s700_800 11.11 XClients Periodic Patch
PHSS_28680 s700_800 11.00 XClients Periodic Patch
PHSS_28679 s700_800 11.11 CDE DevKit Periodic Patch
PHSS_28678 s700_800 11.00 CDE DevKit Periodic Patch
PHSS_28677 s700_800 11.11 CDE Applications Periodic Patch
PHSS_28676 s700_800 11.11 CDE Base Periodic Patch
PHSS_28675 s700_800 11.00 CDE Runtime Periodic Patch
PHNE_28654 s700_800 11.04 (VVOS) Cumulative Mux and Pty Patch
PHNE_28538 s700_800 11.00 cumulative ARPA Transport patch
PHNE_24342 s700_800 11.00 R6.11.00 SNAplus2 services, TN3270 patch
PHCO_28690 s700_800 11.00 cat(1) cumulative patch
PHCO_28655 s700_800 11.04 (VVOS) mksf(1M) cumulative patch
PHCO_28530 s700_800 11.11 file(1) cumulative patch
PHSS_28948 s700_800 11.X OV ITO7.1X Msg/Act Solaris Agent A.07.20
The documents are listed below.
-------------------------------------------------------------------------------
Document ID: PHSS_28732
Date Loaded: 20030516
Title: s700_800 11.X OV OB4.10 patch - CS packet
Patch Name: PHSS_28732
Patch Description: s700_800 11.X OV OB4.10 patch - CS packet
Creation Date: 03/05/12
Post Date: 03/05/16
Hardware Platforms - OS Releases:
s700: 11.00 11.11 11.20
s800: 11.00 11.11 11.20
Products:
OmniBackII A.04.10
Filesets:
OMNIBACK-II.OMNI-CS,fr=A.04.10,fa=HP-UX_B.11.00_32/64,v=HP
Automatic Reboot?: No
Status: General Release
Critical: No
Category Tags:
defect_repair general_release manual_dependencies
Path Name: /hp-ux_patches/s700_800/11.X/PHSS_28732
Symptoms:
PHSS_28732:
Id = HSLco39134 SR:H555009289
Performing "omnisv -stop" command sometimes returns exit
code different then 0 and because of that crs dies with
error message:
"Cannot stop "omniback_crs" service
system error:|502|"
Id = HSLco39169 SR:H555009297
After aborting host backup the object post-exec script
does not execute.
Id = HSLco39260 SR:H555009322
"omnib" started from different scheduler completes
successfully, but the following error is reported
to stderr:
"SystemErr: |10054| Connection reset by peer"
Id = HSLco39447 SR:H555009381
Catalog import fails if "dcbf" file does not exist.
Id = HSLco39448 SR:H555009382
Running backup on Cell Manager which is inhibited with
command: omniclus -clus host_name -inhibit "time"
produces default error report and abnormal end of
session.
Id = HSLco39878 SR:H555009560
Backup run twice when daylight saving time is changed.
Id = HSLco39885 SR:H555009567
"debug.log" contains messages that Detail Catalog
Binary Files (DCBF) is corrupted, although "omnidbcheck"
does not report any error.
Id = HSLco39976 SR:H555009593
When using the "omnimm -list_scratch_media 'pool_name'"
command, no NDMP media is listed .
Id = HSLco40396 SR:H555009779
After installing SSPUX410_056, aborted Oracle
backup session hangs.
Id = HSLco40471 SR:H555009833
When omnitrig is stopped and omnisv is started with
"omnisv -start_mon", all services stop.
Id = HSLco40559 SR:H555009877
Backup specification does not reflect correct
schedules.
Id = HSLco40594 SR:H555009895
omnidbutil -cdbsync fails in a non-MOM environment.
Id = HSLco40896 SR:H555010043
Message "EIPCALREADYINIT" is filling the debug.log file.
Id = HSLco40964 SR:H555010075
When virtual name does not match the hostname of the
host currently running as the cell manager, all the
scripts are considered as remote exec script.
Id = HSLco41021 SR:H555010103
Imported catalog from media has catalog protection
set to None.
Id = HSLco41054 SR:H555010123
Restore session fails with error:
"|Critical| From: RSM "" Time:<time>
Media Management daemon subsystem reports:
"Invalid slot specified."
Id = HSLco41120 SR:H555010158
After aborting the backup session, new backup session
is started and it hangs for a SmMaIdleTimeout variable,
before it aborts.
Id = HSLco41270 SR:H555010234
Integration restore hangs if SmWaitForNewClient
variable is not properly set.
Id = JAGae52957 SR:8606289026
Device Flow Report is not working correctly.
Id = JAGae62427 SR:8606298931
Instead of positioning the tape to the beginning of the
file, backint restore positions the tape to the
beginning of the whole object.
Id = JAGae64291 SR:8606300821
Executing "crs -redebug" from command line displays
a usage summary.
PHSS_27603:
Id = HSLco36403 SR:H555008641
Whenever there is OmniBack II activity going on in
the Cell, the update of the NT clients fails.
Id = HSLco36432 SR:H555008650
Restarting CS daemons using omnisv produces the
following entries in the debug.log:
"VELOCIS DB ERROR [0] internal error
[-2005] server unavailable"
Id = HSLco36656 SR:H555008680
When Cartridge Memory Support is activated for drives
with the LTO-Ultrium media type, MSM (Media Session
Manager) goes into a loop when try to reformatting or
listing Cartridge Memory contents.
Id = HSLco36721 SR:H555008690
If a Manager-of-Managers Server is also a
MC/ServiceGuard virtual node, then the command
"omnirpt -report list_sessions -timeframe
<start_hours_ago><hours_duration>
-multicell -no_multiple"
lists the matching sessions from this node twice.
Id = HSLco36772 SR:H555008704
Format the original medium and purge the database
deletes Detail Catalog Binary Files (DCBF) files.
Id = HSLco36803 SR:H555008716
Messages from pre/post exec scripts are not filtered.
Id = HSLco36880 SR:H555008722
Reporting Email header does not contain device name.
Id = HSLco37193 SR:H555008807
When backing up SAP integration with EMC split mirror
functionality, not all the SAP files are backed up.
Id = HSLco37276 SR:H555008832
Filesystem backup fails with an error:
"[Major] From: BSM<computer> "<object>" Time: <time>
[61:3003] Lost connection to VBDA named <object>
on host <host>.
Ipc subsystem reports: "IPC Read Error
System error: [232] Connection reset by peer"
Id = HSLco37704 SR:H555008887
The connection with the host running SSEA agent is
broken.
Id = HSLco37783 SR:H555008908
When OmniBack II tries to backup non-existent SAP
redo logs, session is ended as failed.
Id = HSLco37939 SR:H555008927
While configuring OmniBack II reports using GUI,
only datalists are listed (barlists are missing).
Id = HSLco37977 SR:H555008950
After running "omnidbutil -cdbsync", the Catalog
Database is lost.
Id = HSLco38084 SR:H555008998
When a host backup session is using WakeOnLan option,
it can not retry using specified value from the
SmMaxAgentStartupRetries option.
Id = HSLco38099 SR:H555009008
Restore Graphical User Interface (GUI) does not
browse nested mountpoints.
Id = HSLco38123 SR:H555009017
Load balancing does not work correctly in case
of mount request.
Id = HSLco38291 SR:H555009053
In case when only Single Server Edition license
is applied, media agent fails during local backup.
Id = HSLco38320 SR:H555009061
In Manager-of-Managers configuration with Central
Media Management Database request for pools list
report fails.
Id = HSLco38383 SR:H555009083
In case that Detail Catalog Binary Files do not exist
in the OmniBack II database, catalog import fails.
Id = HSLco38516 SR:H555009153
OmniBack II does not display data written in
Disk Agent (DA) context of the Graphical User
Interface (GUI) during NDMP restore.
Id = HSLco38751 SR:H555009194
Total blocks and Used blocks of medium are reported as
negative numbers.
Id = HSLco38804 SR:H555009209
a)During backup session using multiple devices, Cancel
Device options leaves device locked. Device is not
available to another session.
b)If connection to a Monitor is lost during backup
session the following message appears:
"[Major] From: BSM<HOSTNAME> "<OBJECT>" Time: <TIME>
[61:3003] Lost connection to Monitor named "noname"
on host <HOSTNAME>. Ipc subsystem reports: "IPC Read
Error System error: [232] Connection reset by peer."
Id = HSLco39036 SR:H555009263
"omnidbutil" ends abnormally during "readascii" process.
Id = HSLco39130 SR:H555009286
Catalog binary file is deleted if original medium with
copy is recycled or exported. Importing the catalog
from copy medium is not possible.
Id = JAGae12418 SR:8606245960
Backup GUI displays selection, which is inconsistent
with datalist.
Id = JAGae43999 SR:8606280024
Report "Extended report on used media" gives wrong info
about used media in selected timeframe.
PHSS_27455:
Id = HSLco33764 SR:H555007590
OmniBack II does not check into what slot mediums were
entered when mount request is confirmed.
Id = HSLco34131 SR:H555007736
Report "Backup Error" does not properly display the
number of errors of the backup session.
Id = HSLco34708 SR:H555008063
Restore is started even in case that drive is
disabled.
Id = HSLco34785 SR:H555008105
Although the number of devices specified in the
backup specification is greater than minimum value
specified in load balancing options, the following
message is displayed:
"Number of devices specified in backup
specification is smaller than MIN value of load
balancing."
Id = HSLco34911 SR:H555008180
DailyMaintenance backup deletes DCBF files of
currently running backups.
Id = HSLco35035 SR:H555008242
During backup of NDMP integration Backup Media Agent
session completes with failures.
Id = HSLco35076 SR:H555008261
Backup fails with an error:
"Internal error. Allocation form library failed.
The Media Management daemon reports:
"Internal error: DbaXXXX functions.""
Id = HSLco35515 SR:H555008452
Backup Session Manager does not terminate after
the time specified in the SmDaIdleTimeout variable
when connection to Disk Agent and Media Agent is lost.
Id = HSLco35873 SR:H555008549
The following warning message is displayed:
"[Warning] From: <hostname> "<datalist or barlist name>"
Time: mm/dd/yy hh:mm:ss
License not available
"Split Mirror Extension for ONE EMC Symmetrix""
Id = HSLco36132 SR:H555008606
SAP offline backup using the VA integration reports
the following errors:
"[Major] From: BSM<CM_hostname>
"<datalist_or_barlist_name>" Time: mm/dd/yy hh:mm:ss
[61:1002] The Snapshot Agent named ""
on host <hostname>
reached its inactivity timeout of 7200 seconds.
The agent on host will be shutdown."
Id = JAGae27169 SR:8606262839
Configuration Report creates an incorrect list of
scheduled backups.
PHSS_26354:
Id = HSLco32101 SR: H555006969
The OmniBack II database backup fails with 'Session
Aborted' if the global variable 'RecoveryIndexDir='
refers to a directory that either does not exist or
is not accessible. (This variable indicates the
location of a copy of the RecoverIndex file.)
Id = HSLco32736 SR:H555007177
If ".util HOSTNAME" returns nothing with "omnicc
-import_host", crs ends abnormally.
Id = HSLco32873 SR:H555007218
If you try to restore files in interval that does not
include full backup the following error appears:
"DB unknown error".
Id = HSLco33215 SR:H555007362
Devices are locked after the end of media session.
Id = HSLco33217 SR: H555007364
After OmniBack II services are stopped during backup
and the remaining OmniBack II processes are killed,
mmd and crs fail to start afterwards.
Id = HSLco33266 SR:H555007383
"Restore by query" loops forever.
Id = HSLco33360 SR:H555007428
Backup fails with error:
"[Major] From: BMA<HOST> Time:<TIME>
[90:64] Can not unload exchanger medium
(Storage slot is occupied.)".
Id = HSLco33437 SR:H555007455
When source tape protection expires and the catalog is
still protected, the tape is reused although a copy is
attached to it. Transporting the catalog then results
is protection set to "None" for the objects from
original tape.
Id = HSLco33515 SR:H555007485
Purgeadvisor reports that filename purge is needed
even after the purge is done.
Id = HSLco33593 SR:H555007524
Although the number of devices specified in the
backup specification is greater then minimum value
specified in load balancing options, the following
message is displayed:
"Number of devices specified in backup
specification is smaller than minimum value of load
balancing.".
Id = HSLco34050 SR:H555007700
Backup fails with error:
"[Critical] From: BMA<HOST> "<DEVICE>" Time:<TIME>
[90:30] SM/MA protocol error => aborting"
Id = HSLco34429 SR:H555007901
After applying CS patch (PHSS_25962/PHSS_25963),
the OB2PORTRANGE variable is ignored.
Id = JAGae14881 SR:8606248483
Address of a Cell Console client is incorrectly
handled.
PHSS_25963:
Id = HSLco31142 SR: H555006771
Load balancing is not working properly.
Id = HSLco31145 SR: H555006772
Omniback database suddenly stops reporting any
details about sessions.
Id = HSLco31265 SR: H555006788
After the execution of a session with load balacing
used, devices remain locked and cannot be used for
later sessions.
Id = HSLco31359 SR: H555006819
Forced ownership in datalist does not function
properly.
Id = HSLco31475 SR: H555006843
Backup Session Manager abnormally ends.
Id = HSLco31629 SR: H555006868
Vault reporting does not work properly.
Id = JAGad98695 SR: 8606229643
Changing any option for a DCBF directory resets
all other values to default.
Id = HSLco31067 SR: H555006757
"End of Session" e-mail notification does not specify
datalist name for which it was created.
Id = HSLco31942 SR: H555006939
Restore of Oracle 8 objects hangs.
Id = HSLco31981 SR: H555006948
Cell Request Server abnormally ends periodically.
Id = HSLco32089 SR: H555006968
The 'omnidbrestore -autorecover' fails with error:
"Current medium is refused for restore. Aborting!"
Id = HSLco32276 SR: H555006998
Using a "\" sign when setting RecoveryIndexDir option
in global options file sometimes causes Backup Session
Manager failure.
Id = HSLco32499 SR: H555007081
"omnisv -start_mon" is inactive for 1 second between
loops.
Id = HSLco32614 SR: H555007115
Executing "omnidbutil -purge -filenames <hostname>"
fails with an error:
"[Major] From: OMNIDBUTIL<host> "" Time: <time>
Functionality not (yet) supported."
Id = JAGad90905 SR: 8606221771
Case sensitive search does not work.
Id = JAGae05208 SR: 8606236143
Not all session manager processes are correctly stopped
using csfailover.ksh script.
Id = HSLco32902 SR: H555007234
Some objects are missing from the OmniBack internal
database after upgrading OmniBack II A.03.xx to
OmniBack II A.04.10.
Defect Description:
PHSS_28732:
Id = HSLco39134
Omnisv does not wait long enough for crs service to be
stopped.
Resolution:
New global option variable "OmnisvStatusSleep" is
introduced. Add this new variable into global options
file: OmnisvStatusSleep=X; where x should be in range
2<X<60. This will enable omnisv to wait for X seconds
to successfully stop crs service.
Id = HSLco39169
Before executing the object post-exec script,
OmniBack II checks if session is aborting. If
it is, then script does not execute.
Resolution:
Global variable PostExecOnAbortHostBackup was added.
If this global variable is set to 1, the post-exec
script will execute even if the session is aborting.
Id = HSLco39260
Backup Session Manager (BSM) is going down too fast
after sending "MSG_CLOSE" to connected monitors.
Resolution:
"OB2BSMSLEEPBEFORECLOSE" environment variable is added
in order to wait few seconds before going down.
Id = HSLco39447 SR:H555009381
During catalog import OmniBack II tries to remove the
original "dcbf" file. If this file does not exist,
catalog import fails.
Resolution:
Catalog import is improved in order not to abort in
case if "dcbf" file does not exist.
Id = HSLco39448
Crs tries to receive messages by inhibited Cell Manager.
Resolution:
If Cell Manager is inhibited, Data Protector does not
send or receive any messages, but exits with message:
"|12:1602| Cannot access the Cell Manager system".
Id = HSLco39878
The algorithm, that handles the daylight saving time
changes is uncomplete.
Resolution:
The algorithm is changed for both time changes:
02h->03h and 03h->02h.
Id = HSLco39885
"omnidbcheck" does not correctly report corruption in
Detail Catalog Binary Files (DCBF).
Resolution:
"omnidbcheck" is improved in order to correctly report
errors on the Detail Catalog Binary Files (DCBF).
Id = HSLco39976
NDMP media data format is not marked as OmniBack II
data format. Command "omnimm -list_scratch_media
'pool_name'" lists only OmniBack data format.
Resolution:
Command "omnimm -list_scratch_media 'pool_name'" is
changed; now it also lists NDMP data format media.
Id = HSLco40396
When Oracle integration backup issues a mount request
and an attempt to abort backup is made, the omniabort
will hang and the session will not shut down. This
happens with SSPUX410_056 installed.
Resolution:
Backup Session Manager (BSM) is fixed.
Part of SSPUX410_061.
Id = HSLco40471
"omnisv -start_mon" checks status of all services.
Resolution:
omnisv -start_mon checks status of all services
excluding omnitrig.
Id = HSLco40559
Schedules with excluded days are interpreted
incorrectly.
Resolution:
Schedules interpretation for excluded days is changed.
Id = HSLco40594
After checking for mom_server file error is not cleared.
Resolution:
After checking for mom_server file error is cleared.
Id = HSLco40896
Function IpcExit() is never called, so each time the
function IpcInit() is called, the error is written in
debug log.
Resolution:
Function IpcExit() is put to correct place in the code.
Id = HSLco40964
When session is configured using post or pre exec
scripts on virtual machines no check is being made to
determine if IP is local. Only hostnames (strings) are
compared.
Resolution:
Additional checking is made to determine if IP is local.
Id = HSLco41021
When importing catalog its protection is set to
None. When catalog is imported with None protection it
is purged out of database first time when purge is
started.
Resolution:
Catalog's protection is changed to be set to Permanent
after importing it.
Id = HSLco41054
OmniBack II does not lock tapes properly.
Resolution:
OmniBack II checks if tape is locked by any of the
owners before locking the tape.
Id = HSLco41120
Omniback II aborts all OB2BAR connections which do
not make connection to object in time.
Resolution:
OB2BAR connections that do not make it to objects
in time are now aborted properly.
Id = HSLco41270
When Media Agent is in stopping state Restore Session
Manager (RSM) can not handle restore request from the
OB2BAR.
Resolution:
Request list is reset after Media Agent gets MSG_STOP
from RSM.
Id = JAGae52957
When backup is aborted OmniBack II does not enter "End
Time" variable in the database.
Resolution:
When session is aborted or mount request is issued
OmniBack enters "End time" variable in the database.
Id = JAGae62427
Restore position for file is not calculated.
Resolution:
Calculation of file position within object is added.
Id = JAgae64291
While parsing arguments passed to crs binary, missing
arguments after -redebug options are not expected
thus abort follows and help is written.
Resolution:
Parsing is changed. When arguments for redebug are not
passed on command line, trace file is examined. If trace
file does not include parameters, help is written.
PHSS_27603:
Id = HSLco36403
OmniBack II erroneously tries to unpack already
unpacked error message in "omnicc" and overwrites
another variable.
Resolution:
Error unpacking and variable name are changed.
Id = HSLco36432
CRS service is trying to connect to Raima Database
Server while it is still in pending state.
Resolution:
CRS service waits for RDS to start listening.
Part of SSPUX410_043.
Id = HSLco36656
Media Agent ends abnormally when listing all
Cartridge Memory contents for the specific medium or
reformatting Cartridge Memory of a specific medium.
Resolution:
MSM (Media Session Manager) is improved in order to
session finish successfully in case of reformatting
cartridge memory or listing cartridge memory contents.
Part of SSPUX410_039.
Id = HSLco36721
When running "omnirpt" command all the cell servers from
the "mom_info" and the local Cell Server are queried for
matching sessions. The virtual node and the local host
are actually the same machine, so the matching sessions
are listed twice.
Resolution:
The function gethostname() is not used any more to
determine if the inspected host is also the local host,
cause in case of a Manager-of-Managers/ServiceGuard
environment it returns the physical node hostname and
not the virtual node hostname, making the virtual
hostname being seen as a non-local host. In this way
the virtual hostname is not queried for matching
sessions any more.
Id = HSLco36772
Purge operation purges catalogs even if copied tape
still exist in the database. Tape format removes
catalog from the database even if the copy tape is
still protected.
Resolution:
The Detail Catalog Binary Files (DCBF) files are not
deleted if the copy tape has valid protection.
Id = HSLco36803
Non OmniBack II format messages from pre/post exec
script are not filtered.
Resolution:
The Backup Session Manager is changed in order to
filter non OmniBack II format messages from pre/post
exec script.
Id = HSLco36880
Device name is not exported in EVENTOBJECT environment
variable.
Resolution:
Device name is exported in to EVENTOBJECT environment
variable.
Id = HSLco37193
In split mirror environment with huge SAP databases
it can happen that the size of the message buffer
OmniBack II uses is too small to receive complete list
of SAP files to be backed up.
Resolution:
Setting the OB2IPCBUFSIZE environment variable in the
/opt/omni/.omnirc file on Cell Server, R1 and R2 hosts,
specifying the desired amount of memory to be used for
the buffer solves the described problem.
Please read the following instructions and make sure
that the patches listed in "Other Dependencies" section
(see below) are installed and the environment
variable is set on Cell Server, R1 and R2 systems before
running the backup!
How to determine the buffer size?
---------------------------------
N_obj: number of objects (files)
N_fs: number of file systems
N_lvmvg: number of volume groups
N_dg: number of disk groups
N_rdsk: number of rawdisks
Obj: Object Name
ObjBack: Object Backup Name
MntPathLen: Path name on backup (R2) host
(example: /var/opt/omni/tmp/App_host)
fsmnt: File System Mount Point
fsdev: File System Device File
(example: /dev/dsk/[c0t1d1,lvol1])
vg: Volume group
(ex: /dev/vg01)
dg: Disk group (VxVM) - dependence on mapfile
which is required for creating disk group
(example:/dev/vx/dsk/dg01)
rdsk: Raw disk file name
(example: /dev/rdsk/c1t1d1)
AvgLen_<xxx> average length of <xxx>
There are two different buffers used:
1. BSM <-> R1
2. R1 <-> R2
Calculating the BSM <-> R1 buffer size
--------------------------------------
MsgSize_BSM_R1 = N_obj * (AvgLen_Obj + 1 + MntPathLen)
Calculating the R1 <-> R2 buffer size
-------------------------------------
MsgSize_R1_R2 =
N_obj*(AvgLen_Obj+1+AvgLen_ObjBack) +
N_fs*(AvgLen_fsmnt*2 + MntPathLen + AvgLen_fsdev*2)+
N_lvmvg*(AvgLen_vg*2) + N_dg*(AvgLen_dg*2) +
N_rdsk*(AvgLen_rdsk*2)
Calculating the OB2IPCBUFSIZE value
-----------------------------------
OB2IPCBUFSIZE > max (MsgSize_BSM_R1, MsgSize_R1_R2)
RESTORE NOTE:
-------------
If restore is started using the sapbda utility,
the variable OB2IPCBUFSIZE must be exported to
environment prior to starting sapbda.
Known problems:
---------------
If the calculated variable OB2IPCBUFSIZE is correctly
set, but is still too small for the file list to fit
into the message buffer, the session will fail with
the following error seen in the report:
BR295I Splitting mirror disks...
BR280I Time stamp <time>
BR279E Return code from '/opt/omni/lbin/ob2smbsplit
/<sap_homedir_path>/.<filename>.lst': 2
BR299E Split/resynchronization of mirror disks failed
In this case the variable OB2IPCBUFSIZE must be
recalculated to appropriate value. See above how to
determine it.
Part of SSPUX410_033.
Id = HSLco37276
Last message from Disk Agent is sometimes lost. This
causes Disk Agent's status reported as "Failed".
Resolution:
New environment variable:
OB2VBDASLEEPBEFORECLOSE
is introduced.
Its default value is 0. Setting it to a positive
number, in /<OMNIBACK_HOME>/.omnirc file, it specifies
number of seconds to pass before Disk Agent completes
after sending the last block of data.
Sleep time insignificantly influences backup
performance.
Id = HSLco37704
In environments where the firewall between Cell Server
and client(s) with firewall idle timeout of <x>
minutes is present, it can happen that an agent is in
idle state for the amount of time longer than mentioned
timeout. In such cases, firewall breaks the connection
between Cell Server and the client(s).
Resolution:
New environment variable OB2IPCKEEPALIVE is introduced.
Setting its value to any of YES, TRUE, ON or 1 in
/opt/omni/.omnirc file on Cell Server causes sending a
dummy package from time to time in order to keep the
connection open.
Part of SSPUX410_046.
Id = HSLco37783
By design, whenever there are no objects backed up,
OmniBack II ends session as failed.
Resolution:
Two new global variables have been introduced:
a) SessSucessfullWhenNoObjectsBackedUp
Setting this variable to 1 user can change the
OmniBack II behavior in order to end the session
as successful when there are no objects backed up.
b) TreatScriptReturnAsNormal
Setting this variable to a certain number instructs
OmniBack II to treat all the script returns equal
to the specified number as normal.
Id = HSLco37939
Barlists are members of a group which is not displayed
under reporting group in GUI Reporting.
Resolution:
Barlists are moved to a group that is displayed in GUI.
Id = HSLco37977
If "omnidbutil -cdbsync" is started on the
Manager-of-Managers client, local Media Management
Database (MMDB) is used for database synchronization.
Resolution:
If "omnidbutil -cdbsync" is running on a
Manager-of-Managers client, it issues an
error message and stops the operation.
Id = HSLco38084
When a host backup session is using WakeOnLan option,
it can not retry using specified value from the
SmMaxAgentStartupRetries option and there are no
mechanism to specify the timeout between retries.
Resolution:
When a host backup session is using WakeOnLine option,
it can retry using specified value from the
SmMaxAgentStartupRetries option and specified timeout
value from MinDelayForConnectionRetry option.
Id = HSLco38099
Tree options are not entered into OmniBack II database
during host backup of nested mountpoints.
Resolution:
Tree options are entered in to OmniBack II database.
Id = HSLco38123
In case that mount request appears at the beginning
of the backup, load balancing does not work correctly.
After the confirmation of mount request, filesystem
which is supposed to be started as the first one,
is started as the last one.
Resolution:
Load balancing is improved in order to work correctly
in case of mount request.
Id = HSLco38291
In case when only Single Server Edition license
is applied, Backup Session Manger aborts the session
before checking if there was an attempt to put the
locked device in a queue.
Resolution:
Backup Session Manger checks if there is an attempt
to put the locked device in a queue. If this is the
case it check for the Single Server Edition license.
Id = HSLco38320
In Manager-of-Managers configuration where Database
Session Manager acts as a gateway for direct access to
Media Management Database, main Database Session
Manager is not aware of pools list report and cannot
get report information from the Media Management
Database.
Resolution:
Database Session Manager can get pools list report
information from the Media Management Database.
Id = HSLco38383
During catalog import OmniBack II tries to remove
the old binary files and create new ones. In case
that old files do not exist, catalog import fails.
Resolution:
Catalog import is improved in order not to abort,
in case that Detail Catalog Binary Files do not
exist.
Id = HSLco38516
Restore Session Manager (RSM) does not include
the information about data written when updating
Graphical User Interface (GUI) Disk Agent (DA)
context.
Resolution:
The information about data written is added to
Restore Session Manager (RSM) messages sent to
Graphical User Interface (GUI).
Id = HSLco38751
Data type 'Long' does not allow numbers bigger than 2TB.
Resolution:
Reported Total blocks and Used blocks of medium are
limited to 2TB.
Id = HSLco38804
a)Device that was locked during backup session,
can not be unlocked using Cancel Device option and
it is not available for another session.
b)If backup is started with reconnect option, in case
that Monitor is closed, OmniBack II reports Error that
connection to Monitor was lost. Session continues and
completes successfully.
Resolution:
a)Device is unlocked for another session.
b)Only lost connections with Disk Agent (DA) or Media
Agent (MA) are reported as error.
Part of SSPUX410_056.
Id = HSLco39036
Files names with new line are not handled correctly.
Resolution:
"readdb" and "writedb" was changed so that file names
with new line are handled correctly.
Id = HSLco39130
When Recycling or exporting original medium from
OmniBack II database purge deletes Detail Catalog
Binary Files (DCBF) even if the copy medium is still
protected in the OmniBack II database. In addition
importing catalog from copy is not possible.
Resolution:
Catalog import from copy medium is possible.
Part of SSPUX410_053.
Id = JAGae12418
GUI is not able to handle nested mount points.
When GUI receives excluded directory from datalist
file it assumes that the part of the string between
first and second slash represents mount point.
Besides this, mount point is shown in GUI as a
mountpoint and as directory.
Resolution:
GUI is aware of nested mountpoints.
Id = JAGae43999
OmniBack II does not properly create list of sessions
for used media in selected timeframe.
Resolution:
"Extended report on used media" report is removed from
reporting.
PHSS_27455:
Id = HSLco33764
Before loading medium on mount request confirmation
database is not checked properly.
Resolution:
On mount request confirmation database is checked
properly.
Id = HSLco34131
Errors that were sent by Disk Agent are doubled.
Resolution:
OmniBack II reports right number of errors for
the backup session.
Id = HSLco34708
In case that integration restore session is started,
restore session manager does not check if the device
is disabled.
Resolution:
Restore Session Manager is changed so that the restore
will not be started if the device is disabled.
Id = HSLco34785
Backup Session Manager uses incorrect variable when
calculating the number of devices used for backup.
Resolution:
Session Manager uses proper variable.
Part of SSPUX410_021.
Id = HSLco34911
If backup protection is specified in a time interval
(-days, -weeks) and backup spans over multiple media,
"omnidbutil -purge -daily" command which is started by
DailyMaintenance process deletes DCBF files for the
media used in backup which ran at the same time as
the DailyMaintenance.
Resolution:
"omnidbutil -purge -daily" is improved in order not to
remove DCBF files for currently running backups.
Part of SSPUX410_022.
Id = HSLco35035
In case that NDMP backup contains large number of
files, Backup Media Agent uses large amount of memory.
Resolution:
Backup Media Agent memory usage is improved so it can
backup up to 5 million files.
Id = HSLco35076
In case of a Media Management Database corruption
backup can fail due to problems with the media
allocation.
Resolution:
Media allocation is improved.
Id = HSLco35515
In some cases because of incorrect agent exit code
Backup Session Manager does not terminate other agents
in correct order, which results in Backup Session
Manager does not terminate.
Resolution:
The exit code was changed.
Id = HSLco35873
OmniBack II never looks for the new TB EMC license
(B6959CA), but always looks for the old EMC standard
license (B6959BA). The same is with the new TB XP
license.
Resolution:
The Backup Session Manager agent looks also for the new
TB EMC and TB XP licenses.
Part of SSPUX410_030.
Id = HSLco36132
Backup Session Manager does not set the timeout of
infinitive seconds for the SNAPA agent, but leaves
the timeout set to the value of SmDaIdleTimeout.
Resolution:
Backup Session Manager sets the timeout of infinitive
seconds for the SNAPA agent.
Id = JAGae27169
Database session manager compares days, not taking
into account 15 minute units. Therefore report shows
some additional backups that are scheduled past
the specified time frame.
Resolution:
Beside days Database Session Manager compares 15
minute units.
PHSS_26354:
Id = HSLco32101
If RecoveryIndex path is incorrect, the file can
not be created. OmniBack II then shows a 'Major'
error and aborts the session.
Resolution:
Messages are changed to 'Warning' and the session is
not aborted if the RecoveryIndex path is invalid.
Id = HSLco32736
OmniBack II returns wrong exit code when the client
does not return any information.
Resolution:
The exit code is changed.
Id = HSLco32873
Selecting files for restore within interval that does
not include the full backup will trigger an error in
the list_full_rest_chain function.
Resolution:
The function marks an error and sends it to GUI, which
will show a message:
"You have chosen an interval which does not include
all the sessions needed to compose a full restore
chain. Please reconnect to the Cell Server".
Id = HSLco33215
Devices are locked with device lock, which can differ
from device name. When devices are unlocked, device
name is always used. If device name and device lock
are not equal, device unlock fails.
Resolution:
Device lock/unlock policy is synchronized.
Id = HSLco33217
When all the OmniBack II services are up and running,
backup is started. If during backup OmniBack II services
are stopped due to some reason and all the OmniBack II
processes are killed, mmd and crs from OmniBack II
services will be unable to start.
Resolution:
There were some problems with licenses, which were not
released properly. Licenses are now released properly.
After fix installation, reboot of Cell Server host is
highly recommended!
Part of SSPUX410_013
Id = HSLco33266
Database file search performance is poor.
Resolution:
Database search performance is improved.
Id = HSLco33360
Executing an "enter" operation for the slot being
used for backup results in backup failure.
Resolution:
New global option EnterEjectCheckLocking is
introduced. If this option is set, Media Management
operation checks if slot is locked and does not
use it.
Part of SSPUX410_012.
Id = HSLco33437
Object protection on the copied medium is set to
"None" after original tape protection expires.
Resolution:
The catalog is now transposed from the source.
The object protection for the copied medium is set
on the same level as medium protection the catalog
is transported from the source.
Id = HSLco33515
Purge advisor incorrectly interprets the growth of
the database and reports daily needed purges.
Resolution:
Purge advisor correctly recognizes the database
when purge of the database is needed.
Id = HSLco33593
Backup Session Manager uses incorrect variable when
calculating the number of devices used for backup.
Resolution:
Session Manager uses proper variable.
Id = HSLco34050
In case in which reconnect option is used for backup,
it is possible that Media Agent fails due to a protocol
error.
Resolution:
Protocol between Session Manager and Media Agent is
changed in order not to acknowledge normal formatted
messages.
Complete functionality of fix will be available
when Media Agent patch PHSS_26357/PHSS_26358 is
installed - or successors of it.
Part of SSPUX410_017.
ID = HSLco34429
The OB2PORTRANGE variable is not exported.
Resolution:
The OB2PORTRANGE variable is exported.
Id = JAGae14881
When a Cell Console client connects to the server,
user name, system name and domain are parsed correctly,
but IP address is not.
Resolution:
A new environment variable
'OB2CRSSTRICTHOSTNAMECHECKING'
is introduced. Setting its value to 1 is to enforce
the use of hostnames obtained from IP address.
PHSS_25963:
Id = HSLco31142 SR: H555006771
There is no warning reported when one creates a datalist
or a barlist with load balancing enabled and minimum
number of devices greater than number of configured
logical devices.
Resolution:
Comparison of minimum and configured devices number
is implemented.
Id = HSLco31145 SR: H555006772
Aborting an import session corrupts Omniback internal
database.
Resolution:
Aborting an import session is properly handled and it
does not corrupt internal database.
If a database corruption has been experienced because
of this defect, then after installation of this patch,
the corruption can be removed and the import of
OmniBack II 3.x tapes be enabled as follows:
1. step:
Import the problematic tape. The import itself will
fail, complaining about catalog and media management
database not being in sync. But internally it will
remove the suspective media position from the database
which makes second step possible.
2. step:
Import the problematic tape again. This succeeds and
results in imported medium and fixed database.
Part of SSPUX410_007.
Id = HSLco31265 SR: H555006788
Device lock counter is not working correctly.
Resolution:
Device lock counter is working properly and the
devices are unlocked after the session ends.
Part of SSPUX410_006.
Id = HSLco31359 SR: H555006819
Object ownership is incorrectly set if it is specified
in the datalist.
Resolution:
Object ownership is correctly set.
Part of SSPUX410_015.
Id = HSLco31475 SR: H555006843
Backup Session Manager abnormally ends in cases when
there are more than 100 objects within one data segment.
Resolution:
Backup Session Manager works properly with unlimited
number of objects within one data segment.
Id = HSLco31629 SR: H555006868
Omniback incorrectly compares selected libraries
versus all libraries when creating "List of Media"
report.
Resolution:
"List of Media" is created properly.
Id = JAGad98695 SR: 8606229643
Omniback does not check whether options have been
passed from the command line.
Resolution:
Additional checking of options is implemented for
the case that options have been sent from command
line.
Id = HSLco31067 SR: H555006757
Datalist name is not exported into environment.
Resolution:
Datalist name is exported into environment.
Id = HSLco31942 SR: H555006939
When delay between two connections for different
Oracle 8 objects is bigger that the value of
SmWaitForNewClient global variable, restore hangs.
Resolution:
Omniback deletes barlist from memory and starts new
restore session in case that Restore Session Manager
timed out and new connection for restore was accepted.
Id = HSLco31981 SR: H555006948
Command "omnicc -query" causes memory leaks in
Cell Request Server.
Resolution:
Memory leaks are removed.
Part of SSPUX410_001.
Id = HSLco32089
The '-autorecover' option in 'omnidbrestore' command
does not set the correct block size for the device.
Resolution:
The code for setting the block size was corrected.
Id = HSLco32276
If "\" sign is the last character when setting
RecoveryIndexDir value, Backup Session Manager fails
because of incorrect parsing of the value.
Resolution:
Any "\" sign that appears at the end of an argument
is cut off during the parsing.
Id = HSLco32499
With 1 second inactivity between loops,
"omnisv -start_mon" is executed too often.
Resolution:
New option "-timeout" is added for omnisv. Usage:
"omnisv -start_mon -timeout N"
where N is time in seconds.
Id = HSLco32614
omnidbutil is not able to connect to Administration
Session Manager (ASM).
Resolution:
Missing fuctionality is added to ASM.
Id = JAGad90905
Flag for case sensitivity is not checked before
search session is executed.
Resolution:
Case sensitivity flag is always checked.
Id = JAGae05208
The regular expression that is parsed by the awk script
does not return the process ID (PID) which should be
killed.
Resolution:
Regular expression string in awk parse command is
changed.
Id = HSLco32902
Objects whose protection has expired are purged from
OmniBack internal database during the upgrade.
Resolution:
New environment variable OB2UPGRADEIGNOREEXPIREDOBJECTS
is introduced. Setting its value to 1 in
/opt/omni/.omnirc file will purge objects with expired
protection during the upgrade. Otherwise, unprotected
objects are left intact.
Part of the SSPUX410_008.
Enhancement:
No
SR:
H555010234 H555009593 8606300821 H555009567 H555009297
H555009289 H555010075 8606298931 H555010158 H555009895
H555009877 H555009779 H555009322 H555009721 H555009560
H555010103 H555009381 H555009382 H555010123 H555009833
8606289026 H555010043 H555009286 H555008908 H555008891
H555008927 8606280024 H555008958 H555008887 H555008998
8606245960 H555009061 H555009053 H555009017 H555009008
H555009153 H555008722 H555008704 H555008650 H555008641
H555009209 H555009083 H555009263 H555008651 H555008832
H555008913 H555008716 H555008680 H555008950 H555009194
H555008807 H555008690 H555008754 H555008549 8606262839
H555008105 H555008242 H555008063 H555008180 H555008261
H555008452 H555008606 H555007590 H555007736 8606248483
H555007700 H555006969 H555007524 H555007218 H555007362
H555007903 H555007364 H555007383 H555007428 H555007455
H555007177 H555007485 H555006757 H555006948 H555006939
H555006868 H555006968 H555006788 H555007115 H555007234
8606236143 H555007081 H555006998 8606221771 H555006771
H555006843 H555006772 8606229643 H555006819
Patch Files:
OMNIBACK-II.OMNI-CS,fr=A.04.10,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/omni/lbin/bsm
/opt/omni/lbin/crs
/opt/omni/lbin/dbsm
/opt/omni/lbin/rsm
/opt/omni/lbin/dbbda
/opt/omni/lbin/asm
/opt/omni/lbin/msm
/opt/omni/lbin/mmd
/opt/omni/lib/libob2ecdb.sl
/opt/omni/lib/libob2ecmn.sl
/opt/omni/lib/libob2emmdb.sl
/opt/omni/lib/libob2eadm.sl
/opt/omni/sbin/omnidbutil
/opt/omni/sbin/omnitrig
/opt/omni/sbin/omnidbrestore
/opt/omni/sbin/omnisv
/opt/omni/sbin/omnisv11
/opt/omni/sbin/omnidbcheck
/opt/omni/.CII_CS
/opt/omni/newconfig/etc/opt/omni/options/global
/opt/omni/newconfig/etc/opt/omni/sg/csfailover.ksh
what(1) Output:
OMNIBACK-II.OMNI-CS,fr=A.04.10,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/omni/lbin/bsm:
[TZ=GMT0 /opt/omni/lbin/bsm -version]
HP OpenView OmniBack II A.04.10: BSM, internal build
PHSS_28731/PHSS_28732, built on Mon Apr 14
11:27:25 2003
/opt/omni/lbin/crs:
[TZ=GMT0 /opt/omni/lbin/crs -version]
HP OpenView OmniBack II A.04.10: CRS, internal build
PHSS_28731/PHSS_28732, built on Mon Apr 14
10:41:38 2003
/opt/omni/lbin/dbsm:
[TZ=GMT0 /opt/omni/lbin/dbsm -version]
HP OpenView OmniBack II A.04.10: DBSM, internal buil
d PHSS_28731/PHSS_28732, built on Mon Apr 14
12:41:37 2003
/opt/omni/lbin/rsm:
[TZ=GMT0 /opt/omni/lbin/rsm -version]
HP OpenView OmniBack II A.04.10: RSM, internal build
PHSS_28731/PHSS_28732, built on Thu May 8
18:05:22 2003
/opt/omni/lbin/dbbda:
[TZ=GMT0 /opt/omni/lbin/dbbda -version]
HP OpenView OmniBack II A.04.10: DBBDA, internal bui
ld PHSS_27602/PHSS_27603, built on Wed Dec 1
8 10:56:35 2002
/opt/omni/lbin/asm:
[TZ=GMT0 /opt/omni/lbin/asm -version]
HP OpenView OmniBack II A.04.10: ASM, internal build
PHSS_25962/PHSS_25963, built on Thu Mar 14
14:54:14 2002
/opt/omni/lbin/msm:
[TZ=GMT0 /opt/omni/lbin/msm -version]
HP OpenView OmniBack II A.04.10: MSM, internal build
PHSS_28731/PHSS_28732, built on Mon Apr 14
11:46:40 2003
/opt/omni/lbin/mmd:
[TZ=GMT0 /opt/omni/lbin/mmd -version]
HP OpenView OmniBack II A.04.10: MMD, internal build
PHSS_28731/PHSS_28732, built on Mon Apr 14
15:27:55 2003
/opt/omni/lib/libob2ecdb.sl:
None
/opt/omni/lib/libob2ecmn.sl:
None
/opt/omni/lib/libob2emmdb.sl:
None
/opt/omni/lib/libob2eadm.sl:
None
/opt/omni/sbin/omnidbutil:
[TZ=GMT0 /opt/omni/sbin/omnidbutil -version]
HP OpenView OmniBack II A.04.10: OMNIDBUTIL, interna
l build PHSS_28731/PHSS_28732, built on Mon
Apr 14 12:41:04 2003
/opt/omni/sbin/omnitrig:
[TZ=GMT0 /opt/omni/sbin/omnitrig -version]
HP OpenView OmniBack II A.04.10: OMNITRIG, internal
build PHSS_28731/PHSS_28732, built on Mon Ap
r 14 11:48:38 2003
/opt/omni/sbin/omnidbrestore:
[TZ=GMT0 /opt/omni/sbin/omnidbrestore -version]
HP OpenView OmniBack II A.04.10: OMNIDBRESTORE, inte
rnal build PHSS_25962/PHSS_25963, built on T
hu Mar 14 15:54:04 2002
/opt/omni/sbin/omnisv:
None
/opt/omni/sbin/omnisv11:
None
/opt/omni/sbin/omnidbcheck:
[TZ=GMT0 /opt/omni/sbin/omnidbcheck -version]
HP OpenView OmniBack II A.04.10: OMNIDBCHECK, intern
al build PHSS_28731/PHSS_28732, built on Mon
Apr 14 12:41:10 2003
/opt/omni/.CII_CS:
None
/opt/omni/newconfig/etc/opt/omni/options/global:
None
/opt/omni/newconfig/etc/opt/omni/sg/csfailover.ksh:
None
cksum(1) Output:
OMNIBACK-II.OMNI-CS,fr=A.04.10,fa=HP-UX_B.11.00_32/64,v=HP:
1673816823 1519084 /opt/omni/lbin/bsm
2135313349 776122 /opt/omni/lbin/crs
2201013825 1506102 /opt/omni/lbin/dbsm
3099024438 1281045 /opt/omni/lbin/rsm
834033404 702765 /opt/omni/lbin/dbbda
1127558555 763774 /opt/omni/lbin/asm
2047973244 878844 /opt/omni/lbin/msm
2521934492 583375 /opt/omni/lbin/mmd
134042711 910150 /opt/omni/lib/libob2ecdb.sl
2372121570 898512 /opt/omni/lib/libob2ecmn.sl
2642359306 750239 /opt/omni/lib/libob2emmdb.sl
2431806509 889685 /opt/omni/lib/libob2eadm.sl
909046829 878507 /opt/omni/sbin/omnidbutil
1290128942 533918 /opt/omni/sbin/omnitrig
984773928 519024 /opt/omni/sbin/omnidbrestore
842583705 271188 /opt/omni/sbin/omnisv
3167360741 303104 /opt/omni/sbin/omnisv11
4196000675 784154 /opt/omni/sbin/omnidbcheck
4159459899 11134 /opt/omni/.CII_CS
348246615 29741 /opt/omni/newconfig/etc/opt/omni/options/
global
4109013506 2408 /opt/omni/newconfig/etc/opt/omni/sg/
csfailover.ksh
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies:
If any newer SSP for the Cell Server is installed
on your system, you must re-apply the SSP after
installing this Cell Server patch.
PHSS_28739:
Cell Console (CC) packet patch,
Release Date: Late May 2003
Id = HSLco40559 SR:H555009877
Id = HSLco39130 SR:H555009286
Id = HSLco37939 SR:H555008927
Id = HSLco37193 SR:H555008807
Id = HSLco33515 SR:H555007485
Id = JAGae12418 SR:8606245960
Id = JAGae43999 SR:8606280024
PHSS_28739 is required for this defect fixes.
PHSS_28344:
SAP packet patch,
Release Date: Available
Id = HSLco37783 SR:H555008908
Id = HSLco37193 SR:H555008807
PHSS_28344 is required for this defect fixes.
PHSS_28342:
EMC packet patch,
Release Date: Available
Id = HSLco37193 SR:H555008807
PHSS_28342 is required for this defect fix.
PHSS_28233:
CORE module packet patch,
Release Date: Available
Id = HSLco37977 SR:H555008950
Id = HSLco37193 SR:H555008807
Id = HSLco33764 SR:H555007590
Id = HSLco31142 SR:H555006771
Bad catalog access messages are displayed without
PHSS_28233.
PHSS_27594:
SSEA packet patch,
Release Date: Available
Id = HSLco37704 SR:H555008887
PHSS_27594 is required for this defect fix.
PHSS_27459:
Media Agent - MA packet patch,
Release Date: Available
Id = HSLco36656 SR:H555008680
Id = HSLco35035 SR:H555008242
Id = HSLco34050 SR:H555007700
PHSS_27459 is required for this defect fixes.
Supersedes:
PHSS_27603 PHSS_27455 PHSS_26354 PHSS_25963
Equivalent Patches:
PHSS_28731:
s700: 10.20
s800: 10.20
Patch Package Size: 4170 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 PHSS_28732
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHSS_28732.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHSS_28732. 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 PHSS_28732.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHSS_28732.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHSS_28732.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
PHSS_28732:
NOTE!
This Patch has to be installed on the Cell Manager host.
OmniBack II server must be shutdown before installing
the patch. Use the following command for shutting down
the server:
"/opt/omni/sbin/omnisv.sh stop".
After the installation is complete, restart OmniBack II
server using "/opt/omni/sbin/omnisv.sh start".
Patch includes the following Site Specific Patches:
SSPUX410_001
SSPUX410_006
SSPUX410_007
SSPUX410_008
SSPUX410_012
SSPUX410_013
SSPUX410_015
SSPUX410_017
SSPUX410_021
SSPUX410_022
SSPUX410_030
SSPUX410_033
SSPUX410_039
SSPUX410_043
SSPUX410_046
SSPUX410_053
SSPUX410_056
SSPUX410_061
-----End of Document ID: PHSS_28732------------------------------------------
Document ID: PHNE_28636
Date Loaded: 20030516
Title: s700_800 11.00 EISA 100BT cumulative patch
Patch Name: PHNE_28636
Patch Description: s700_800 11.00 EISA 100BT cumulative patch
Creation Date: 03/04/29
Post Date: 03/05/16
Hardware Platforms - OS Releases:
s700: 11.00
s800: 11.00
Products:
EISA100BT B.11.00.01 B.11.00.02 B.11.00.03 B.11.00.04
Filesets:
100BT-EISA-KRN.100BT-KRN,fr=B.11.00.01,fa=HP-UX_B.11.00_32,v=HP
100BT-EISA-KRN.100BT-KRN,fr=B.11.00.02,fa=HP-UX_B.11.00_32,v=HP
100BT-EISA-KRN.100BT-KRN,fr=B.11.00.03,fa=HP-UX_B.11.00_32,v=HP
100BT-EISA-KRN.100BT-KRN,fr=B.11.00.04,fa=HP-UX_B.11.00_32,v=HP
100BT-EISA-RUN.100BT-RUN,fr=B.11.00.01,fa=HP-UX_B.11.00_32,v=HP
100BT-EISA-RUN.100BT-RUN,fr=B.11.00.02,fa=HP-UX_B.11.00_32,v=HP
100BT-EISA-RUN.100BT-RUN,fr=B.11.00.03,fa=HP-UX_B.11.00_32,v=HP
100BT-EISA-RUN.100BT-RUN,fr=B.11.00.04,fa=HP-UX_B.11.00_32,v=HP
100BT-EISA-RUN.100BT-INIT,fr=B.11.00.01,fa=HP-UX_B.11.00_32,v=HP
100BT-EISA-RUN.100BT-INIT,fr=B.11.00.02,fa=HP-UX_B.11.00_32,v=HP
100BT-EISA-RUN.100BT-INIT,fr=B.11.00.03,fa=HP-UX_B.11.00_32,v=HP
100BT-EISA-RUN.100BT-INIT,fr=B.11.00.04,fa=HP-UX_B.11.00_32,v=HP
100BT-EISA-FMT.100BT-FORMAT,fr=B.11.00.01,fa=HP-UX_B.11.00_32,v=HP
100BT-EISA-FMT.100BT-FORMAT,fr=B.11.00.02,fa=HP-UX_B.11.00_32,v=HP
100BT-EISA-FMT.100BT-FORMAT,fr=B.11.00.03,fa=HP-UX_B.11.00_32,v=HP
100BT-EISA-FMT.100BT-FORMAT,fr=B.11.00.04,fa=HP-UX_B.11.00_32,v=HP
Automatic Reboot?: Yes
Status: General Release
Critical:
Yes
PHNE_28636: PANIC
PHNE_27534: PANIC ABORT
lanadmin(1M) command aborts when querying
EISA 10/100BT interface with '-ax' options.
PHNE_24725: PANIC
PHNE_23981: HANG
PHNE_19200: PANIC
PHNE_16154: PANIC
PHNE_13543: OTHER
Multicast & Promiscuous mode not working
Category Tags:
defect_repair enhancement general_release critical panic
halts_system
Path Name: /hp-ux_patches/s700_800/11.X/PHNE_28636
Symptoms:
PHNE_28636:
1. ( SR:8606294055 CR:JAGae57795 )
Inadequate frame padding.
2. ( SR:8606289350 CR:JAGae53281 )
When the lanadmin(1M) command is used with the "-x"
option to query the EISA 10/100BT interface, the system
may panic.
HP1_ospif_dlpi_ioctl+0x9f0
hp_dlpi_process_ioctl+0x268
hp_dlpi_wput+0x5ec
putnext+0x16c
wait_iocack+0x6c
str_istr_ioctl+0x698
hpstreams_ioctl_int+0x3d4
hpstreams_ioctl+0x50
spec_ioctl+0xb0
vno_ioctl+0x8c
ioctl+0x258
syscall+0x1c8
PHNE_27534:
1. ( SR:8606188846 CR:JAGad58062 )
EISA 10/100BT card experiences multiple internal resets
with the following message logged to NetTL log file.
"bdm_watchdog: TX did not complete on time, resetting
adapter btlan01".
2. ( SR:8606248819 CR:JAGae15216 )
EISA 100BT driver panics with "Data page fault" in
_bigmac_cmdfmt_tx().
3. ( SR:8606266748 CR:JAGae30993 )
lanadmin(1M) command core dumps when querying
EISA 10/100BT interface with "-ax" option.
PHNE_24725:
1. EISA 100BT driver panics with "Data Page Fault" in
bdm_rcv_buf_alloc(). -- JAGaa45963
PHNE_23981:
1. EISA FDDI driver hangs because of EISA 100BT's
bus locking. -- JAGad50169
2. Reproducible system hang in oim_open() when
starting SAP. -- JAGad54480
3. suid bit set to lanadmin library. -- JAGad67830
PHNE_19200:
1. EISA100BT sends corrupted MAC address for DLPI
test-xid requests. -- JAGaa41098
2. linkloop to self doesn't return error when cable is not
connected. -- JAGab03857
3. IP multicast datagrams looped back in the driver.
-- JAGaa41968
4. EISA100BT driver doesn't set ifOper status correctly
in the MIB structure. -- JAGaa21367
5. Some required EISA100BT structures are not available
for Q4. -- JAGaa21642
6. Automatic speed configuration doesn't work for EISA100BT.
-- JAGab46349
7. EISA100BT start-up doesn't give a warning when set to
full duplex. -- JAGaa21652
8. Setting the speed is not possible in hpeisabtconf file.
-- JAGab65054
9. nettl traces are not formatted correctly. -- JAGab64926
10. Minimum frame length in 10BT mode should be 60 bytes
instead of 64 bytes. -- JAGab64392
11. ER: Allow the MTU size configuration using lanadmin.
-- JAGab64413
12. ER: IOCTL support is required for speed and duplex
setting using SAM. -- JAGab64697
13. EISA100BT generates duplicate packets under heavy load.
-- JAGab64911
14. Service Guard doesn't work with new interface naming
convention. -- JAGab64435
15. Startup script does not allow for non-sequential arrays.
-- JAGab70575
16. Panic with 'Already Owns this Spinlock' on EISA 100BT.
-- JAGab68637
17. "lanadmin -S 0" command hangs.
-- JAGab72670
18. DLPI primitive to set physical address succeeds even
for invalid values -- JAGab84309
19. Driver does not return error for invalid multicast
addresses. -- JAGab84311
20. Card does not work in loopback mode with changed MAC
address in hpeisabtconf. -- JAGad09607
PHNE_16403:
1. Performance degradation.
PHNE_16154:
1. EISA 100BASE-T card does not come up on 715/100/E
workstations.
2. When there is heavy network traffic, EISA 100BASE-T
card does not come up at boot time.
3. EISA 100BASE-T panics on D and C class with Data
Page fault under heavy load.
PHNE_13543:
1. SAP promiscuous mode and layer2 multicast are not
supported.
2. EISA 100BT returns current MAC address to a factory
MAC address request.
3. Startup scripts to alter the MAC address or the
duplex mode will not function.
Defect Description:
PHNE_28636:
1. ( SR:8606294055 CR:JAGae57795 )
Inadequate frame padding.
Resolution:
Adequate frame padding is done.
2. ( SR:8606289350 CR:JAGae53281 )
When EISA 10/100BT interface self-test fails, a field in
the driver data structure is not initialized properly.
The system panics when the lanadmin(1M) command with
"-x" option tries to access this uninitialized field.
Resolution:
Proper check has been added to avoid accessing
uninitialized field in the driver data structure.
PHNE_27534:
1. ( SR:8606188846 CR:JAGad58062 )
The "Command Unit" of the EISA 10/100BT card goes into
an "IDLE" state even when there are packets queued up
for transmit. This would cause the card to be unaware
of new packets posted for transmission resulting in
bdm_watchdog timer going off thus triggering a card
reset.
Resolution:
If the "Command Unit" has gone into "IDLE" state and
transmit queue is not empty, then the "Command Unit" is
restarted in bigmac watchdog routine.
2. ( SR:8606248819 CR:JAGae15216 )
In response to EISA 100BT driver's dump command request,
the card's internal registers have to be dumped on to the
host's preallocated memory location. Instead, the data
was written on to the transmit descriptor thus corrupting
the transmit descriptor ring.
Resolution:
A separate descriptor has been allocated for the dump
command.
3. ( SR:8606266748 CR:JAGae30993 )
Parameter returned to "lanadmin" was not properly
initialized in EISA 100BT driver shared library.
Resolution:
Return parameter is initialized.
PHNE_24725:
1. Under heavy load driver was corrupting free buffer list.
Later when driver tries to allocate memory in
bdm_rcv_buf_alloc() it was panicing with data page fault.
Resolution:
Code has been modified to take care of this situation.
PHNE_23981:
1. EISA 100BT was holding bus unnecessarily because of
which EISA FDDI driver was hanging.
Resolution:
Unnecessary bus locking has been removed.
2. In the oim_open() function, a linked list was
processed improperly in a while loop.
Resolution:
Processing of the linked list has been modified in
the while loop.
3. The lanadmin library was set with suid bit.
Resolution:
File permissions have been modified.
PHNE_19200:
1. An upper layer didn't set the source MAC address
while passing the packet to the driver and driver
expected MAC address to be set by upper layer.
Resolution:
Modified transmit path to copy source MAC address
for outbound packets.
2. Driver was not checking interface status for
loopback packets.
Resolution:
Code is modified to check interface status before
looping back the packet.
3. Driver didn't check whether it needs to loop back
the multicast packet to the local host.
Resolution:
The code was modified to check whether driver needs
to loop back the multicast packet.
4. EISA100BT driver was not consistent in setting ifOper
Status in the MIB with respect to lanscan.
Resolution:
Modified code to have consistency for lanadmin &
lanscan states.
5. Some required EISA100BT structures are not available
for Q4.
Resolution:
Added the necessary structures that are required for
Q4 support.
6. EISA100BT start-up script was not passing the speed
value to the 'lanadmin' command.
Resolution:
Start-up script was modified to pass the speed value
to the 'lanadmin' command.
7. EISA100BT start-up script didn't check for full duplex
mode setting.
Resolution:
Added a check for invalid duplex mode.
8. hpeisabtconf file didn't support SPEED variable.
Resolution:
Added SPEED variable in hpeisabtconf file.
9. EISA100BT subsystem formatter was not able to
format the packets properly.
Resolution:
Rewrote the subsystem formatter to fix formatting
problems.
10. EISA100BT driver supported a minimum packet length
of 64 bytes in 10BT mode instead of the standard 60
bytes.
Resolution:
Modified the driver to support a minimum packet
length of 60 bytes instead of 64 bytes.
11. ER: Allow the MTU size configuration using lanadmin.
Resolution:
Added new IOCTL requests to support set/reset MTU
values.
12. ER: IOCTL support is required for speed and duplex
setting using SAM.
Resolution:
Modified driver to support additional ioctl requests
that are required for SAM support.
13. EISA100BT card was sending duplicate packets under
heavy UDP traffic.
Resolution:
Modified transmit path to flush/purge the data in the
cache and synchronized shared memory access between
card and memory.
14. While changing the driver to new naming convention,
the ifDescr MIB variable was not modified to reflect the
same.
Resolution:
Modified the ifDescr MIB variable to use the new naming
convention.
15. Startup script was not able to recognize interface
entries in non-sequential order in file
/etc/rc.config.d/hpeisabtconf
Resolution:
Startup script is modified to process all interface
entries in file /etc/rc.config.d/hpeisabtconf, even
if they are in non-sequential order.
16. The panic happens when the driver receives a
SET_SPEED ioctl when there are pending inbound
packets.
Resolution:
Modified the code to release lock and
reclaim it again after processing pending inbound
packets.
17. Driver used to return negative value for invalid speed
values, due to which DLPI sleeps, and hence the lanadmin
command used to hang.
Resolution:
The driver now returns EINVAL to DLPI in case of an
invalid speed value.
18. The DLPI primitive to set physical address succeeds
even for invalid values (all bits 0's or 1's).
Resolution:
A check has been added for these invalid addresses.
19. Driver returns success for invalid multicast hardware
addresses which do not have the least significant bit
of the first byte set.
Resolution:
A check is now made to ensure that this bit is set.
20. Card does not work in loopback mode with changed MAC
address in hpeisabtconf. Card was sending a loop back
packet to sense speed with new MAC address and was
not getting this packet back.
Resolution:
Card will send a loop back packet with Factory MAC
address to sense speed. After loopback test card
will be set with new MAC address.
PHNE_16403:
1. A busy-wait in the performance path caused the
performance degradation.
PHNE_16154:
1. The driver did not set the speed correctly in 10Mb mode.
This occurred mainly on 715/100/E systems.
2. The driver sent a loopback packet without sensing the
media speed. The default speed was set to 100Mb. So,
under heavy network traffic the driver failed to receive
the loopback packet in 10Mb mode.
3. The driver did not do proper MP synchronization.
PHNE_13543:
1. Specific code for support of Promiscuous mode, layer2
multicast did not exist.
2. Returned incorrectly the current MAC address instead
of factory MAC address.
3. Wrong variable name in hpeisabtconf.
Enhancement:
No (superseded patches contained enhancements)
PHNE_19200:
- Allow the MTU size configuration using lanadmin.
- IOCTL support is provided for speed and duplex
setting using SAM.
PHNE_16403:
- Performance improvement was made.
SR:
8606294055 8606289350 8606188846 8606248819 8606266748
8606220723 8606180948 8606185278 8606198641 8606164026
5003397125 5003451450 5003440230 1653289090 1653296236
4701430116 5003434928 1653311423 8606103630 8606102706
8606104897 8606112070 8606112072 8606140285 1653275446
1653264465 1653267237 1653263970 1653253013 1653250639
1653249318
Patch Files:
100BT-EISA-KRN.100BT-KRN,fr=B.11.00.01,fa=HP-UX_B.11.00_32,
v=HP:
100BT-EISA-KRN.100BT-KRN,fr=B.11.00.02,fa=HP-UX_B.11.00_32,
v=HP:
100BT-EISA-KRN.100BT-KRN,fr=B.11.00.03,fa=HP-UX_B.11.00_32,
v=HP:
100BT-EISA-KRN.100BT-KRN,fr=B.11.00.04,fa=HP-UX_B.11.00_32,
v=HP:
/usr/conf/lib/libbtlan0.a
100BT-EISA-RUN.100BT-RUN,fr=B.11.00.01,fa=HP-UX_B.11.00_32,
v=HP:
100BT-EISA-RUN.100BT-RUN,fr=B.11.00.02,fa=HP-UX_B.11.00_32,
v=HP:
100BT-EISA-RUN.100BT-RUN,fr=B.11.00.03,fa=HP-UX_B.11.00_32,
v=HP:
100BT-EISA-RUN.100BT-RUN,fr=B.11.00.04,fa=HP-UX_B.11.00_32,
v=HP:
/usr/lib/nls/msg/C/dsbtlan0.cat
/usr/lib/lanadmin/libdsbtlan0.sl
100BT-EISA-RUN.100BT-INIT,fr=B.11.00.01,fa=HP-UX_B.11.00_32,
v=HP:
100BT-EISA-RUN.100BT-INIT,fr=B.11.00.02,fa=HP-UX_B.11.00_32,
v=HP:
100BT-EISA-RUN.100BT-INIT,fr=B.11.00.03,fa=HP-UX_B.11.00_32,
v=HP:
100BT-EISA-RUN.100BT-INIT,fr=B.11.00.04,fa=HP-UX_B.11.00_32,
v=HP:
/usr/sbin/hpeisabt_init
/usr/newconfig/etc/rc.config.d/hpeisabtconf
/sbin/init.d/hpeisabt
100BT-EISA-FMT.100BT-FORMAT,fr=B.11.00.01,
fa=HP-UX_B.11.00_32,v=HP:
100BT-EISA-FMT.100BT-FORMAT,fr=B.11.00.02,
fa=HP-UX_B.11.00_32,v=HP:
100BT-EISA-FMT.100BT-FORMAT,fr=B.11.00.03,
fa=HP-UX_B.11.00_32,v=HP:
100BT-EISA-FMT.100BT-FORMAT,fr=B.11.00.04,
fa=HP-UX_B.11.00_32,v=HP:
/usr/lib/libeisa100btfmt.sl
/usr/lib/nls/msg/C/fmteisa100bt.cat
what(1) Output:
100BT-EISA-KRN.100BT-KRN,fr=B.11.00.01,fa=HP-UX_B.11.00_32,
v=HP:
/usr/conf/lib/libbtlan0.a:
FILESET EISA100BT: libbtlan0: Version: B.11.00.07 P
HNE_28636 $Date: 2003/02/07 21:50:53 $
100BT-EISA-RUN.100BT-RUN,fr=B.11.00.01,fa=HP-UX_B.11.00_32,
v=HP:
/usr/lib/nls/msg/C/dsbtlan0.cat:
None
/usr/lib/lanadmin/libdsbtlan0.sl:
EISA100BT LANADMIN: libdsbtlan0: Version: B.11.00.0
7 PHNE_28636 $Date: 2003/02/07 22:22:54 $
100BT-EISA-RUN.100BT-INIT,fr=B.11.00.01,fa=HP-UX_B.11.00_32,
v=HP:
/usr/sbin/hpeisabt_init:
None
/usr/newconfig/etc/rc.config.d/hpeisabtconf:
None
/sbin/init.d/hpeisabt:
None
100BT-EISA-FMT.100BT-FORMAT,fr=B.11.00.01,
fa=HP-UX_B.11.00_32,v=HP:
/usr/lib/libeisa100btfmt.sl:
EISA100BT NETTL: libeisa100btfmt: Version: B.11.00.
07 PHNE_28636 $Date: 2003/02/07 22:25:57 $
/usr/lib/nls/msg/C/fmteisa100bt.cat:
None
cksum(1) Output:
100BT-EISA-KRN.100BT-KRN,fr=B.11.00.01,fa=HP-UX_B.11.00_32,
v=HP:
1121102905 309392 /usr/conf/lib/libbtlan0.a
100BT-EISA-RUN.100BT-RUN,fr=B.11.00.01,fa=HP-UX_B.11.00_32,
v=HP:
3862894740 3138 /usr/lib/nls/msg/C/dsbtlan0.cat
1455904787 36864 /usr/lib/lanadmin/libdsbtlan0.sl
100BT-EISA-RUN.100BT-INIT,fr=B.11.00.01,fa=HP-UX_B.11.00_32,
v=HP:
780528253 5258 /usr/sbin/hpeisabt_init
340626021 1254 /usr/newconfig/etc/rc.config.d/hpeisabtconf
2418239947 7667 /sbin/init.d/hpeisabt
100BT-EISA-FMT.100BT-FORMAT,fr=B.11.00.01,
fa=HP-UX_B.11.00_32,v=HP:
1526256771 16384 /usr/lib/libeisa100btfmt.sl
3989282158 5124 /usr/lib/nls/msg/C/fmteisa100bt.cat
Patch Conflicts: None
Patch Dependencies:
s700: 11.00: PHNE_14106
s800: 11.00: PHNE_14106
Hardware Dependencies: None
Other Dependencies:
The speed and duplex setting using SAM will work only
if the SAM patch PHCO_17792 or any patch superseding
it and, the lan common patch PHNE_17113 or any patch
superseding it is installed.
Supersedes:
PHNE_13543 PHNE_16154 PHNE_16403 PHNE_19200 PHNE_23981 PHNE_24725
PHNE_27534
Equivalent Patches:
PHNE_28635:
s700: 10.20
s800: 10.20
PHNE_28637:
s700: 11.11
s800: 11.11
Patch Package Size: 190 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_28636
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHNE_28636.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHNE_28636. 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_28636.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHNE_28636.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHNE_28636.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
1. A new copy of the hpeisabtconf file is provided
under the directory /usr/newconfig/etc/rc.config.d.
This new hpeisabtconf is modified to support new
speed/duplex setting options for startup script.
Copy this configuration file and incorporate any
previous modifications to the
/etc/rc.config.d/hpeisabtconf file to this new
copy and replace the working configuration file
/etc/rc.config.d/hpeisabtconf with it.
-----End of Document ID: PHNE_28636------------------------------------------
Document ID: PHNE_28795
Date Loaded: 20030515
Title: s700_800 11.22 Cumulative Mux and Pty Patch
Patch Name: PHNE_28795
Patch Description: s700_800 11.22 Cumulative Mux and Pty Patch
Creation Date: 03/05/13
Post Date: 03/05/15
Hardware Platforms - OS Releases:
s700: 11.22
s800: 11.22
Products: N/A
Filesets:
OS-Core.CORE2-KRN,fr=B.11.22,fa=HP-UX_B.11.22_IA,v=HP
Automatic Reboot?: Yes
Status: General Release
Critical: No
Category Tags:
defect_repair general_release
Path Name: /hp-ux_patches/s700_800/11.X/PHNE_28795
Symptoms:
PHNE_28795:
( SR:8606264304 CR:JAGae28634 )
Modem Dial-Out/Dial-In do not work on Serial ports.
( SR:8606290691 CR:JAGae54537 )
Serial ports do not work when set to baud rates other than
9600.
Defect Description:
PHNE_28795:
( SR:8606264304 CR:JAGae28634 )
Modem Dial-Out/Dial-In on Serial ports returns error due to
their improper Initialization.
Resolution:
Serial port Initialization have been corrected.
( SR:8606290691 CR:JAGae54537 )
Data is not transmitted when baud rate is set to value
other than 9600 for Serial ports.
Resolution:
Initialization code now uses appropriate divisor values for
baud rates other than 9600.
Enhancement:
No
SR:
8606264304 8606290691
Patch Files:
OS-Core.CORE2-KRN,fr=B.11.22,fa=HP-UX_B.11.22_IA,v=HP:
/usr/conf/lib/libwsio-pdk.a(asio0.o)
what(1) Output:
OS-Core.CORE2-KRN,fr=B.11.22,fa=HP-UX_B.11.22_IA,v=HP:
/usr/conf/lib/libwsio-pdk.a(asio0.o):
asio0.c $Date: 2003/04/23 03:17:06 $Revision: r11.22
/1 PATCH_11.22 (PHNE_28795)
cksum(1) Output:
OS-Core.CORE2-KRN,fr=B.11.22,fa=HP-UX_B.11.22_IA,v=HP:
3011762907 115144 /usr/conf/lib/libwsio-pdk.a(asio0.o)
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes: None
Equivalent Patches: None
Patch Package Size: 60 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_28795
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHNE_28795.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHNE_28795. 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_28795.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHNE_28795.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHNE_28795.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
-----End of Document ID: PHNE_28795------------------------------------------
Document ID: PHNE_28567
Date Loaded: 20030514
Title: s700_800 11.00 ONC/NFS General Release/Performance Patch
Patch Name: PHNE_28567
Patch Description: s700_800 11.00 ONC/NFS General Release/Performance Patch
Creation Date: 03/04/29
Post Date: 03/05/14
Hardware Platforms - OS Releases:
s700: 11.00
s800: 11.00
Products: N/A
Filesets:
OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32,v=HP
NFS.NFS-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32,v=HP
OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP
NFS.NFS-KRN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP
OS-Core.CORE-ENG-A-MAN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
NFS.NFS-CLIENT,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
NFS.NFS-PRG,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
NFS.KEY-CORE,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
NFS.NFS-CORE,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
NFS.NISPLUS-CORE,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
NFS.NFS-SERVER,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
NFS.NFS-SHLIBS,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
NFS.NIS-CORE,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
NFS.NIS-CLIENT,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
NFS.NIS-SERVER,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
NFS.NFS-ENG-A-MAN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
InternetSrvcs.INETSVCS-INETD,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
NFS.NFS-64SLIB,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
NFS.NFS-64ALIB,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
Automatic Reboot?: Yes
Status: General Release
Critical:
No (superseded patches were critical)
PHNE_28136: PANIC HANG ABORT CORRUPTION MEMORY_LEAK
PHNE_28102: HANG ABORT
PHNE_27217: PANIC HANG ABORT
PHNE_26387: PANIC
PHNE_25626: HANG ABORT
PHNE_25484: ABORT
PHNE_24909: HANG
PHNE_24034: HANG ABORT CORRUPTION
PHNE_23833: PANIC HANG ABORT
PHNE_23249: HANG
PHNE_22642: ABORT PANIC
PHNE_17586: PANIC
Data Page Fault
PHNE_17247: PANIC
Data Page Fault
PHNE_16599: PANIC HANG
Assertion Failure/vn_rele Panic
System hang/semaphore deadlock
PHNE_14919: CORRUPTION
Data destroyed on Server (with warning)
PHNE_14620: PANIC
Data memory protection fault
PHNE_13208: HANG
Category Tags:
defect_repair enhancement general_release critical panic
halts_system corruption memory_leak
Path Name: /hp-ux_patches/s700_800/11.X/PHNE_28567
Symptoms:
PHNE_28567:
nfsstat
SR: 8606308270
DTS: JAGae71305
The "nfsstat -m" command does not display NFS PV3
information.
PHNE_28136:
automountd libautofs.a
SR: 8606278982
DTS: JAGae43038
An AutoFS mounted file system using the "-hosts" map
can take a long time to mount when the environment
contains dead NFS servers.
libautofs.a
SR: 8606287136
DTS: JAGae51075
The contents of a directory mounted with AutoFS
become unavailable, and the directory cannot be used,
mounted, or unmounted.
libautofs.a
SR: 8606274519
DTS: JAGae38596
After unmounting all the AutoFS mount points through
the script "nfs.client stop", the system panics if it
tries to access an unmounted directory.
libautofs.a
SR: 8606267508
DTS: JAGae31750
A process is able to write into a read-only
automounted file system.
libnfs.a
SR: 8606267227
DTS: JAGae31470
The system panics after a read/write NFS exported
file system is unmounted and then re-mounted as
read-only without re-exporting the file system.
libnfs.a
SR: 8606269865
DTS: JAGae34105
When Intergraph's DiskShare NFS server returns zero
bytes for the preferred and/or maximum transfer size
of the READ/WRITE operation, the HP-UX NFS client
panics.
libnfs.a
SR: 8606274703
DTS: JAGae38780
NFS pathconf(_PC_CHOWN_RESTRICED) and fpathconf
(_PC_CHOWN_RESTRICED) return 0 when chown is not
restricted instead of -1, the POSIX compliant result.
libnfs.a mount
SR: 8606272309
DTS: JAGae36449
Using loopback NFS mounts, the server may hang due to
a deadlock condition.
libnsl.1/a
SR: 8606288821
DTS: JAGae52752
Calls to netdir_getbyname() from a multithreaded
process may hang or terminate with SIGSEGV or SIGBUS.
libnsl.1/a
SR: 8606282498
DTS: JAGae46451
Memory/file-descriptor leak in RPC multi-threaded
server programs, if the client tries to connect using
a version number that is unsupported by the server.
The memory leak may result in the server dumping core
and terminating. This can also cause the server to
quickly run out of file descriptors.
libnsl.1/a
SR: 8606291642
DTS: JAGae55409
Memory based XDR stream implementations do not
function properly.
librpc.a
SR: 8606289500
DTS: JAGae53431
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.
librpc.a
SR: 8606256016
DTS: JAGae20331
Threads accessing an NFS directory hang for a long
time with "bindresvport: loop-twice port assigned ..."
messages other than port 512 logged in syslog.log.
librpc.a
SR: 8606271824
DTS: JAGae36003
The system reports "vmunix: bindresvport: loop_twice
port assigned 512" messages.
librpc.a
SR: 8606282662
DTS: JAGae46615
The message "NFS server xxxx not responding still
trying" is seen on a client while attempting to
establish an NFS TCP connection, and the connection
is in the LISTEN state.
librpc.a
SR: 8606284964
DTS: JAGae48906
Data corruption while using XDR function
xdrmblk_getlong() with a 64-bit kernel.
nfsstat
SR: 8606275551
DTS: JAGae39627
If an NFS server listed in the /etc/mnttab file
is down or there are network problems, the
"nfsstat -m" call hangs.
rpc.lockd
SR:8606284885
DTS:JAGae48827
The number of file locks (nflocks) grows over a long
period of time, eventually causing NFS to lock up.
The only workaround is to restart NFS.
PHNE_28102:
automount
SR: 8606288394
DTS: JAGae52325
Incorrect permissions for the log file.
automount automountd
SR: 8606286563
DTS: JAGae50502
Incorrect configuration for AutoFS.
domainname domainname.1 ypinit ypserv ypxfrd
SR: 8606276334
DTS: JAGae40412
Problem with ypxfrd.
libnsl.1/a
SR:8606274555
DTS:JAGae38632
Showmount dumps the core with SIGSEGV.
libnsl.1/a
SR: 8606274502
DTS: JAGae38579
RPC does not function properly.
libnsl.1/a
SR: 8606281883
DTS: JAGae45826
The netdir_getbyname() routine using NIS can hang
under certain circumstances.
rpc.yppasswdd
SR:8606276016
DTS:JAGae40093
The rpc.yppasswdd process dies.
PHNE_27217:
automountd libautofs.a
SR: 8606264317
DTS: 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
(DevIDs11) 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 (DeviceIDs11) is
not installed, this product update to HP-UX will
have no impact on your system.
automountd
SR: 8606256845
DTS: JAGae21158
The /var/adm/automount.log file is shipped incorrectly.
automountd
SR: 8606242021
DTS: 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.
automountd libautofs.a
SR: 8606229377
DTS: JAGad98430
AutoFS mounted file systems never get unmounted.
automountd
SR: 8606245876
DTS: 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>
automountd
SR: 8606234968
DTS: 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.
automountd libautofs.a
SR: 8606233931
DTS: 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.
automountd
SR: 8606259713
DTS: JAGae24031
AutoFS problem.
clear_locks clear_locks.1m
SR: 8606248269
DTS: JAGae14669
If a client's /var/statmon/sm directory contents are
destroyed, future lock requests hang.
libautofs.a
SR: 8606271227
DTS: JAGae35462
The ls command will hang when users try to access
a dead server after some systems with mounted
directories are shut down.
libautofs.a
SR: 8606277106
DTS: JAGae41178
Under heavy load, file systems mounted with AutoFS
never get unmounted, even after the system load has
decreased.
libautofs.a
SR: 8606232532
DTS: JAGae01767
AutoFS mounted directories are empty.
libautofs.a
SR: 8606221909
DTS: JAGad91027
System panic occurs while AutoFS is unmounting
the idle AutoFS mount points. The panic string
is "spinlocks held with M_WAITOK".
libautofs.a
SR: 8606226778
DTS: 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
libautofs.a
SR: 8606248870
DTS: 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.
libnfs.a
SR: 8606147221
DTS: JAGad16564
Problem with privileged groups.
libnfs.a
SR: 8606245329
DTS: JAGae11799
A system hangs or panics when issuing a "ln"
command.
libnfs.a
SR: 8606257688
DTS: JAGae21991
Client hangs when trying to lock a remote file.
libnsl.1/a
SR: 8606264087
DTS: JAGae28412
When a 64-bit RPC application uses UNIX authentication
flavor, the RPC server does not properly decode the
client credentials.
libnsl.1/a
SR: 8606254087
DTS: JAGae18419
The rpcbind process increases in size and stops
responding to client requests. This requires
rpcbind needs to be killed and restarted.
librpc.a
SR: 8606257219
DTS: JAGae21525
Accessing a TCP AutoFS mount point causes the
system to hang.
librpc.a
SR: 8606265228
DTS: JAGae29556
Spinlock deadlock panic due to a lock being
held too long.
mountd.1m
SR: 8606249559
DTS: JAGae15949
The '-p' option for rpc.mountd described in
the man page does not function as described.
mountd.1m
SR: 8606132817
DTS: JAGad01965
rpc.mountd no longer supports the '-e' and '-n'
options but the man page for rpc.mountd still
shows both options being available.
nfs.core
SR: 8606256846
DTS: JAGae21159
The /var/spool/rexd directory is shipped incorrectly.
mount umount
SR: 8606235172
DTS: 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
nfsconfcol
SR: 8606234034
DTS: JAGae03255
The nfsconfcol script is not removing the target
data files before writing to them.
rpc.lockd rpc.statd
SR: 8606249576
DTS: JAGae15966
A client's attempt to acquire a lock may result in a
delay or a hang.
rpc.lockd
SR: 8606180770
DTS: JAGad49991
Blocked lock requests on a client system hang.
rpc.lockd
SR: 8606259831
DTS: JAGae24149
A client system hangs when trying to lock a file.
rpc.lockd rpc.statd
SR: 8606244127
DTS: 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.
rpc.mountd
SR: 8606255006
DTS: JAGae19335
Exported directories cannot be mounted.
PHNE_27213:
{Site Specific Patch}
PHNE_26387:
libautofs.a
SR: 8606248624
DTS: JAGae15022
AutoFS causes a system panic with the panic string
"rm_autonode: No entry for <<address>>".
PHNE_25626:
automount
SR: 8606219527
DTS: 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.
libautofs.a
SR: 8606221217
DTS: JAGad90351
The "ll" command hangs in the case of an automounted
file system if the server is down.
libnfs.a
SR: 8606237277
DTS: JAGae06322
NFS PV2 client does not properly show the quota exceeded
error.
libnfs.a
SR: 8606228306
DTS: JAGad97363
A file has an unusual timestamp when created with open(2)
using O_EXCL flag.
libnsl.1/a
SR: 8606204999
DTS: JAGad74175
The ttsyncd process loops, occupying much of the CPU
usage and causing the system to slow down.
libnsl.1/a
SR: 8606218377
DTS: JAGad87526
A multi-threaded server leaks file descriptors under
heavy load if clients are running on the same box.
libnss_nisplus.1
SR: 8606221102
DTS: JAGad90236
Reactivating a user account that has been disabled on a
trusted NIS+ client fails.
librpc.a
SR: 8606172908
DTS: 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 has 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.
nsswitch.conf.4
SR: 8606188628
DTS: JAGad57842
The man page for nsswitch.conf does not reflect ldap as
an additional database source for nss backends.
rpc.rusersd
SR: 8606225120
DTS: JAGad94209
rpc.rusersd core dumps if more than 180 users have
logged in.
rpc.statd
SR: 8606224657
DTS: 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.
rpcgen
SR: 8606230660
DTS: JAGad99710
A Server stub generated by rpcgen logs error messages to
/dev/console.
ypserv
SR: 8606226735
DTS: JAGad95797
The inetd is unable to resolve services.
PHNE_25484:
rpc.lockd
SR: 8606245747
DTS: JAGae12206
rpc.lockd core dumps with a SIGBUS error during heavy
NFS file locking.
PHNE_24909:
libnfs.a
SR: 8606222617
DTS: JAGad91730
If NFS loopback mounts are used, potentially all nfsd
processes may get stuck in an NFS deadlock situation.
libnfs.a
SR: 8606205013
DTS: JAGad74189
The mount option 'grpid' does not return the correct
'gid' value on NFS PV2 and PV3.
libnsl.1/a
SR: 8606205779
DTS: JAGad74954
The automountd (AUTOFS) hangs/cores while attempting
to automount exported FS and reports 100% CPU
utilization.
libnsl.1/a
SR: 8606212242
DTS: JAGad81430
When a customer specifies a username 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.
libnss_nisplus.1
SR: 8606216548
DTS: JAGad85717
A password expires unexpectedly in an NIS+
environment.
libnss_nisplus.1
SR: 8606219558
DTS: 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.
yppasswdd.1m
SR: 8606199444
DTS: JAGad68631
The yppasswd command updates fields other than the user
password field in an NIS map.
PHNE_24034:
automountd
SR: 8606152534
DTS: JAGad21864
AutoFS can mishandle unmounts when a server is down,
which may appear as bdf command anomalies.
automountd
SR: 8606196567
DTS: JAGad65770
AutoFS cannot unmount a cachefs type file system.
automountd
SR: 8606160777
DTS: JAGad30096
AutoFS can not unmount hfs or cdrom file system types.
libautofs.a
SR: 8606176017
DTS: JAGad45257
AutoFS directories are empty under heavy NFS load.
libautofs.a
SR: 8606193515
DTS: JAGad62727
Duplicate entries for direct AutoFS mounts show up in the
/etc/mnttab file.
libnfs.a
SR: 8606197003
DTS: JAGad66201
Walk through large size buffer cache causes file access
performance degradation.
libnfs.a
SR: 8606203242
DTS: 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.
libnfs.a
SR: 8606146332
DTS: JAGad15675
The I/O throughput on a locked file is low compared to
the throughput on an unlocked file.
libnsl.1/a
SR: 8606207461
DTS: JAGad76637
rpcbind crashes with signal 10, Bus error (SIGBUS).
librpc.a
SR: 8606197306
DTS: JAGad66499
An NFS client becomes hung while performing many
lock operations on files in NFS mounted directories.
It also receives "bindresvport: loop_twice port
assigned 512" messages in the message buffer.
librpc.a
SR: 8606168123
DTS: 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.
nfs.client
SR: 8606181688
DTS: JAGad50904
On a system with active lofs mounts managed by AutoFS,
the "/sbin/shutdown" command may hang when the file
systems are unmounted.
nis.client, ypbind, ypinit, ypinit.1m, ypserv.1m
SR: 8606201620
DTS: 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.
rpc.lockd
SR: 8606184904
DTS: JAGad54106
rpc.lockd can cause a user process to hang, if a
loopback mount is specified with an alias hostname.
rpc.lockd
SR: 8606202370
DTS: JAGad71544
NFS locks remain when killing NFS loopback mounted client
applications.
rpc.statd
SR: 8606208446
DTS: JAGad77633
NFS file lock recovery fails because rpc.statd matches
the wrong hostname.
rpcbind
SR: 8606164889 8606173448
DTS: JAGad34186 JAGad42706
Customer Symptoms:
rpcbind core dumps with SIGBUS or SIGSERV.
PHNE_23833:
automount
SR: 8606175862
DTS: JAGad45102
Mount points of automounter directories are not
visible when executing the "ls" command.
automount
SR: 8606169011
DTS: JAGad38290
The automount process hangs, making automounter
mount points inaccessable.
automountd
SR: 8606160596
DTS: JAGad29916
The /var/adm/automount.log file fills up the /var
file system.
exportfs
SR: 8606171662
DTS: JAGad40926
exportfs sometimes does not work correctly when
invalid host names are present in a host list
in the /etc/exports file.
fsirand.1m
SR: 1653311530
DTS: JAGab46804
Unable to use fsirand() on JFS file system.
libnfs.a
SR: 8606178998
DTS: JAGad48223
Unnecessary NFS read before write is causing severe
decreases in write performance.
libnfs.a
SR: 8606165859
DTS: 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.
libnfs.a
SR: 8606178618
DTS: 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").
libnfs.a
SR: 8606175781
DTS: 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.
libnsl.1/a
SR: 8606183171
DTS: JAGad52387
UDP packets sent by remote users can cause RPC
applications to abort.
libnsl.1/a
SR: 8606186548
DTS: JAGad55752
RPC server running in TCP multithreading
mode develops a file descriptor leak when
clients are on same machine as the server.
Eventually the server fails to process
clients' requests when the process limit
is attained.
libnss_nis.1
SR: 8606179951
DTS: JAGad49173
getservbyname() using NIS returns NULL when
trying to resolve service aliases.
libnss_nisplus.1
SR: 8606172747
DTS: 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.
nfsstat.1m
SR: 8606173363
DTS: JAGad42623
The "man nfsstat" command does not display all of the
statistical data fields.
rpc.lockd
SR: 8606180764 8606180765
DTS: JAGad49985 JAGad49986
rpc.lockd causes user process to hang.
rpc.lockd
SR: 8606174017
DTS: JAGad43270
rpc.lockd drops the lock request from same process
for a different file.
rpc.lockd
SR: 8606185238
DTS: JAGad54440
Partial record unlocking in NFS does not work
properly.
rpc.lockd
SR: 8606179200
DTS: JAGad48424
rpc.lockd core dumps when user process is
interrupted with "control-c".
rpc.mountd
SR: 8606176384
DTS: JAGad45622
The boot process of a Linux client fails due to
rpc.mountd not allowing AUTH_NULL authentication.
ypxfr
SR: 8606164133
DTS: JAGad33433
The ypxfr command fails with the error message:
"ypxfr: bind_to_server clntudp_create error:
RPC unknown host".
PHNE_23249:
libautofs.a, libnfs.a, librpc.a
SR: 8606103740 8606159451
DTS: JAGab70789 JAGad28779
A multithreaded process can hang when performing NFS
file operations and concurrently writing core, forking,
performing debugger attachment or undergoing job
control.
PHNE_23247:
{Site Specific Patch}
PHNE_22642:
automount
SR: 8606155592
DTS: JAGad24909
Automount (automounter) coredumps when sent SIGUSR1
to force it to update the automaps.
automountd
SR: 8606160808
DTS: JAGad30127
When using AutoFS, NFS mount points do not enforce
quotas.
libautofs.a
SR: 8606135856
DTS: JAGad04988
Panic occurs when trying to umount a ufs filesystem
which is still in the process of mounting.
libautofs.a
SR: 8606159736
DTS: JAGad29062
Unexpected delay in unmounting of Autofs mounts.
libnfs.a
SR: 8606179269
DTS: JAGad48493
Poor NFS pv3 performance on 64-bit (V-class) on 11.0.
libnfs.a
SR: 8606161701
DTS: JAGad31017
When reopening an NFS file right after closing it,
file attribute related inconsistencies can occur.
libnfs.a
SR: 8606158230
DTS: JAGad27560
Unmount of an nfs file system causes a panic.
libnfs.a
SR: 8606163247
DTS: JAGad32551
Unable to remove an NFS tmp file, .nfsXXXX after
failing to create or write a file which has exceeded
the disk quota limit.
libnfs.a
SR: 8606166314
DTS: JAGad35601
Process using NFS can not be killed or stopped by
sending the process a signal (SIGKILL or SIGSTOP).
libnsl.1/a
SR: 8606140609
DTS: JAGad09968
Core dump occurs when user belongs to more than
16 groups.
libnsl.1/a
SR: 8606160400
DTS: JAGad29722
On installing PHSS_20014 and PHSS_21947, 100% CPU
is used up by 2 processes - opcmsgrd and opcdistm.
librpc.a
SR: 8606169796
DTS: JAGad39062
Data page fault panic due to bad machine name
length in NFS request.
librpc.a,nfsd
SR: 8606167053
DTS: 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. In this case, NFS/TCP on
the server has become inoperable due to a hang.
newkey
SR: 8606157592
DTS: JAGad26923
Newkey does not recognize the root password of the
remote machine and returns an error, "ERROR,
passwd differs from login passwd".
PHNE_22125:
libautofs.a
SR: 8606143877
DTS: JAGad13210
Using autofs, mount points become inaccessible
after a series of mount/unmount cycles.
libnfs.a
SR: 8606128739
DTS: JAGac86286
File corruption over NFS when NFS file server is
TOC'ed.
libnfs.a
SR: 8606144881
DTS: JAGad14221
HP NFS client performance is degraded as shown by
"nfsstat -c", it makes unnecessary GETATTR calls
for each read or write on files opened with
synchronous I/O flags set; and synchronous I/O
mode remains in effect for subsequent opens on an
NFS file opened once with synchronous I/O flags
set.
libnfs.a
SR: 8606147198
DTS: JAGad16541
CPU time is wasted by unnecessary calls to
compare_cred function in NFS PV3 client code.
libnfs.a
SR: 8606145970
DTS: JAGad15306
The stat() system call on NFS directories
shows a non-existent ACL.
libnfs.a
SR: 8606128493
DTS: JAGac84458
System panic when running "du -s" or
"find -name" on a 64 bit machine.
libnfs.a, librpc.a
SR: 8606160097
DTS: JAGad29423
Mount an NFS file system with non-interruptible
options remains interruptible.
libnfs.a
SR: 8606144617
DTS: JAGad13957
Using NFS, a read-only file open by one
process causes a "Permission denied"
error in an on-going write operation on
the same file by another process.
libnfs.a, librpc.a, nfsd
SR: 8606145517
DTS: JAGad14853
If NFS is stopped and restarted, the nfsd
processes do not get re-registered with rpcbind,
and rpcinfo commands fail.
libnfs.a, nfsd
SR: 8606146885
DTS: JAGad16228
nfsd unregisters a running nfsd process on
startup.
librpc.a
SR: 8606155004
DTS: JAGad24321
When a server is down, an NFS/TCP client process
e.g. a bdf command can hang.
librpc.a
SR: 8606143872
DTS: JAGad13205
NFS/TCP mounting and unmounting eventually hangs.
librpc.a
SR: 8606144478
DTS: JAGad13818
NFS/TCP connections are not torn down when the
peer sends a FIN.
nfs.core
SR: 8606159847
DTS: JAGad29173
File permission change on /etc/services file.
rpc.lockd
SR: 8606145476
DTS: JAGad14812
Lockd/statd client crash recovery does not work.
rpc.mountd
SR: 8606127276
DTS: JAGac68822
A failing mount request may return a wrong error
code.
rpc.statd
SR: 8606143409
DTS: JAGad12739
A looping problem in rpc.statd occurs between the
server and SGI clients.
ypserv
SR: 8606155843
DTS: JAGad25155
YPSERV fails to return all groups for id/group
command when concurrent access is allowed to maps.
PHNE_21376:
automountd
SR: 8606128485
DTS: JAGac84450
Automountd not triggered for mounts
anymore when autonode has NULL flag.
exportfs
SR: 8606108804
DTS: JAGab78579
When a user attempts to mount an exported
filesystem which is a symbolic link to an
actual directory or filesystem on an NFS
server, a "Permission Denied" error occurs.
This occurs after installing patch PHNE_18221.
libautofs.a
SR: 8606128485
DTS: JAGac84450
Automountd not triggered for mounts
anymore when autonode has NULL flag.
libnsl.1/a
SR: 8606134593
DTS: JAGad03728
automountd coredumps in the NIS+ environment.
libnsl.1/a
SR: 8606143750
DTS: JAGad13073
When using the TCP loopback transport a
memory leak may occur.
libnsl.1/a, rpc.nisd
SR: 8606107751
DTS: JAGab78042
When using NIS+ with TCP, as the number of open
file descriptors increases, file table overflow
errors occur in the syslog.log file and user
information is not recognized.
rpc.lockd
SR: 8606131496
DTS: JAGad00646
Failover occurs with the serviceguard NFS package because
the rpc.lockd daemon fails (terminates) during periods of
high memory usage (running out of memory).
rpc.statd
SR: 8606131366
DTS: JAGad00517
The rpc.statd daemon core dumps during high memory
utilization (when available memory runs low).
rpc.statd
SR: 8606136063
DTS: JAGad05198
rpc.statd aborted with memory leak due to unresolved
host requests.
rpcbind
SR: 8606131978
DTS: JAGad01128
Rpcbind exhibits wrong behavior on shutdown.
ypserv
SR: 8606134296
DTS: JAGad03431
ypserv becomes unavailable for the local ypbind and
for the other yp clients.
PHNE_20627:
libnfs.a
SR: 8606134214
DTS: JAGad03354
Extremely slow performance of commands or utilities
operating on large directories over NFS.
SR:8606109663
DTS:JAGab82363
Removing an NFS file causes a file named ".nfsXXXX"
(where XXXX is a pid) to be created.
SR:8606135799
DTS:JAGad04931
The i-node for the ".." directory entry of a subdirectory
is not updated on an NFS client after that subdirectory
is moved up one directory level on the NFS client,
ie - moved to "..".
SR:8606135800
DTS:JAGad04932
Output from "tail -f" on an NFS file does not reflect any
appends made to the file on the NFS server if a "umount"
is performed on the NFS file system while the "tail -f"
is being executed.
PHNE_20371:
autofs/mount
SR: none
DTS: JAGab68200
Autofs/mount can fail when the system
hostname is longer than 8 characters.
automount
SR: none
DTS: JAGab68200
Autofs/automount can fail when the system
hostname is longer than 8 characters.
automount,automountd
SR: 8606106692
DTS: JAGab76019
automount with stalemounts causing duplicate
mnttab entries & lock problems.
symptoms of automount are: stale nfs handles are
seen in mnttab after an unmount and when the
mount is repeated (in this case a cdrom...) the
mnttab contains two entries for the device. One
of which is invalid. This second (stale) handle
causes subsequent locking problems.
automountd
SR: none
DTS: JAGab68200
Autofs/automountd can fail when the system
hostname is longer than 8 characters.
automountd
SR: 8606107366
DTS: JAGab77563
Autofs exhibits wrong behavior in processing
executable maps.
automountd
SR: 8606107274
DTS: JAGab77060
automount option -proto=udp causes mounts to fail
libautofs.a
SR: 8606107122
DTS: JAGab76805
autofs - shell gets intermittent "cannot execute"
libautofs.a
SR: 8606106938
DTS: JAGab76453
automounter hangs when trying to mount cachefs
filesystem (reported on HP-UX 10.20)
libnsl.1/a
SR: none
DTS: JAGaa43721
When accessing remote files over NFS, the
NFS protocol on HP-UX only uses UDP.
libnsl.1/a
SR: none
DTS: JAGab68200
NIS and other ONC/NFS systems can fail when
libnsl does not provide support for a system
hostname longer than 8 characters.
libnsl.1/a
SR: 8606107366
DTS: JAGab77563
Autofs exhibits wrong behavior in processing
executable maps.
libstraddr.1
SR: none
DTS: JAGab68200
Libstraddr routines can fail when the system
hostname is longer than 8 characters.
make.script
SR: 8606107068
DTS: JAGab76707
ypmake and Makefile failed
on some mail.aliases file and mail.aliases map
is corrupted.
mount
SR: none
DTS: JAGaa43721
When accessing remote files over NFS, the
NFS protocol on HP-UX only uses UDP.
nfs.core
SR: none
DTS: JAGaa43721
When accessing remote files over NFS, the
NFS protocol on HP-UX only uses UDP.
nfs/mount
SR: none
DTS: JAGab68200
Nfs/mount can fail when the system
hostname is longer than 8 characters.
nfsstat
SR: none
DTS: JAGaa43721
When accessing remote files over NFS, the
NFS protocol on HP-UX only uses UDP.
nisplus/nisserver
SR: none
DTS: JAGab68200
Nisplus can fail when the system hostname
is longer than 8 characters.
rpcinfo
SR: none
DTS: JAGab68200
Rpcinfo can fail when the system hostname
is longer than 8 characters.
rpc.lockd
SR: 5003459362
DTS: JAGab12595
file locks hang when NFS server uses
fully-qualified hostname
rpc.lockd
SR: 8606113678
DTS: JAGac07192
Application hangs on client when obtaining NFS
lock on server
setoncenv
SR: none
DTS: JAGaa43721
When accessing remote files over NFS, the
NFS protocol on HP-UX only uses UDP.
ypmake
SR: 8606107068
DTS: JAGab76707
ypmake and Makefile failed
on some mail.aliases file and mail.aliases map
is corrupted.
PHNE_20344:
libnfs.a librpc.a nfs_iface.o
SR:N/A
DTS:JAGac42842
NFS version 3 only supports up to 8k read/write
transfer size.
libnfs.a
SR:8606110199
DTS:JAGab82902
Memory leak in NFS version 3 at rfs3_readdirplus().
libnfs.a
SR: 8606125471
DTS: JAGac40861
Poor NFS performance relative to SPECsfs97 benchmark.
libnfs.a
SR:8606107676 8606124555
DTS:JAGab77944 JAGac39938
NFS performance problems with NFS client
readdir cache.
libnfs.a
SR:8606126860
DTS:JAGac59701
"do_readdirplus" variable not available in the NFS
kernel.
PHNE_19759:
1.fuser -f on a file does not return pid of opener
2.compress command on a SUN client fails due to invalid
name length returned by NFS pathconf from HP Server
3.getmount_entry() returns down status for all hard
mounted NFS file systems
PHNE_19620:
automountd
DTS: JAGab72053
NFS - autofs (11.0) hangs when unmount from down server
SR: 8606103364
DTS: JAGab70009
replicated automounts fail if system parameter
maxfiles > 2048
libautofs.a
DTS: JAGab73529
autofs w/cachefs can panic in cachefs_root()
SR: 8606105077
DTS: JAGab72920
AutoFS failure with cdrom.
The failure occurs in two ways:
- Hangs if indirect mount
- Error if direct mount
libnsl.1/a
SR: 8606104454
DTS: JAGab41115
rpcinfo gets error "can't contact rpcbind: RPC:
Program not registered" from remote rpcbind on
RPCB_GETADDR/RPCB_DUMP request for list of services.
libnss_nis.1
SR: 5003465898
DTS: JAGab20796
getservbyname() is slow.
librpcsvc.a
SR: 8606103503
DTS: JAGab70329
rpc.mountd dies with SIGSEGV if rmtab is large and
showmount -a is done.
rpc.lockd
SR: 8606105833
DTS: JAGab74177
Virtual nfs servers have locking problems.
DTS: JAGab45462
rpc.lockd uses port numbers within reserved port
range, 600 to 1024.
DTS: JAGab15223
Processes waiting to lock an nfs file which has been
deleted do not get woken up, resulting in a hang.
DTS: JAGaa45544
Locks hang and rpc.lockd logs error messages about
the local and remote lock tables being inconsistent.
rpc.lockd causes lock queue corruption with loopback
mounts.
rpc.mountd
DTS: JAGab45462
rpc.mountd uses port numbers within reserved port
range, 600 to 1024.
rpc.statd
DTS: JAGab45462
rpc.statd uses port numbers within reserved port
range, 600 to 1024.
PHNE_18221:
libautofs.a
SR: 1653298828 5003458299 1653299826 5003462911
SR: 1653304972
DTS: JAGab00144 JAGab03833 JAGab11283 JAGab16597
DTS: JAGab18083
JAGab00144 - AutoFS is not triggering re-mount
JAGab03833 - AutoFS hangs even with PHNE_17200
JAGab11283 - cp(1) fails to inactive direct mount
JAGab16597 - mv command fails in AutoFS direct mnt
JAGab18083 - getcwd() fails with AutoFS filesys
libnsl.1/a
SR: 5003463992
DTS: JAGab17512
Applications fail to create a server side RPC
endpoint due to a failure to obtain a reserved port.
libnsl.1/a
SR: 5003465880
DTS: JAGab20797
A multi-threaded application which calls
getservbyname() failed.
libnss_compat.1
SR: none
DTS: JAGab03573
64-bit application using 'getgrent' fails if
nsswitch.conf uses group:compat
rpc.lockd
SR: 5003446203
DTS: JAGaa46687
rpc.lockd runs out of file descriptors
and returns the following error in
its log file:
RPC: Remote system error
rpc.mountd
SR: 5003439471 5003463331
DTS: JAGaa42795 JAGab17386
ER for share(1M) options and defect in "showmount -e"
rpc.mountd
SR: none
DTS: JAGaa44896 JAGaa24142
rpc.mountd - server allows mounts not on access list
rpc.pcnfsd
SR: 5003460030
DTS: JAGab13451
rpc.pcnfsd does not accept '~' for
file names.
rpc.statd
SR: 5003446195
DTS: JAGaa46688
rpc.statd fails on fopen when more than
260 entries are in /var/statmon/sm.
PHNE_17586:
1. Huge directory reads take too long and client system
performance degrades as NFS IO activity increases.
2. System panics with data page fault when 0 len UDP
pkt received by NFS server system.
3. Root users are denied access to valid root exported
file systems on 11.0 server.
4. Root users on NFS PV3 client who do not have file
permissions for read/write are allowed to open file
successfully but denied access when reading or
writing the file.This behaviour is inconsistent
with non-root users who are denied access at file
open time.
5. NFS requests from anonymous NT clients are rejected.
6. Large file reads on a 32 bit NFS client does not work,
file copy completes without errors but no data is copied
to the target file.
7. When copying large file from local disk to NFS
file system,more bytes than necessary are copied to
the file and the resulting file size is bigger.
8. Buffering of data on NFS file is permanently
turned off by the client system even after releasing
all file locks and closing all file descriptors.
9. Exportfs prints debug messages in syslog.log.
10. When a file is opened with O_CREAT|O_TRUNC|O_EXCL
flags set and the file does not already exist,open is
expected to succeed but for NFS V3 files,open seems to
fail with EACCES.
11. When file has Mandatory lock mode set,HP NFS V3
allows file read/write access when no locks exist on
the file,but NFS V2 denies file read/write access.
Also,NFS V3 client hangs application when locks exist
on the file.This behaviour is inconsistent with SUN's,
where NFS V3 and V2 access is denied consistently at
file open time when file has mandatory lock mode set.
12. Data page fault panic in mvfs due to NFS server
initialization corrupting global memory at boot up.
PHNE_17247:
1. Data page fault panic due to NFS server
initialization corrupting global memory at boot up.
2. Large file reads on a 32 bit NFS client does not work,
file copy completes without errors but no data is copied
to the target file.
3. When copying large file from local disk to NFS
file system,more bytes than necessary are copied to
the file and the resulting file size is bigger.
PHNE_17200:
Makefile
SR: none
DTS: JAGaa73221
When rpc.mountd tries to match a hostname
in netgroup, the given hostname has to be
the exact same as it is stored in the
netgroup.
automount
SR: 5003450916
DTS: JAGaa93190
automount loops using replicated server
automount
SR: 5003362707
DTS: JAGaa25720
automount fails to mount all exported
file systems.
automountd
SR: 1653267377
DTS: JAGaa24193
autofs holding lock on /etc/.mnttab.lock.
automountd
SR: none
DTS: JAGaa95626
Logging information is hard to
read.
automountd
SR: none
DTS: JAGaa40567
executable map processing may grant
caller additional privileges.
libautofs.a
SR: 5003445601
DTS: JAGaa46003
NFS - autofs hangs when manual unmounts used
nfs.core
SR: none
DTS: JAGaa43075
rexd does not start since it cannot find
/var/spool/rexd on system.
nis.server
SR: none
DTS: JAGaa94166
nis.server script won't run correctly unless the
new namesvrs is installed at the same time.
rpc.mountd
SR: 5003454371
DTS: JAGaa94274
rpc.mountd deadlock with automount
rpc.mountd
SR: 5003447003
DTS: JAGaa45940
NFS - rpc.mountd MOUNT performance is very slow
rpc.nispasswdd
SR: 1653286955
DTS: JAGaa44956
when rpc.nispasswdd is running with "-g"
option, it corrupts the credential of a
user who has a credential and changes
password.
rpc.pcnfsd
SR: 5003405118 5003336198
DTS: JAGaa26176 JAGaa25473
1) PC users fail to authenticate when trusted
system is enabled.
2) pcnfsd stops responding to all requests when
a request is made to printer that is down.
rpc.pcnfsd
SR: 1653293043
DTS: JAGaa93189
User authentication fails for users who
do not use a shell that ends with "sh".
rpc.rstatd
SR: 5003442574
DTS: none
The amount of memory associated with the
rpc.rstatd process continues to grow
without ever being returned to the system.
rpc.statd
SR: 5003445858
DTS: JAGaa45938
rpc.statd core dumps with SIGSEGV.
rpcbind
SR: none
DTS: JAGaa92935
rpcb_unset() does not remove all registration
entries from rpcbind.
rpcgen
SR: none
DTS: JAGaa57297
rpcgen generated makefiles fail to build targets
rpcgen
SR: 1653291484 1653291500
DTS: JAGaa57208 JAGaa57209
rpcgen generated file fails to compile.
stdhosts
SR: none
DTS: JAGaa94167
stdhosts command fails on lines longer
than 256 char.
ypinit
SR: none
DTS: JAGaa41361
ypinit has warning message.
ypmake
SR: none
DTS: JAGaa73221
When rpc.mountd tries to match a hostname
in netgroup, the given hostname has to be
the exact same as it is stored in the
netgroup.
ypserv
SR: 5003448159
DTS: JAGaa46689
ypserv is running out of file descriptors
due to not releasing them.
ypserv
SR: none
DTS: JAGaa41159
ypserv core in svc_freeargs ( a rpc routine)
after nslookup for a period of time.
ypxfr_1perday
SR: none
DTS: JAGaa43641
vhe_list should not be in the script.
PHNE_17101:
autofs
SR: none
DTS: none
Autofs fails to start on a 64-bit OS
unless PHNE_15638 has already been
installed.
nfsstat
SR: 5003444745
DTS: JAGaa44646
nfsstat -m exited with an error that it
could not open the mount table
PHNE_16599:
1. NFS server system panics with assertion failure
in vn_rele sometimes during NFS file locking/unlocking.
2. Too much rnode memory allocated resulting in gradual
shortage of free memory resource on the system.
3. NFS Version 3 mounted directories may appear to be
empty on the NFS client even though the directories exist
on the server file system.
4. A touch command to change the modification time stamp
of NFS file may cause system hang.
5. Some NFS clients may experience poor NFS Read
performance with HP servers when using NFS Version 3 mounts.
6. Invalid file system id returned to Statfs of
NFS Version 2 mounted file set.
PHNE_16470:
Makefile
SR: none
DTS: INDaa30982
vhe_list is no longer supported by NIS.
It needs to be removed from ypinit,
ypmake and /var/yp/Makefile.
automount
SR: none
DTS: JAGaa26320, JAGaa26354
Made debug logging change and checked
in the change for setmntent for read locks.
automount
SR: none
DTS: JAGaa40906
automount tries to remount already mounted directory
automount
SR: 1653270413
DTS: INDaa31358
logging data is difficult to read.
automountd
SR: 5003431353, 5003434654
DTS: none
1. duplicate entries in /etc/mnttab error
message in syslog
2. AutoFS will not unmount LOFS mounts
exportfs
SR: 1653270413
DTS: INDaa31358
logging data is difficult to read.
libautofs.a
SR: none
DTS: JAGaa24180
1. HOME env set to autofs directory on 64-bit 9808
system hangs gpm help.
2. Autofs hangs when running Netscape.
3. Autofs hangs when remounting hierarchical mounts.
libnsl.1/a
SR: 1653270413
DTS: INDaa31358
logging data is difficult to read.
libnsl.1/a
SR: 5003429845
DTS: INDaa31432
Compile of application using archived libraries
files with duplicate symbol __nss2herrno
libnsl.1/a
SR: 5003429456
DTS: INDaa31422
rpc.mountd stops running
libnsl.1/a
SR: none
DTS: JAGaa24798
CDE logins fail when user belongs to more then
16 groups.
libnsl.1/a
SR: none
DTS: INDaa30681
The performance of a 64-bit application
slows down when it uses the 32-bit cache
information in the ypbind file.
libnss_nisplus.1
SR: none
DTS: JAGaa40026
getxxxent leaks memory when using NIS+
libnss_nisplus.1
SR: 5003418210
DTS: JAGaa24152
Module ngetprpwent is missing
from libnss_nisplus.
librpcd_util.a
SR: 1653270413
DTS: INDaa31358
logging data is difficult to read.
librpcsoc.1
SR: none
DTS: INDaa30814
on command fails with the messages
on: failed to reach <host> at address <host address>
mknetid
SR: none
DTS: INDaa30115
mknetid cores when a user is in more that 20 groups
namesvrs
SR: none
DTS: INDaa30072
nis.server script fails if IBM is NIS master to
HP slave.
nfs.client
SR: none
DTS: JAGaa27109
Non-busy NFS mounts are frequently not
unmounted during nfs.client stop.
nfs.server
SR: none
DTS: JAGaa24199
local file systems are mounted when NFS client restarts
nfs_umount
SR: none
DTS: JAGaa27067
/sbin/fs/nfs/umount -aF nfs does not unmount
all NFS file systems.
nfsstat
SR: none
DTS: INDaa31388
Executable hangs.
nis.server
SR: none
DTS: INDaa30072
nis.server script fails if IBM is NIS master to
HP slave.
on
SR: 5003420992
DTS: INDaa30864
on fails when home directory is mounted via
autofs.
rpc.lockd
SR: 1653270413
DTS: INDaa31358
logging data is difficult to read.
rpc.lockd
SR: none
DTS: JAGaa40591
Lock failure caused data corruption
rpc.lockd
SR: none
DTS: JAGaa26538
logged messages causes file system to fill
rpc.lockd
SR: 1653254474, 5003417998
DTS: JAGaa26354, JAGaa26221, JAGaa26257
The rpc.lockd tracing was improper format.
Loss of UDP NFS file locking packets resulted
in a growing message queue. rpc.lockd processes
control C (NLM_CANCEL) incorrectly when the server is
a SUN system.
rpc.mountd
SR: none
DTS: JAGaa24186
Believes there is a problem
in the way the daemon checks to see if it is up.
rpc.mountd
SR: 1653270413
DTS: INDaa31358
logging data is difficult to read.
rpc.mountd
SR: 1653266148
DTS: INDaa31024
valid clients in the NFS server's export list
can not mount the NFS server.
rpc.pcnfsd
SR: 1653272484
DTS: JAGaa26373
Validity checks not performed on printer and
system name.
rpc.rexd
SR: 1653270413
DTS: INDaa31358
logging data is difficult to read.
rpc.rquotad
SR: 1653270413
DTS: INDaa31358
logging data is difficult to read.
rpc.rquotad
SR: none
DTS: INDaa31358
Executable hangs.
rpc.rstatd
SR: 1653270413
DTS: INDaa31358
logging data is difficult to read.
rpc.rusersd
SR: 1653270413
DTS: INDaa31358
logging data is difficult to read.
rpc.sprayd
SR: 1653270413
DTS: INDaa31358
logging data is difficult to read.
rpc.statd
SR: none
DTS: JAGaa26538
logged messages causes file system to fill
rpc.statd
SR: 4701392027
DTS: JAGaa26354, JAGaa26276
The debug logging needs change.
rpc.walld
SR: 1653270413
DTS: INDaa31358
logging data is difficult to read.
rpc.yppasswdd
SR: none
DTS: INDaa31524
If a password contains a ":", it cannot be changed
via NIS.
rpc.yppasswdd
SR: none
DTS: INDaa31380
rpc.yppasswdd does not update NIS maps when ptmp
and maps on diff file system.
rpcbind
SR: 1653270413
DTS: INDaa31358
logging data is difficult to read.
ypbind
SR: none
DTS: INDaa31412
ypbind cache file sometimes is not created
due to the value in an uninitialized time
stamp. The performance of NIS degrades
when cache file is absent.
ypbind
SR: none
DTS: INDaa31381
ypbind cache file cannot be created
due to a missing compilation flag.
The performance of NIS degrades
when cache file is absent.
ypinit
SR: none
DTS: INDaa30982
vhe_list is no longer supported by NIS.
It needs to be removed from ypinit,
ypmake and /var/yp/Makefile.
ypmake
SR: none
DTS: INDaa30982
vhe_list is no longer supported by NIS.
It needs to be removed from ypinit,
ypmake and /var/yp/Makefile.
ypmake
SR: none
DTS: INDaa31440
When a new map is made on the Master with
NOPUSH=1 option, on the Slave, transferring
the new map fails sometimes.
ypserv
SR: none
DTS: INDaa29252
ypserv stops answering some queries for
entries outside domain on a slow system.
ypxfr
SR: 5003418160
DTS: JAGaa24144
ypmake on the YP master reports a failure
when contacting a slave server
ypxfr
SR: none
DTS: none
Incorrect parameter declaration for the
function ypxfrd_getdbm.
PHNE_16017:
1. The setting of NFS file/directory modification and access
time stamps is inconsistent.
2. An HP NFS server does not permit NFS file/directory time
stamps to be set from a non-HP NFS client.
3. Copying a file from a 64-bit client causes the file
timestamp to be incorrectly set to Dec 31, 1969.
4. Poor NFS performance over 100BT.
PHNE_15638:
automountd:
1. No autofs support on HP-UX.
mount:
1. No autofs support on HP-UX.
umount:
1. No autofs support on HP-UX.
rup:
error exit code incorrect
libnsl:
rpcbind has memory leak
bindreserveport fails
rpc.statd:
gethostbyname called incorrectly.
rpc.lockd:
No support for shares and non-monitored locks in NLM
version 4
automount:
Messages written to syslog file without verbose option
nfs.client:
rpc.lockd does not reclaim locks after a server reboots.
PHNE_14919:
1. NFS write performance may be slow, and may be
particularly poor when large files are being closed or
synchronized.
2. NFS Server files may be accessed and possibly destroyed
when their permissions should not allow access.
3. NFS Remounts may fail with a "device busy" error.
4. Locking large files (> 2 GBytes) may encounter errors.
PHNE_14800:
NFS Performance as measured by the SPECsfs benchmark
gives an inadequate number of IOPS on the initial 11.0
system release.
PHNE_14772:
N/A
PHNE_14746:
rpcgen:
1. rpcgen displays an incorrect usage string
2. C++ applications fail to compile due to non-existent
header file. <sysent.h>
nfs.core:
1. rpcbind cannot receive messages on ticotsord device
rpc.nisd:
1. NISPLUS server can not resolve hostname using DNS for
NIS client.
(SR/DTS: 5003-395731/INDaa28803)
2. NIS+ clients sometimes get "NIS+ unreachable" message
when in fact NIS+ server(rpc.nisd) is up and running.
(SR/DTS: 5003-395558/INDaa29132)
nisaddent:
1. nisaddent adds empty passwd fields on a trusted system.
(DTS: INDaa28982)
nisserver:
1. nisserver creates unnecessary environment variables -
NIS_MASTER and NIS_SLAVE, and adds them into
/etc/rc.config.d/namesvrs file.
(SR/DTS: 5003-395582/INDaa29138)
2. nisserver script does not set up NIS+ server correctly
if
- NIS compat mode is not set, and if,
- nisserver was previously executed with NIS
compat mode set.
(SR/DTS: 5003-395582/INDaa29138)
nisclient:
1. nisclient has illegal grep syntax for hp
(DTS: INDaa28804)
2. nisclient -u script reports success even when
chkey fails
(SR/DTS: 5003-397422/INDaa29242)
nispopulate:
1. nispopulate has illegal grep syntax for hp
(DTS: INDaa28804)
libnss_nisplus.1:
1. 64-bit gethostbyname() returns 0.0.0.0 for the IP
address of a valid host stored in the NISPLUS table
hosts.org_dir.
(DTS: INDaa29686)
nisdefaults:
1. nisdefaults does not indicate if a principal is not
authenticated.
(SR/DTS: 5003-396655/INDaa29212)
nisstat:
1. nisstat -H hostname does not work.
(SR/DTS: 5003-395541/INDaa29137)
automount:
1. Old automount daemon conflicts with New automount
command
2. Automount daemon does not use NIS master map
rpc:
1. no entry for rpc.nisd_resolv
2. no entry for automountd
nfsconf:
1. No support for AutoFS
nfs.client:
1. No support for AutoFS
libstraddr.1:
1. 64-bit application can not send request on loopback
transport.
2. 64-bit library does not exist
libnsl.1:
1. Can not generate new thread after the 65th has been
created.
2. Can not create RPC MT Servers.
3. netdir_getbyname() returns different error message
for non-existent hosts.
4. 64-bit Cannot use loopback transports over RPC.
5. Can not create 64-bit RPC MT Servers.
6. 64-bit netdir_getbyname() returns different
error message for non-existent hosts.
libnsl.a:
1. Can not generate new thread after 65th has been
created
2. Can not create RPC MT Servers
3. netdir_getbyname() returns different error message
for non-existent hosts.
4. 64-bit application cannot use loopback transports
over RPC.
5. Can not create 64-bit RPC MT Servers.
6. 64-bit netdir_getbyname() returns different
error message for non-existent hosts.
vhe_altlog:
1. Obsoleted product vhe is still available.
vhe_getlist:
1. obsoleted product vhe is still available.
vhe_list:
1. obsoleted product vhe is still available.
vhe_mounter:
1. obsoleted product vhe is still available.
vhe_script:
1. obsoleted product vhe is still available.
config:
1. Loopback transport configuration files not moved
to correct location
unconfig:
1. Loopback transport files left after deinstall.
netconfig:
1. Customer configured information lost in /etc/netconfig
hosts:
1. Customer configured information lost in
/etc/net/[ticlts|ticots|ticotsord]/hosts
services:
1. Customer configured information lost in file
/etc/net/[ticlts|ticots|ticotsord]/services
rpc.rstatd:
1. When run from the command line, rpc.rstatd dies after 10
minutes.
keyserv:
1. keyserv registers a UDP port with rpcbind
nis_cachemgr:
1. nis_cachemgr registers a UDP port with rpcbind
(DTS: INDaa29627)
rpcbind:
1. Can not send request over loopback transport devices
to rpcbind
rpc.mountd:
rpc.mountd denies access to valid netgroup.
PHNE_14620:
1. System panics with a data memory protection fault
2. NFS unmounts may take several minutes with large
memory systems
PHNE_13208:
1.Processes hung when doing NFS file IO
2.NFS sub-system failed to respond under 2 way NFS IO stress
3.Sometimes returned invalid error during NFS Read/Write
Defect Description:
PHNE_28567:
nfsstat
JAGae71305
If device ID's are enabled, and the file systems
are configured such that the index for NFS PV3
file systems is a value other than 3, the
information for NFS PV3 file systems will not be
displayed when the "nfsstat -m" command is
executed.
Resolution:
Added a function call to get the file system
index instead of setting it to a constant value.
PHNE_28136:
automountd libautofs.a
JAGae43038
The AutoFS daemon automountd serializes mount and
unmount requests. When a mount request for a dead
NFS server is received it takes 75 seconds for
automountd to fail the mount request. During this
time no other mount or unmount requests can be
processed, even if the requests are for a live NFS
server.
Resolution:
The number of mount requests sent from the kernel
to automountd has been reduced which will decrease
the chance of automountd getting a request for a
dead NFS server. Also, no mount requests will be
sent to automountd without first checking to see
if the NFS server is up.
libautofs.a
JAGae51075
Threads in the AutoFS code are not synchronized
properly while one thread is trying to remove a
directory and another thread is sending a mount
request for the same directory. This causes AutoFS
to create a fresh directory with null flags.
Therefore AutoFS is unable send a mount request
for the newly created directory.
Resolution:
Measures have been taken to provide a proper
synchronization between the threads in AutoFS that
are accessing the same directory.
libautofs.a
JAGae38596
When the script "nfs.client stop" is run, it unmounts
all the AutoFS mount points. While unmounting the
AutoFS mount points, AutoFS does not verify whether or
not a directory entry under such an AutoFS mount point
is busy and therefore it frees the internal data
structures of the corresponding AutoFS mount point.
The system panics when some process tries to access a
directory entry under such an AutoFS mount point
because AutoFS' internal data structures no longer
exist.
Resolution:
AutoFS verifies whether or not the directory entries
under an AutoFS mount point are busy. If busy, the
mount point is not unmounted.
libautofs.a
JAGae31750
AutoFS is allowing a process to write into a
read-only file system. This is because AutoFS
is not verifying whether the underlying file
system is read-only or not.
Resolution:
AutoFS is now verifying whether the underlying
file system is read-only or not. If the underlying
file system is read-only then AutoFS returns
an error.
libnfs.a
JAGae31470
The NFS server does not see any changes made to an
exported file system. Because of this, making an
exported read-write mount point read-only through
remounting will result in a system crash in the NFS
server stack.
Resolution:
Modified the NFS server to check whether an exported
file system permits alterations before each attempt
to modify it, and aborts all modification requests on
a read-only file system.
libnfs.a
JAGae34105
Intergraph's DiskShare NFS server returns zero bytes
for the preferred and/or maximum transfer size of
READ/WRITE, which makes the HP-UX NFS client panic.
The correct behavior should be to 1) return I/O error
message when the preferred and/or maximum size has
a value of zero, and 2) allow normal operation when
the maximum transfer size has a non-zero value.
Resolution:
When an NFS server returns zero or MAX_LARGE_FILES
for a READ/WRITE operation's transfer size, the
HP-UX client now responds correctly instead of
panicking.
libnfs.a
JAGae38780
The functions pathconf(_PC_CHOWN_RESTRICTED) and
fpathconf (_PC_CHOWN_RESTRICTED) of NFS are
returning the wrong value if chown is not
restricted.
Resolution:
Created a kernel variable that allows toggling
between the existing behavior and the POSIX
conformance. This fix is disabled by default. To
enable the fix, set the NFS kernel global variable
pathconf_chown_restricted_posix to 1 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 'pathconf_chown_restricted_posix?W 0d1' |
adb -w -k /stand/vmunix /dev/kmem
To patch the in-memory kernel (does not survive a
reboot), use this command:
echo 'pathconf_chown_restricted_posix/W 0d1' |
adb -w -k /stand/vmunix /dev/kmem
A kernel regeneration will require these steps to
be done again.
libnfs.a mount
JAGae36449
This deadlock lock happens only in loopback mounts.
This happens while adding an entry into directory
name lookup cache (DNLC) for a file. The NFS server
attempts to hold a vnode lock that is already held.
This leads to a deadlock situation.
Resolution:
Avoid DNLC caching of removed NFS files in NFS
loopback mounts.
libnsl.1/a
JAGae52752
Mutex variables are not initialized which causes
the calling process to hang or terminate.
Resolution:
Functions for initializing the mutex variables
were added.
libnsl.1/a
JAGae46451
File descriptors are not closed when the server
detects an RPC_PROGVERSMISMATCH error.
Resolution:
Modified libnsl to close open file descriptors and
free transport handles when an RPC_PROGVERSMISMATCH
error is returned to the client.
libnsl.1/a
JAGae55409
XDR stream manipulation is not handled correctly
in some cases.
Resolution:
Modified the XDR code to correct the problem.
librpc.a
JAGae53431
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.
librpc.a
JAGae20331
An error condition returned while binding to a
reserved port is not handled in the code.
Resolution:
The error condition returned while binding to a
reserved port is now handled properly.
librpc.a
JAGae36003
The system reports "vmunix: bindresvport:
loop_twice port assigned 512" many times in
syslog.log, even though there are reserved ports
available.
Resolution:
Provide a kernel variable that by default disables
these messages. To re-enable these messages, the
kernel parameter 'loop_twice_msg' 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 'loop_twice_msg?W 0d1' |
adb -w /stand/vmunix /dev/kmem
To patch the in-memory kernel (does not survive a
reboot), use this command:
echo 'loop_twice_msg/W 0d1' |
adb -w /stand/vmunix /dev/kmem
A kernel regeneration will require these steps to
be done again.
librpc.a
JAGae46615
While binding a TCP connection, an uninitialized
variable causes the connection to incorrectly be
in the LISTEN state.
Resolution:
Initialized the variable to fix the state of the
connection.
librpc.a
JAGae48906
When copying 32-bit XDR long variables to 64-bit
kernel variables, the upper bits are left the way
they were before the copy.
Resolution:
Added code to make sure the upper 32 bits of 64-bit
variable data is now properly set.
nfsstat
JAGae39627
When "nfsstat -m" is executed from the client, a
statfs call is made across the wire to each server
listed in the /etc/mnttab file. The statfs call waits
for a response from the server, so if no response is
received, the client hangs.
Resolution:
With the HP-UX Device IDs product (DeviceIDs11i)
installed, the device id information is available in
the /etc/mnttab file on the client and the statfs
call is not made across the wire.
rpc.lockd
JAGae48827
A certain sequence of shared (read) locking and
partial unlocking on overlapping regions by multiple
processes over NFS causes the server's lockd to skip
unlocking a portion of the range in the kernel,
thereby losing track of these locks. These locks
accumulate over a period of time and consequently
exhaust all the available lock structures in the
kernel, at which time the kernel can no longer give
out any locks.
Resolution:
The code in lockd dealing with unlocking regions in
the kernel for overlapping shared (read) locks has
been rewritten. The server lockd now correctly
identifies non-overlapping regions and issues
unlock requests whenever necessary.
PHNE_28102:
automount
JAGae52325
Incorrect permissions for the log file.
Resolution:
Automount has been modified to set the proper
permissions for the default log file.
automount automountd
JAGae50502
Incorrect configuration of AutoFS.
Resolution:
The AutoFS code has been modified to address the
problem.
domainname domainname.1 ypinit ypserv ypxfrd
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.
libnsl.1/a
JAGae38632
Showmount dumps the core with SIGSEGV.
Resolution:
Code has been added to address the problem.
libnsl.1/a
JAGae38579
RPC does not function properly.
Resolution:
RPC has been modified to correct the problem.
libnsl.1/a
JAGae45826
When netdir_getbyname() calls ypmatch a hang can result
under certain circumstances.
Resolution:
The logic in ypmatch has been modified.
rpc.yppasswdd
JAGae40093
The rpc.yppasswdd process dumps the core.
Resolution:
rpc.yppasswdd has been modified to correct the problem.
PHNE_27217:
automountd libautofs.a
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. In concert with changes in
libc and File Systems, AutoFS will now make use
of the Device IDs and not query each server when
performing unmounts.
automountd
JAGae21158
The /var/adm/automount.log file is shipped incorrectly.
Resolution:
The /var/adm/automount.log file is now shipped properly.
automountd
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
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.
automountd libautofs.a
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.
automountd
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.
automountd
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.
automountd libautofs.a
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.
automountd
JAGae24031
AutoFS problem.
Resolution:
Fixed the AutoFS problem.
clear_locks clear_locks.1m
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.
libautofs.a
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.
libautofs.a
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.
libautofs.a
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.
libautofs.a
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.
libautofs.a
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:
Add 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.
libautofs.a
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.
libnfs.a
JAGad16564
Problem with privileged groups.
Resolution:
Fixed problem with privileged groups.
libnfs.a
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.
libnfs.a
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.
libnsl.1/a
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.
libnsl.1/a
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.
librpc.a
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.
librpc.a
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.
mountd.1m
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.
mountd.1m
JAGad01965
The '-e' and '-n' options for rpc.mountd described
in the man page are no longer supported.
Resolution:
Change the man page to remove references to options
'-e' and '-n'.
nfs.core
JAGae21159
The /var/spool/rexd directory is shipped incorrectly.
Resolution:
The /var/spool/rexd directory is now shipped properly.
mount umount
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.
nfsconfcol
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.
rpc.lockd rpc.statd
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.
rpc.lockd
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.
rpc.lockd
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.
rpc.lockd rpc.statd
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.
rpc.mountd
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:
hanged 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.
PHNE_27213:
{Site Specific Patch}
PHNE_26387:
libautofs.a
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_25626:
automount
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.
libautofs.a
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.
libnfs.a
JAGae06322
An NFS client does not return an error message when a
user's 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.
libnfs.a
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'.
libnsl.1/a
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.
libnsl.1/a
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.
libnss_nisplus.1
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.
librpc.a
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.
nsswitch.conf.4
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 is added into the nsswitch.conf man
page.
rpc.rusersd
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.
rpc.statd
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
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.
rpcgen
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.
ypserv
JAGad95797
An HP-UX server does not allow a blank entry in the map,
whereas 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.
PHNE_25484:
rpc.lockd
JAGae12206
rpc.lockd can core dump, with PHNE_24034 or
PHNE_24909 installed, if a local variable has not
been initialized.
Resolution:
Changed routine to initialize the local variable.
PHNE_24909:
libnfs.a
JAGad91730
Under certain conditions (memory pressure, file
system full), when a system is configured as an NFS
client and server using NFS-loopback mounts, a
deadlock condition can occur. NFS buffers remaining
in buffer cache that have active vnodes are re-used.
Resolution:
Dependency on PHKL_25525.
When writing dirty buffers, added "B_ASYNC" to ensure
buffer is eventually invalidated.
libnfs.a
JAGad74189
The mount option 'grpid' does not return the correct
'gid' value for the 'touch' command on HFS files sytems,
or for the 'mkdir' command on HFS and VxFS file systems.
Resolution:
Modified NFS client code to set the correct 'gid' value
when the file system is mounted with the 'grpid' mount
option.
libnsl.1/a
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.
libnsl.1/a
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 passwd from
the user and updates the NIS+ tables with the
username containing leading blanks.
Resolution:
Modified the function to include the leading blanks
in the search value.
libnss_nisplus.1
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.
libnss_nisplus.1
JAGad88698
Default system attributes are not assigned to
NIS+ users that log on 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.
yppasswdd.1m
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.
PHNE_24034:
automountd
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.
automountd
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.
automountd
JAGad30096
The AutoFS automountd caused the unmount command to fail
for mounted hfs and cdrom type file systems.
Resolution:
Added a new parameter for the hfs and cdrom unmount
commands.
libautofs.a
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.
libautofs.a
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.
libnfs.a
JAGad66201
File access performance is slow on systems with large
memory and buffer cache.
Resolution:
Restore the performance version of the NFS code to walk
through buffer cache. The problem described in
JAGad32551 is also fixed.
libnfs.a
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.
libnfs.a
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.
libnsl.1/a
JAGad76637
rpcbind and other RPC/XDR applications can be adversely
affected with SIGBUS.
Resolution:
Added code to address the problem.
librpc.a
JAGad66499
The system is running out of reserved ports.
Hundreds of processes are trying to gain access to
such ports (ie, perform a lock through lock manager).
Since the lock invocation (via a lockf or fcntl
system call) tries to use reserved ports 512 to 1023
to communicate with the local lock manager, these
ports are taken by the first lockers. If these are
all busy then subsequent lock invocations just loop
trying to get the next available reserved port. The
loop to get the next available reserved port is a
tight hard loop with a one-second delay between
activity to check whether any of the 512 reserved
ports are available. These lock invocations are the
ones actually starving the processes that first
obtained the reserved ports and they are sending
the messages to the message buffer. Thus, a virtual
deadlock occurs.
Resolution:
A backoff for the delay between successive attempts
at obtaining a reserved port is now provided. The
delay is progressive in that it starts at 1 second
and is doubled until it is 32 seconds. This allows
for those processes with a reserved port to run and
complete, and therefore give up their reserved port
to the processes waiting for one.
librpc.a
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.
nfs.client
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.
nis.client, ypbind, ypinit, ypinit.1m, ypserv.1m
JAGad70794
NIS clients do not have a mechanism to bind to a
particular NIS server.
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
rpc.lockd
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.
rpc.lockd
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.
rpc.statd
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.
rpcbind
JAGad34186 JAGad42706
Customer Symptoms:
rpcbind core dumps with SIGBUS or SIGSERV.
rpcbind core dumps with SIGBUG or SIGSEGV due to memory
corruption in the internal linked list of registered
programs. This list is abnormally terminated by memory
corruption and when the invalid node is accessed,
rpcbind can core. This has been noticed on several
occassions including NIS+ startup and random buffer
overflow under heavy load.
Resolution:
The core of memory corruption is in netbufdup().
Changed the malloc to valloc() to increase the required
buffer allocation.
PHNE_23833:
automount
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.
automount
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.
automountd
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.
exportfs
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.
fsirand.1m
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 fsirand command is only supported on HFS
file systems.
libnfs.a
JAGad48223
Server reads are occurring unnecessarily when a
client is only doing writes.
Resolution:
Removed the read operation that occurred before
the write operation.
libnfs.a
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.
libnfs.a
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.
libnfs.a
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.
libnsl.1/a
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.
libnsl.1/a
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 wrongly created file descriptors are never
closed.
Resolution:
In svc_vc_getargs(), comment out the call to
svc_args_done(). This will keep the file
descriptors until the RPC service routine is
totally complete.
libnss_nis.1
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.
libnss_nisplus.1
JAGad42007
When in trusted mode, the passwd change should
always create a fully qualified domain name even
if one was not passed into the command.
Resolution:
New code was added to libnss_nisplus.1 to fully
qualify domain names if they are passed non-fully
qualified.
nfsstat.1m
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.
rpc.lockd
JAGad49985 JAGad49986
rpc.lockd rejects NLM_GRANTED_MSG when it is
received out of order with NLM_LOCK_RES
(blocked). 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_LOCK_RES(blocked),
it is treated as if NLM_LOCK_RES(granted)
was received. When NLM_GRANTED_MSG is
received ahead of NLM_UNLOCK_RES it is
treated as if NLM_UNLOCK_RES was received.
rpc.lockd
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
same process are ignored even if it is for
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 lock. This enables lockd to
distinguish between requests from same process
for different files.
rpc.lockd
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.
rpc.lockd
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 messages
related to "control-c" interrupt processing.
Resolution:
&nb