Patch Name: PHKL_15915 Patch Description: s700 10.20 LVM/UFS/NDDB/flkmgr/VxFS/PCI/kload/mprot patch Creation Date: 98/07/10 Post Date: 98/07/17 Warning: 98/09/08 - This Critical Warning has been issued by HP. - Patch PHKL_15619 introduced defects with Loopback File Systems (LOFS) that can cause a variety of problems. These defects are also present in PHKL_15915. The three reported symptoms of these problems on LOFS file systems are: - a system panic in locallookuppn() when the ".." path component is referenced in commands such as ls(1) and rm(1). - the mount(1M) command failing with "device busy". - the rmdir(1M) command failing with "Cannot remove mountable directory". - The problem only affects Loopback File Systems, other file system types are not affected. To determine if Loopback File Systems are being used, execute the command "mount -v" and search for the string "lofs". - A recent modification to automountd(1M) in the NFS patch PHNE_15541 changes the behavior for autofs to use Loopback File Systems instead of loopback NFS for all mounted local file systems. Therefore, users of AutoFS may experience these problems once PHNE_15541 is installed. - While the problems were introduced in PHKL_15619, they are also present in patches superseding PHKL_15619. The problem also exists in PHKL_15742, PHKL_15766, PHKL_15787, PHKL_15915, PHKL_15942, and PHKL_15958. - It is recommended that PHKL_15618, PHKL_15742, PHKL_15766, PHKL_15787, PHKL_15915, PHKL_15942, and PHKL_15958 be removed from all systems utilizing Loopback File Systems. - Until a replacement patch is available, the previously available patches PHKL_15199 and PHKL_7967 will be re-released. Hardware Platforms - OS Releases: s700: 10.20 Products: N/A Filesets: AdvJournalFS.VXFS-ADV-KRN JournalFS.VXFS-BASE-KRN JournalFS.VXFS-PRG LVM.LVM-KRN OS-Core.CORE-KRN OS-Core.KERN-RUN ProgSupport.C-INC Automatic Reboot?: Yes Status: General Superseded With Warnings Critical: No (superseded patches were critical) PHKL_15787: PANIC HANG PHKL_15766: HANG PHKL_15742: PANIC CORRUPTION PHKL_15619: HANG CORRUPTION PHKL_15495: PANIC PHKL_15456: PANIC HANG PHKL_15321: ABORT PHKL_15244: PANIC HANG PHKL_15199: HANG PHKL_15085: PANIC PHKL_14953: HANG I/O requests hang in LVM wait queue when the FC cord link is broken. PHKL_14856: PANIC This defect was only observed under extremely heavy loaded system with infrequency. PHKL_14803: HANG PHKL_14613: HANG PHKL_14568: PANIC Panic while trying to perform an lvmerge operation. PHKL_14490: PANIC HANG PHKL_14321: PANIC PHKL_14225: ABORT PHKL_14126: PANIC CORRUPTION PHKL_14049: PANIC PHKL_13986: PANIC PHKL_13911: PANIC PHKL_13868: OTHER Port I/O will not work correctly, machine may panic. PHKL_13768: OTHER Prevents MC/Service Guard TOC on PA8000 systems. PHKL_13744: PANIC PHKL_13514: PANIC PHKL_13452: PANIC PHKL_13305: HANG PHKL_13260: HANG This patch fixes a defect which could essentially hang the systems with VISUALIZE-FX graphics hardware. The patch in addition to this fixes a performance problem seen on systems that use applications with large number of shared memory segments. The systems spend too much time servicing protection id faults. PHKL_13247: ABORT PANIC PHKL_13206: CORRUPTION A clean file on VxFS can be marked bad. PHKL_13155: HANG PHKL_13014: PANIC PHKL_12963: PANIC PHKL_12901: PANIC PHKL_12662: HANG PHKL_12397: PANIC HANG PHKL_12306: HANG PHKL_12110: PANIC HANG PHKL_12100: CORRUPTION Kernel portion of fix for unrepairable VxFS filesystem where fsck produces the error message "no valid ILIST in fileset 999". PHKL_12088: OTHER Patch REQUIRED for the OmniStorage 2.20 product. PHKL_11860: PANIC PHKL_11766: PANIC PHKL_11733: OTHER Unmountable VxFS filesystem. PHKL_11730: PANIC PHKL_11696: PANIC PHKL_11607: PANIC PHKL_11561: CORRUPTION This patch when used with the appropriate SG/DLM version will avoid any potential windows for data corruption during reconfiguration in a HA cluster environment using SG or DLM. PHKL_11545: PANIC PHKL_11519: ABORT PHKL_11408: CORRUPTION PHKL_11406: CORRUPTION PHKL_11358: PANIC PHKL_11351: PANIC PHKL_11332: PANIC PHKL_11321: PANIC PHKL_11316: HANG The system hangs when a large number of users try to log in or out of the system simultaneously. PHKL_11238: PANIC So far, the panic only appears on MP systems running the latest Informix release. PHKL_11164: PANIC PHKL_11085: CORRUPTION From a customer perspective, EMC Symmetrix disks can appear to lose or corrupt data when rare spurious errors are reported. The data is actually able to be recovered on the disk, and this patch allows LVM to ignore the fact that the block was once "bad" and obtain the good data from the repaired block. PHKL_11055: HANG PHKL_11039: CORRUPTION This patch fixes data corruption for applications that create large files which keep changing their size dynamically. PHKL_11013: OTHER This problem leaves the filesystem disabled and unusable, and requires a system reboot to regain access to it. PHKL_11002: OTHER T600 will not BOOT. PHKL_10953: HANG PHKL_10932: OTHER HPMC on Emerald-class systems at boot time. PHKL_10930: HANG PHKL_10769: PANIC PHKL_10757: PANIC PHKL_10675: PANIC CORRUPTION PHKL_10643: PANIC PHKL_10554: PANIC The HPMC/panic that is fixed by this patch has been observed only in rare instances on pre-release hardware. However, the potential exists for similar problems in the field only if PHKL_9151 has been applied. This fix should also provide increased performance for PA-8000 systems. PHKL_10452: PANIC PHKL_10288: PANIC PHKL_10257: PANIC PHKL_10234: PANIC PHKL_10199: CORRUPTION PHKL_9931: HANG PHKL_9909: HANG PHKL_9569: HANG PHKL_9517: CORRUPTION PHKL_9372: PANIC PHKL_9370: OTHER Unmountable VxFS filesystem. PHKL_9365: CORRUPTION PHKL_9361: PANIC PHKL_9075: PANIC PHKL_8953: HANG PHKL_8908: PANIC CORRUPTION Panic should occur only if root VG is LVM on built-in SCSI in 710, 720, 715/50, 725/50. Corruption should only occur on QUANTUM LPS525S on built-in SCSI in 710, 720, 715/50, 725/50. PHKL_8683: PANIC PHKL_8532: CORRUPTION PHKL_8331: CORRUPTION PHKL_8294: HANG PHKL_8203: HANG PHKL_8187: HANG PHKL_8084: ABORT PHKL_7987: HANG PHKL_7899: PANIC HANG OTHER The KI instrumentation fix does not fall into any of specified symptoms; the root setuid fix does not either. PHKL_7870: PANIC PHKL_7776: OTHER Unmountable VxFS filesystem. Path Name: /hp-ux_patches/s700/10.X/PHKL_15915 Symptoms: PHKL_15915: An application receives SIGBUS during a memmove() operation on a properly aligned and mmap'd page. PHKL_15787: SR: 4701396200 DTS:JAGaa12818 other lab DTS: DSDe441605 and DSDe442781 LVM PVLink switches with failed FibreChannel hubs can be very slow. This patch is essential for FibreChannel hubs configurations. This patch reintroduces the FibreChannel hub PVLink switch improvements made in PHKL_15200. The prior version caused unexpected side effects for Galaxy and Nike arrays: potential for panic when used with Service Guard clusters and occasional link bounce (ping-pong) on transient link failures and link recovery. SR: 4701394635 DTS: JAGaa12375 HFS filesystems that have had large files unlinked and then new files created may see spikes in I/O for the writes of these later files. PHKL_15766: SR: 5003414540 Enabling the kernel kload driver will cause Enhanced DFS 1.5.1(EFS) to fail since EFS no longer needs it. SR: 4701394163 pfault() not able to update protection ID properly causes hang; this could have happened by accident while using "-Z" flag on a "cc" command for the following code: addr = NULL; mprotect(addr, 4096, PROT_READ); PHKL_15742: 1. SR: 1653236869 DTS: JAGaa01996 mounting a VxFS filesystem over NFS using a small read buffer size causes failures when reading directories; as a result, directory entries can not be seen. 2. SR: 4701393074 DTS: JAGaa10827 Data page fault panic from vx_spin_lock() 3. SR: 5003295238 DTS: JAGaa09110 ftruncate with memory mapped files on JFS 4. SR: 4701393819 DTS: JAGaa11061 System panics with a 'Data Page Fault' in ogetblk() after PHKL_15619 is installed. PHKL_15619: SR: 4701393819 CR: JAGaa11061 An 'nfsd' process may hang on the system. If a system dump is taken, the 'nfsd' process will be hanging in the vx_vn_bread() function. SR: 4701349175 DTS: DSDe435102 A System "HANG" occurs whenever a large number of users log in/out at the same time. SR: 4701393884 CR: JAGaa08709 A directory mounted via the loop-back file system (lofs) can be removed. Thus, making the mount inaccessible SR: 5003413278 DTS: DSDe442455 If mounting a vxfs file system fails, processes accessing vxfs file systems will hang. SR: 5003421628 DTS: JAGaa10135 System with large buffer cache (>1G) and heavy I/O hangs intermittently. The TOC dump shows processes are looping in rmprobe() and bcfeeding_frenzy(). SR: 1653259408 DTS: DSDe441605 The fibre-channel hubs performance improvement fix (for DSDe441605) has unexpected side effects for customers with active-passive (Nike and Galaxy) arrays. These changes may cause these arrays to begin a ping-pong between primary and alternate links when a link is restored or when a transient error on the primary link occurs. SR: 4701393058 CR: JAGaa10826 After a VxFS file system is full, system panics with data page fault when accessing data buffers. PHKL_7967: fuser does not report processes in LOCAL FILESYSTEMS lofs. PHKL_15492: The command: lvlnboot -d <lvol> <volgrp> returns with the message: Unable to configure dump logical volume. Dump logical volume file beyond the IODC max address whenever any part of the given <lvol> lies beyond 2G bytes from the start of a PCI-SCSI disk. PHKL_15495: Panic occurs during a hazard stress test exercising VxFS (JFS) on a HA cluster. PHKL_15504: VxFS can not update an extended inode for an existing file when the filesystem is completely full. Large file support doesn't allow DMAPI invisible writes. PHKL_15456: SR 5003418244, DTS JAGaa07539: System experiences intermittent hangs; in some cases the system is able to resume processing without intervention in about 20 minutes, but other times it will lock up and need to be TOC'ed. The event trace in the dump shows: crash event was a TOC timespecfix+0x0 timespecadd+0x30 ktimer_expire+0x24c invoke_callouts+0x160 softclock+0x38 sw_service+0x154 mp_ext_interrupt+0x2a0 At times the system will panic with Spinlock deadlock. SR 4701391730, DTS DSDe438419: processes may hang doing mmap(2) due to a lock-order violation; the offending process' stack trace will look something like this: _swtch+0x138 _mp_b_sema_sleep+0xe0 vnode_vas_lock+0x78 freereg+0x194 smmap_common+0x5d0 smmap+0x38 syscall+0x1a4 $syscallrtn+0x0 SR 1653177089, DTS DSDe429996: 10.xx read/write via block devices is slower than 9.xx. PHKL_15321: Fsadm returns the following error during reorganization: vxfs fsadm: Ioctl failure: Invalid argument PHKL_15244: - DTS: DSDe442455 SR: 5003413278 System panics when multiple processes are trying to mount a snapshot filesystem using the same LV. - DTS: JAGaa02119 SR: 5003407601 Reboot process hangs on a MP system. PHKL_15199: SR:1653259408 DTS: DSDe442757 other lab DTS: DSDe441605 and DSDe442781 LVM PVLink switches with failed FibreChannel hubs can be very slow. LVM PVsparing does not always start using a spare when a device fails. Hang occurs with heavy I/O stress and patch PHKL_14804 installed. This patch is essential for the use of FibreChannel hubs. PHKL_15145: Flush data to disk before splitting mirrored disks. PHKL_15085: The system will panic if a graphics process does graphics DMA on VISUALIZE-FX hardware, and then execs another program without forking first. PHKL_15057: The current first-fit allocation policy for allocating virtual addresses for shared objects (shared memory, memory mapped files, etc.) does not meet certain customers' requirements. It is found to cause fragmentation of the shared virtual space, preventing certain applications from being run. PHKL_14955: This patch allows the NDDB kernel debugger to debug 10.20 kernels running on PA-RISC 2.0 CPUs. Without this patch, NDDB (and landdb/rsddb) may report incorrect status such as "Breakpoint at 0x0". The landdb/rsddb kernel debuggers will no longer function after the patch is applied; the NDDB kernel debugger must be used instead. Other functionality provided in this patch includes: o Support the Core I/O 10Base-T LAN card for NDDB communications. o Support configurations where the console is connected to the second RS-232 port. o Support platforms using RS-232 communications on the GSC-to-PCI bus bridge. o Detach the target kernel using the "free" command; reboot the target using the "kill" or "quit" commands. o NDDB "ps", "ktps", and "cpus" commands show info on processes, "kernel threads", and CPUs. o Various bug fixes. PHKL_14953: I/O requests passing through the LVM layer hang when the pv-link is broken (FC cable is pulled off). The I/O requests are hung even if the pv-link is restored. PHKL_14917: Excessive SCSI timeouts on MO drives. PHKL_14856: Machine under a heavy load can panic with an instruction page fault. PHKL_14803: SR: 5003407601 DTS: JAGaa02119 System hangs during reboot. SR: 5003407619 DTS: JAGaa01516 Under heavy I/O, after the buffer cache allocation has reached its system defined maximum, the system eventually hangs when all I/O processes sleep on waiting for buffer cache. PHKL_14740: When a Service Guard cluster experiences a failure on one node, the VGs may fail to activate on the surviving node when the shared disks are using FibreChannel. PHKL_14685: When the customer installs the flock manager driver, the library libflkmgr.a does not exist. This is seen only in those environments running flock manager. PHKL_14613: System hangs under extreme load on UFS filesystem while a LV creation is in progress. PHKL_14568: This patch fixes 3 defects: - SR:1653254987 DTS:JAGaa01797 MP systems using LVM mirroring could experience panics (data fage fault) while doing an lvmerge() operation. - SR:4701379347 DTS:DSDe441470 Add flock manager driver functionality - SR:1653216952 DTS:DSDe437110 sleep(3C) behaves incorrectly for values larger than (2^32-1)/200 = 21474836 seconds. The man page documents legal values up to 2^32-1 seconds + 10^9-1 nanoseconds. PHKL_14490: This patch fixes three defects: - SR: 4701382564, DTS: DSDe441726 If the kernel free sysmap space falls to 0, the system panics without prior warning that indicates this condition. - SR: 1653251934 DTS: JAGaa01592 The system hangs under heavy I/O involving VxFS filesystems. When the buffer cache virtual space is heavily fragmented and a readhead is being done, system hangs. - SR: 1653252544 DTS: DSDe441877 Some user applications will hang with high system load. These processes cannot be killed and the system needs to be rebooted to clear these processes. PHKL_14323: Command lvlnboot may fail with the following error: "No Boot Logical Volume Configured". PHKL_14321: This patch fixes two defects : - SR: 1653235176, DTS: JAGaa01482 This defect causes a panic in an MP system when two processes are doing mmap/munmap on portions of the same file using a sliding window. The user will see the system panic with "panic: rmfree: overlap" message. The stack trace will be as shown below: panic+0x10 rmfree+0x268 quaddealloc34+0x30 hdl_detach+0x108 detachreg+0x3c do_munmap+0x190 do_munmap+0x84 syscall+0x1a4 A different panic could occur due to an unrelated race condition when mmap/munmap is called. This second panic is a result of data page fault. The stack trace in this case will be as shown below: panic+0x3C report_trap_or_int_and_panic+0x8C trap+0xC18 $RDB_trap_patch+0x20 smmap+0x8F0 syscall+0x1A4 - SR: 4701383612, DTS: DSDe441827 The defect's symptoms are that writes to a VME device will succeed on 10.20 but reads will fail with EFAULT. PHKL_14225: Application experiences random illegal instruction trap when executing cache-flushing code. PHKL_14183: This patch is part of the 10.20 ACE 2 bundle which adds networking enhancements to 10.20. New networking features supported in ACE 2 include NFS Version 3.0, AutoFS, and CacheFS. PHKL_14126: This patch fixes two defects : - SR: 4701381608, DTS: DSDe441567 Patch PHKL_13684 introduced a defect that can break applications which use the vnode layer procedure vn_open(). This can result in a panic due to an invalid address or possibly on data corruption. Currently we are only aware of conflicts with Netware. - SR: 1653223404, DTS: DSDe438306 vgchange display couldn't query one physical volume The specified path does not correspond to PV attached to this VG. After issue vgchange with -a y -q n options, system trap panic. PHKL_14049: This patch fixes three problems: a) SR: 1653247486, DTS: JAGaa01357 For a mirrored LVM root disk containing 2**n extents, if the system is booted in maintenance mode (hpux -lm), it will panic with trap 15 data page fault on the next reboot. b) SR: 1653239137, DTS: JAGaa01378 For a root VG with two disks which are mirror partners, if one disk becomes inaccessible, the system panics on bootup with trap 15 data page fault. c) SR: 1653248690, DTS: JAGaa01406 System panics in lv_end() with isr.ior=0.58 data page fault when a bad block is detected on disk. The console message shows: lv_readvgdats: Could not read VGDA 1 header & trailer from disk H/W path x/x.x.0 (error = 5) lv_readvgdats: Could not read VGDA 2 header & trailer from disk H/W path x/x.x.0 (error = 5) PHKL_14012: This is an enhancement to add the flock manager driver hooks to the kernel. This patch is only needed if you are planning to use the flock manager driver. PHKL_14009: pstat_getlv() returns information about first VG only. PHKL_13986: Allows attachment of external HP-PB card cage to HP-HSC to HP-PB converter. PHKL_13911: In a mixed UFS/VxFS environment, the system panics with a dirty invalid buffer which was associated with an HFS filesystem that has since been unmounted. The typical stack trace of the panic looks like the following: panic+0x14 brelse+0x1ec getnewbuf+0x6b0 ogetblk+0x104 getblk1+0x258 vx_getblk+0x5c PHKL_13874: This patch fixes two problems: a) When running fsadm on a file which was created under VxFS version 2, sometimes "Invalid Argument" would be reported. b) When running fsadm on a file which was created under VxFS version 2, sometimes "No such device or address" would be reported. PHKL_13868: PCI port I/O does not work properly, and machine may panic. PHKL_13795: This patch is part of the 10.20 ACE 2 bundle which adds networking enhancements to 10.20. New networking features supported in ACE 2 include NFS Version 3.0, AutoFs, and CacheFS. PHKL_13768: Temporary system hang on PA8000 systems, possibly resulting in TOC to preserve system integrity (if running MC/Service Guard). When analysing the system crash dump, a processor would be executing in the kernel routine alloc_large_page(). PHKL_13761: mprotect() system call causes high system time resulting in poor system performance. PHKL_13744: Errors in opening a tape device on the HSC bus may cause a data page fault panic. The panic occurs at st_head_pos+0x5c. PHKL_13713: When using chown for certain user IDs, the command would fail. PHKL_13684: In a multi-vendor client-server environment (HP client or HP server), a user-supplied umask is ignored during file creation, even if no default ACL is present. This appears to violate POSIX ACL draft 12. PHKL_13680: 10.xx read/write via block special device file is slower than 9.xx. PHKL_13514: With certain hardware configurations, especially on the J2240, it is possible for the system to panic (at bootup) with the message: panic: Could not assign interrupt handler PHKL_13508: On a heavily fragmented VxFS filesystem, bdf and df show only small amounts of available space. df furthermore shows a larger percentage number for minfree although this concept is unknown to VxFS. All this is ok on a VxFS Version 2 filesystem, but on a Version 3 filesystem extents smaller than 8k are available for files. PHKL_13452: The user will see a data page fault PANIC with vx_attr_alloc(), vx_attr_indadd(), or vx_attr_iget() at the top of the stack. A sample stack trace might look like: panic+0x10 report_trap_or_int_and_panic+0xe8 trap+0x1054 $RDB_trap_patch+0x20 vx_attr_iget+0x90 vx_iremove_attr+0x358 vx_attr_uset+0x374 vx_do_ioctl+0x73c vx_ioctl+0x38 vno_ioctl+0x98 ioctl+0x444 syscall+0x1a4 PHKL_13305: This problem manifests as a hang during a reboot operation. The reboot can be initiated with a shutdown command. The problem will only appear on a multi-processor machine. I/O in progress during the reboot either from disk or from the network can cause the primary reboot processor to wait for an indefinite amount of time. PHKL_13260: This patch fixes three problems: a) SR: 1653237842, DTS: JAGaa01160 Slow performance with high system time on PA2.0 and PA1.1 systems. The system slows down under user applications with lots of shared memory segments (like Informix database which uses lots of shared memory segments). b) SR: 1653237842, DTS: JAGaa01160 Illegal sharing of protection ids lead to silent data corruption (SHMEM_MAGIC applications) c) SR: 4701373969, DTS: DSDe440766 This defect causes VISUALIZE-FX graphics hardware to lock up. If the VISUALIZE-FX device is the console for the machine, this will render the machine unusable unless it can be reached over a network (in which case killing and restarting the X server should fix the problem). CTRL-SHIFT-RESET from the console keyboard will not terminate the X server in this case. PHKL_13247: The shared PV LINKS will not switch when needed. The activation of the VG using vgchange -a s may fail on one of the nodes if the command is being run simultaneously on all the nodes. HPMC or bad pointer panic in FibreChannel driver on ServiceGuard cluster failover. Failure to activate VG (any I/O connect type) on ServiceGuard cluster failover. PHKL_13237: If serialize() command is executed as: 'serialize ls', the command fails with the error number set to EINVAL. (User id must be 0, or user belong to a group that has privilege to execute the serialize command). The serialize command should have serialized the target process, in this case the command 'ls', and should have listed the content of the current directory. PHKL_13206: When getdirentries() is incorrectly called with a regular file on VxFS filesystem, following message will be reported and the clean file can be marked bad. "vxfs: mesg 008: vx_direrr - <FS> file system inode X block Y error 6" or "vxfs: mesg 017: vx_dirbread - <FS> file system inode X marked bad" or "vxfs: mesg 016: vx_ilisterr - <FS> file system error reading inode X" PHKL_13155: Processes hang intermittently due to process deactivation and reactivation. PHKL_13014: - 9000/725/B panic on boot. - Tape driver rejects odd-length write requests. - "Unhandled pending interrupt" declaration and SCSI bus reset. PHKL_12997: When dump is configured past 2GB on a device connected to a HSC F/W SCSI interface card, the device fails to configure: WARNING: Dump space on device <device ID> cannot be configured past 2097151 bytes. Device <device ID> skipped. PHKL_12963: In the past, a process running in a group could consume more than just its own groups entitlement if excess CPU cycles were available. This change allows this to optionally be disallowed / capped within PRM. Also, there was a problem when PRM, thread stealing and processor affinity were used/occurred on a system at the same time. In this case, it was possible for a processor to not find a process, which could cause a panic. PHKL_12901: A kernel stack overflow panic occurs when the stack is valid and all three pages allocated for kernel stack are consumed. The defect is seen when a combination of NFS,LVM,VxFS related modules are called. PHKL_12669: This patch contains problems in three areas: 1. There are no warning to user when bad block alternates were allocated inside the user data area. 2. There is no way to use lv timeout feature when the async driver minor number is not 0. 3. Add a new lvol flag in lv_lvsubr.c to support a command patch. PHKL_12662: UFS filesystem may hang on system reboot. PHKL_12660: EINVAL errors on FibreChannel raw disk reads and writes. PHKL_12633: SHMEM_MAGIC executables suffer from unacceptable performance greatly impairing its usefulness. PHKL_12601: VxFS systems do not allow a process to ftruncate() a file it has opened, write-locked and read from. When the program fails, errno is set to 11 which means resource is temporarily unavailable. PHKL_12409: Applications relying on alarm() returning a number greater than zero will fail if there was time remaining on the cancelled alarm and were trying to re-schedule the original alarm. alarm() returns "zero" when cancelling a previous alarm() with an alarm pending. PHKL_12397: This patch fixes two defects : - System panic (data page fault) when debugging processes over an interruptable NFS mount point. - After call to pstat_getmsg(), all accesses to the message queue hang. PHKL_12378: MP systems running applications that require many files with filenames longer than 14 characters to be accessed will experience severe CPU contention. Netscape Mail server v3.0 with Netscape mail server Benchmark puts this in evidence by reporting a very low message receive/deliver rate. Systems with large buffer cache will have spinlock contention problem. PHKL_12306: Glance reports 0 MB/s on GSC disks. EINVAL on read/write to FC EMC Symmetrix. System hang. Device hang. PHKL_12217: The tar command can go into a tight loop, backing up the same file over and over on a NFS-mounted filesystem. So far this problem has been seen only on NFS filesystems exported from SGI IRIX 6.2 systems. PHKL_12110: System hangs on UP systems or spinlock deadlocks on MP systems, when using nanosleep system call. If using signals which were to be ignored when in nanosleep() we were awakened even though we should not have been. This patch is especially critical as soon as newer libc patches are installed on the system. The first releases of libc to be critical are PHCO_10384 for 10.10, PHCO_11004 for 10.20 and PHCO_10652 for 10.01. PHKL_12100: command patch PHCO_12922 The following problems are fixed: 1) Under certain circumstances after a hard failure, VxFs fsck log replay would fail requiring a full fsck. 2) On large filesystems containing a very large number of files, full fsck would run extremely slowly. PHKL_12088: The DMAPI functionality delivered with HP-UX 10.20 OnlineJFS delivers a Kernel-space library, but does not include a User-level library. OmniStorage 2.20 requires a User-space DMAPI library to function successfully. PHKL_12073: With sa_flags (in sigaction structure) set to SA_SIGINFO, after a child process abnormally terminates without a core file being generated, the si_code number of the siginfo_t structure is supposed to contain CLD_KILLED. This failed to happen when the child process abnormally terminated with a SIGPOLL signal. PHKL_12042: Resource-intensive processes (such as an Informix oninit) either perform poorly over time (as timeshare) or monopolize the system (as realtime). Also, MP systems show processes frequently being moved from one CPU to another. PHKL_11902: pid information is missing from a diagnostic message which tries to explain to a user that their process does not have the correct locking priveleges required for using large text pages. PHKL_11860: The PHKL_9371 installed system panics during reboot, if reboot command is used. This patch fixes this problem. PHKL_11766: 1. vgextend command will complain "too many links" if user wants to add an addition PV to a VG, and the total PV and their links add up to total number of maximum PV allowed in a VG. 2. trap panic in lv_resyncpv from LVM. Lots of "pvnum is POWERFAILED" messages. PHKL_11733: After a hard failure (panic/hang/TOC), a VxFS filesystem may not mount and will return the following error message: vxfs mount: %s is not a vxfs filesystem. This could even happen with patches PHKL_9371 and PHCO_11223 installed. A full fsck does not clean the filesystem; a newfs/mkfs is the only solution. PHKL_11730: Data page fault in bwrite. PHKL_11696: panic: hdl_alloc_spaceid: spacemap exhausted PHKL_11637: CDROM drive remains locked when system is rebooted. PHKL_11632: SCSI bus resets when probing bus with DLT library robotic arm via ioscan. PHKL_11614: Accounting does not work for the clients in a diskless cluster. The accounting file does not get updated for users other than ROOT when accounting is ON, if the pacct file is on an NFS filesystem. PHKL_11607: System may panic in vx_itimes() when mounting a VxFS file system after a boot from a hard failure. PHKL_11561: A customer might find corrupt data on disk after a Service Guard or Distributed Lock Manager fail-over. This defect is specific to the HA cluster environments. PHKL_11545: - Fixes an intermittent panic when opening a tape device on the HSC bus. - Improves performance for wide SCSI tape devices connected via the HSC bus. - Allows DLT4000 devices to perform odd-sized writes. PHKL_11519: On a NFS server with a Vxfs filesystem exported, the file /var/adm/nettl.LOG0x grows dramatically with the recording of "read failed with errno 22" (EINVAL). This problem is addressed by kernel patch PHKL_11322 among other problems. However, after the patch is installed, some NFS clients experience command coredump on the NFS-mounted VxFS disk. PHKL_11471: Quota command shows poor performance on a busy system under VxFS. PHKL_11408: Corruption of memory pages on systems with PA-RISC 2.0 CPU. Problem should happen rarely and only under extreme memory stress. PHKL_11406: When using large environments greater than 20 kbytes user applications dump core sometimes, or get bad data. PHKL_11358: A panic would result when trying to rename a vnode which was a UFS mount point under a VxFS directory. The reverse did not cause a panic but was not being handled properly either. PHKL_11351: (DSDe438658) panic: Data Page Fault with FDDI. T600 will HPMC when HSC (GSC) interface cards using a GSCtoPCI interface chip are installed. (4701362111) Any MP system is likely to panic when multiple HSC (GSC) interface cards using GSCtoPCI interface chips are installed. (DSDe437012) Performance enhancement in PCI services. PHKL_11339: A process launched from shell sees (getrlimit) limits set in the shell via ulimit -t but ignores them. When a process forks, the child sees the limits set by the parent via setrlimit but ignores them. PHKL_11332: (4701356766/ DSDe437007; 4701353888/ DSDe436271) T600 systems panics under heavy I/O load stress testing during lab tests. PHKL_11321: This patch fixes two VxFS performance problems and one defect: 1) Upgrading from 10.10 to 10.20, customer experienced approximately 25% performance degradation in read operation under VxFS. 2) Loading a program for a second and subsequent time takes much longer if the program is using shared libraries on VxFS. 3) Occasional panic occurs when running an executable which attempts to pagein through vnode level, producing a stack: trap+0xf84 0.0xe21c4 0x6954.0x7ffe75b8 ... $RDB_trap_patch+0x20 0.0x22608 0x6954.0x7ffe75b8 ... lbcopy_fp_method1+0x58 0.0x222b98 0x6954.0x7ffe7108 ... privlbcopy+0x1c 0.0x222fc4 0x6954.0x7ffe70c8 ... uiomove+0x4f0 0.0xfabe8 0x6954.0x7ffe7008 ... vx_read1+0x26c 0.0xb9744 0x6954.0x7ffe6ec8 ... vx_rdwr+0x16c 0.0xc5164 0x6954.0x7ffe6e08 ... vn_rdwr+0x8c 0.0x107b04 0x6954.0x7ffe6d48 ... mfs_hpux_pagein+0x448 0.0x1cbb5c 0x6954.0x7ffe6c88 ... virtual_fault+0x9a0 0.0xf1fc8 0x6954.0x7ffe6b48 ... vfault+0x104 0.0xf281c 0x6954.0x7ffe6ac8 ... trap+0x129c and the message: trap type 15, pcsq.pcoq = 0.222b98, isr.ior = 18e.4179000 savestate ptr = 0x7ffe7108, savestate return ptr = 0x222fc4 9245XB HP-UX (B.10.20) #1: Sun Jun 9 06:31:19 PDT 1996 panic: (display==0xbd00, flags==0x0) Data page fault This is mostly seen on PureAtria's Clearcase product which sets the UIOSEG_PAGEIN flag for vn_rdwr() calls. PHKL_11316: A system hang occurs whenever a large number of users login or logout at the same time. The password file has large number of entries and the system can have around 1000 concurrent connections. The problem occurs when many processes try to access the same file concurrently, the inode locking routines start dealing with the contention very inefficiently. PHKL_11247: On a VxFS filesystem with quotas enabled, users who do not have quotas set receive "write: Disk quota exceeded" error message when creating files on this filesystem. PHKL_11244: When accessing an address returned by mmap(), the application gets a SIGBUS error and core is dumped. PHKL_11238: Panic on S800 MP systems using 10.01+ with latest Informix PHKL_11164: The system message buffer would show many "sysmap: rmap ovflo, lost [...]". Eventually, the system would panic with "kalloc: out of kernel virtual space." This problem would only be seen on PA8000 systems. PHKL_11085: On very rare occasions EMC Symmetrix disk drives will report a disk error which causes LVM to mark the block as bad in its bad block directory. The Symmetrix drive can be "repaired" online by EMC support, but the entry in the LVM bad block directory will prevent any further I/O to the affected block. This patch enables a new relocation policy which will prevent entries from being added to the bad block directory. In order to make use of this new relocation policy, a commands patch, PHCO_10826 must also be installed. Also, algorithms within LVM that deal with PVLinks had built in the assumption that Nike serial numbers were unique. This turned out to not be the case. The only time that the serial numbers need to be unique is in OPS clusters. This patch removes this restriction for all non-OPS cluster environments. PHKL_11055: Large memory systems could hang while trying to allocate kernel memory. A TOC crash dump would show a processor executing in alloc_large_page() while other processors would be spinning waiting for the pfdat_lock spinlock. This problem would only be seen on PA8000 systems. PHKL_11039: VxFS filesystem corruption when running applications using file truncation on large files. The system message buffer will show: "vxfs: mesg 017: vx_trunc - /mnt file system inode \ 123 marked bad. vxfs: mesg 016: vx_ilisterr - /mnt file system error \ reading inode 123". It also fixes a malloc panic which was found while fixing this defect. PHKL_11013: The vxupgrade command, used to convert a VxFS version 2 file system to a version 3, can give an I/O error on execution. This causes the filesystem to be marked as unavailable, and a full fsck to be run. PHKL_11006: timer_settime(2) does not set 10ms timer interval properly. The smallest interval can be set is 20ms. PHKL_11002: (4701353888/ DSDe436271) T600 systems will not boot without this patch on 10.20 HP-UX. PHKL_10966: When running fsadm to reorganize extents (de-fragment) the command fails with error: exclusion zone for bno = 323584, len = 2048 failed This error message does not occur at all times. It has been observed when running fsadm on filesystems which contain directories with many small files. PHKL_10953: Severe system hang: the crash dump (TOC) would show many threads waiting for the filesystem alpha semaphore. The kernel stack trace of the thread owning filesys_sema would show bc_yield() calling swtch(). PHKL_10932: (4701353078/DSDe436182) Emerald-class (890, T5x0, T600) systems will experience an HPMC at boot when IODC for memory controllers is being accessed. Note: if you are not experiencing this problem now, then your memory controllers are not subject to this problem. (This problem is NOT intermittant.) PHKL_10930: The system hangs when trying to dump core, as the result of a system panic or TOC. PHKL_10821: Although users can now exec() programs with up to 2048000 bytes of argument and env strings, sysconfig() _SC_ARG_MAX continues to return 20480 bytes as the maximum length of all arguments and env strings. PHKL_10800: Audit records contain relative path names which the user has no idea where they are anchored. This fix prepends the cwd to the relative path name yielding a complete absolute path. PHKL_10769: On C200 and newer workstations with PCI there is a possible HPMC that can occur due to a hardware bug in certain revisions of the PCI bus ASIC. This patch prevents the HPMC from happening. PHKL_10757: Workstation Additional Core Enhancements for HP-UX 10.20 (July 1997). This patch provides additional enhancements to support new HP workstations. The primary change is the addition of a new signal (SIGGFAULT) and virtual memory subsystem changes to support virtual device locking for new VISUALIZE-FX graphics hardware. It also contains two bug fixes: one for the MP PDIR bug (could panic the system) and the other for the pstat_cmd() panic. PHKL_10756: This patch contains enhancements to support the GSCtoPCI PCI Bus Bridge on HP workstations. PHKL_10755: Performance enhancements for PCI SCSI (Ultra-SCSI). PHKL_10689: HP-UX didn't log any error when a user process: 1. encounters a swap space shortage 2. exceeds a system resource limitation Processes were terminated but the errors were not recorded on any of the system log files. PHKL_10675: (1) System may panic with "panic: sync not stale" while running lvmerge (merging LVM mirrors). For the panic to occur, an I/O timeout must occur during the lvmerge operation which results in a resync getting scheduled. (2) Potential data corruption if user I/O requests encounter errors to the same extents which are being reimaged by lvmerge. (3) Various panics during VG activation (vgchange -a). A bit is cleared in a kernel structure which LVM has already freed. If another kernel subsystem has been allocated the freed memory before the bit is cleared, panics or other strange behaviors may occur. This particular defect was introduced by PHKL_9000. PHKL_10643: System panic with Memory Mapped Files on UFS filesystem. A typical kernel stack trace would show a data page fault panic in hdl_unsetbits() called from async_pagein_comp(). PHKL_10554: PA-8000 performance; fix kernel-assisted branch prediction. Corrects corner case condition that causes an HPMC. The stack trace would point to module flip_comb(). This corner case has only been seen in lab-internal testing, using pre-release hardware. It has not been seen on any customer's system. PHKL_10452: Panic: kernel stack overflow; trace includes lv_end(). PHKL_10421: When reading a tape on a 7980S tape drive, reading a partial record fails and returns I/O Error. If a tape device receives a bus reset the device will rewind. Following this, when the device is closed, the driver will write EOF marks at the beginning of the tape causing the remaining data to be unusable. When a tape device is opened for write access and the media is write protected the driver returns I/O Error, which can be ambiguous. EPERM (Permission denied) is a more descriptive error. PHKL_10316: When ptrace is called from the DDE debugger while the DDE debugger has watchpoints set, the ptrace system call is called to single step the user process. If the ptrace call is handling a user signal and another signal event is pro- cessed before returning to the user process from ptrace, ptrace may incorretly sent the user's save_state program counter to an incorrect value and return EIO to the parent debugger. PHKL_10288: Panic trap 15 in bwrite() under heavy disk I/O stress. PHKL_10257: Panic with "vn_rele" with EXEC_MAGIC executable run over NFS PHKL_10234: panic: kernel scheduler interrupt PHKL_10199: VxFS version 3 filesystem returns the following file allocation error on filesystems large than 64Gb before the filesystem is actually full: vxfs: msg001: vx_nospace - /dev/vgXX/lvolY file system full (1 block extent) The following console message may also be seen: vxfs: mesg 003: vx_mapbad - /dev/vgXX/lvolY file system free extent bitmap in au nnnn marked bad PHKL_10176: The total length (including terminators) of all argv and env strings passed to a newly-EXECed process was 20480 bytes. If a greater length was detected, the exec() failed with E2BIG. PHKL_10064: Setting a negative timestamp with utime() fails. PHKL_9965: The performance of some drivers (mostly Networking, and for example ATM) was not optimal on Cache Coherent IO systems such as the K-series. PHKL_9931: VxFS hangs waiting for I/O to finish. PHKL_9919: Timing differences between CPU too large, causing midaemon to die frequently (often in less than 15 minutes). PHKL_9909: A deadlock can occur on system running LVM, VxFS and UFS. The hang was introduced by one process running lvmerge on UFS LVs and another process running umount on a VxFS LV. This deadlock can only occur with the following scenario: (1) Process A is running a lvmerge or a lvsplit on a UFS LV (2) Process B is running a mount, umount or sync on a VxFS LV. PHKL_9711: Each time edquota -t is invoked for a VxFS filesystem, it resets the previously defined filesystem time limit back to default (7 days). PHKL_9569: This patch addresses 2 distinct VxFS symptoms: - When trying to take a filesystem snapshot, the mount command could fail with the following error message: # mount -F vxfs -o snapof=/dev/vg00/vxonline \ /dev/vg00/vxbackup /vxbackup vxfs mount: /dev/vg00/vxbackup is already mounted, /vxbackup is busy, or allowable number of mount points exceeded - The system could hang when manipulating directories. PHKL_9529: vgdisplay(1M)/vgextend(1M) show incorrect value for maximum number of PE per PV. PHKL_9517: VxFS filesystem corruption can occur when running the reorg option of the fsadm command on a busy filesystem. System diagnostic messages from the dmesg command will include the following: vxfs: mesg 008: vx_direrr - /??? file system inode X block Y error 6 vxfs: mesg 017: vx_iread - /??? file system inode X marked bad vxfs: mesg 016: vx_ilisterr - /??? file system error reading inode X vxfs: mesg 008: vx_direrr - /??? file system inode X block Y error 6 vxfs: mesg 017: vx_iread - /??? file system error reading inode X PHKL_9372: Panic: "data page fault" when using fsadm to resize a mounted VxFS filesystem with disk quotas. PHKL_9370: If a customer upgrades from 10.01 or 10.10 to 10.20, and tries to increase their VxFS filesystems via SAM, the filesystem will not mount after extending the volume and filesystem. The typical approach for SAM is: 1) unmount the filesystem 2) lvextend the volume 3) extendfs the filesystem 4) mount the filesystem The mount will always fail in this case. PHKL_9365: Random, spurious, rare instances of data corruption, usually in I/O to devices. This is rare enough (and masked by normal system configurations) that it has not been observed in customer systems, only within HP. PHKL_9361: MP machine used as a NFS client panics with: panic: (display==0xb800, flags==0x0) Data page fault panic stack: crash event was a panic panic+0x10 report_trap_or_int_and_panic+0x8c trap+0xbfc $call_trap+0x20 binvalfree_vfs+0x5c rinval+0x10 nfs_unmount+0x20 umount_vfs+0x5c umount_root+0x20 umount+0x98 syscall+0x1a4 PHKL_9273: On MP systems, applications which do file locking frequently can perform poorly. The symptoms are a high switch rate (switch rate > syscall rate) and heavy system activity (%sys > 90%). PHKL_9153: Add write-gathering support for NFS servers. PHKL_9151: This patch includes 3 separate performance enhancements. All are targetted for PA-RISC 8000 processors. 1. Kernel-assisted branch prediction. 2. bl->bll branch stub elimination. 3. Repositioning performance-critical kernel assembly routines. PHKL_9075: Applications using Memory Mapped Files were performing poorly when mapping thousands of pregions to the same file. The problem would mainly be noticed with shared (MAP_SHARED) and exclusive (MAP_FIXED with address in the process private data space) mappings. This patch is required when using the Object Store database product from ODI. Additionally, this patch provides an enhancement to the mprotect(2) system call: mprotect(2) used to fail protecting non mmap(2)'ed addresses. This patch enables to mprotect(2) data, stack and shared memory segment addresses. Finally, this patch fixes a kernel panic with large buffer cache: kernel panic with a data page fault when attempting to copy data from the last page of the third quadrant. This will only occur on systems with a buffer cache of one gigabyte or larger. The panic message will display the following: isr.ior = 0.bffffffc Running strings on a raw sar(1) output file can show some printable strings (sar ignores these). PHKL_8999: Without this patch customers are limited to supporting 2 nodes in a shared environment. With this patch customers can now use SLVM in a 4 node cluster. Alternate links for devices such as the Nike disk array are now supported in a shared environment. This change supports a new -t switch for lvchange, allowing the administrator to limit the time LVM holds I/O requests to be retried on LVs when disks are powerfailed. Without using this option, LVM will hold the I/O requests as long as there is one disk where the data resides which may eventually return. Using this option would cause LVM to give up on the powerfailed disk and return I/O errors to the user application using the LV. This feature is obviously not to be used indiscriminately. For many High Availability applications, having I/O requests held in kernel indefinitely is not acceptable. Most customers should not need to use the new switch. PHKL_8953: The K400 4-way suddenly stopped to work. The user heavily accessed VxFS snapshot filesystem and have done sync's in parallel. PHKL_8908: "SCSI: Unhandled interrupt" and resulting bus reset can cause panic during boot of 710, 715/50, 720 and 725/50 workstations if root disk is LVM and on built-in SCSI bus. It's theoretically possible for the bus reset to cause data corruption on QUANTUM LPS525S disks on the bus. Some M/O drives will not work on the above systems plus 705, 715/33, 730, 735 and 755. PHKL_8755: Fixes a bug with Exabyte tape drives that caused append writes (those not at BOT) to be in non-compressed mode when using the BEST density setting. PHKL_8716: After call to pstat_getmsg(), all accesses to the message queue pstat_getmsg() was called hang. PHKL_8683: System panic with data page fault on ICS. PHKL_8532: System crash dumps are corrupt and unusable. PHKL_8506: This patch changes the behavior of the open() call with a write-protected tape. The open() will now fail with EIO if the mode is not O_RDONLY. PHKL_8481: VxFS performance has improved disk I/O throughput at the cost of extra CPU utilization. This patch improves VxFS performance by implementing a log buffer re-use scheme and also by making modifications to the read/write sleep lock primitives. PHKL_8346: Executables cannot access more than 1.75 GB shared memory. PHKL_8331: Data loss with UFS files using fragments. PHKL_8294: When multiple nfsd processes access the same file simultaneously, they hang in a deadlock. PHKL_8203: MP system hangs during panic. The LED shows system staying at INIT CB0B. Machine needs to be TOC'ed to save the core dump. PHKL_8187: Select timeouts are retried forever, i.e. I/O requests never complete when a device is removed. SCSI bus hang and reset. PHKL_8128: Device files other than those that use the BEST density do not work. Opening such a device file returns EINVAL. This happens only on DLT tape drives. PHKL_8084: LVM may return I/O's with errors instead of sending them to an alternate link. This patch also facilitates using "vgreduce -f" for PVs which have alternate links; without this patch "vgreduce -f" is not allowed on LVM disks with alternate links. PHKL_8028: Without immediate reporting enabled a DLT tape drive will take several seconds for each filemark written. If a user application is writing many filemarks to a tape the performance will be poor. This patch enables immediate reporting of filemarks, which should improve performance for an application that writes many filemarks to a tape. PHKL_7987: System hang. Select timeouts with EMC/Symmetrix disk array. PHKL_7951: Ptrace not allowing writes on PA8000 to some floating point registers. PHKL_7899: KI queuedone, enqueue and queuestart traces on VxFS may contain NULL values in the b_apid and b_upid fields. With a system running a heavy load using VxFS on LVM, the following panic may occur: "lv_syncx: returning error: 5" Systems running VxFS may hang due to a deadlock problem. The setuid bit will be removed on a VxFS file when the file is edited or text has been appended to it when run as root. PHKL_7870: lvreduce(1M) may cause a system panic, if it is used to reduce an LV which was left inconsistent by a prior LVM operation. lvreduce(1M) could not be used to remove LVs that were somehow corrupted, if it was, the command would cause a system panic. PHKL_7776: It's possible for a VxFS filesystem to get into a state where it can't be mounted (except read-only), but fsck(1M) does not report any problem with it. At mount time, the kernel prints the following warning on the console: vxfs: mesg 012: vx_iget - <null> file system invalid inode number XXX and mount(1M) fails with the following message: vxfs mount: /dev/XXX is not a vxfs file system. Once a filesystem has gotten into this state, it remains unmountable, even after running fsck(1M). Defect Description: PHKL_15915: Failure to allocate pdir alias entries causes the application to receive SIGBUS. Any application that makes extensive use of alias pdir entries running on a fast system will use all the available alias pdir entries before the unhashdaemon wakes up.(which is responsible to allocate more of them when alias pdir entries are all consumed). This daemon wakes up once per second. We use alias pdir entries when we want to mmap the same offset twice. When the numbers of available entries fall below the thresholds (min_alias_entries and min_alias_pdirs) the unhashdaemon calls grow_aatables() to allocate more entries. The fix was to call grow_aatables() directly whenever need arises instead of relying on the unhashdaemon to wakeup at the right time. PHKL_15787: LVM recovered PVLinks serially, so in situations where 100's of links can fail simultaneously (eg. FibreChannel hubs) the time to switch all the links can be hours. The prior PHKL_15200 version of this code did not always properly detect active-passive (Nike and Galaxy) disk array paths. HFS files that have been unlinked do not have their associated buffers removed from the buffer cache. This causes the buffers to be reused with their old flags intact which could have the side effect of turning async writes into delayed writes. These delayed writes could then flood the device with I/O during a sync. PHKL_15766: SR 5003414540 With the release of Enhanced DFS 1.5.1(EFS) the kload driver has been removed from the kernel master driver file (/usr/conf/master.d/core-hpux). This was done because EFS no longer requires kload. For users who are still using a version of DFS prior to EFS, they will have to re-enable kload by removing "*replaced-by-efs" from /usr/conf/master.d/core-hpux and then rebuilding the kernel. Another option would be to upgrade to EFS. Example to re-enable kload in /usr/conf/master.d/core-hpux: from: *replaced-by-efs kload kload 14 100 -1 -1 to: kload kload 14 100 -1 -1 SR 4701394163 The defect was in the test done in mprotect. That test checks if the pregion submitted to mprotect has the appropriate type. Because of the defect, pregions that should not be "mprotected" (in our case a NULLDEREF pregion) may go through and get mprotected. PHKL_15742: 1. SR: 1653236869 DTS: JAGaa01996 The problem is that the rfs_readdir() routine in 10.20 calls VOP_READDIR2(); for vxfs, this merely calls generic_readdir2() which was the problem. The generic_readdir2() routine assumes that "real byte offsets" of returned directory entries and the offset of the corresponding entry in the actual directory are one and the same; for vxfs, this is not the case. The fix was to backport the VxFS-specific vx_readdir2() 2. SR: 4701393074 DTS: JAGaa10827 While creating a new JFS file, if attributes exist, they are passed from the parent directory to the new files. 3. SR: 5003295238 DTS: JAGaa09110 The problem is that we only do a VX_MPURGE(vp) if we had gotten an error earlier in the routine. The change (in 10.30 and onward) makes us always do a VX_MPURGE(vp) if we're not currently mmap'ped regardless of whether we got an error. 4. SR: 4701393819 DTS: JAGaa11061 vx_vn_bread(), called by NFS via VOP_BREAD(), should not release the buffer to buffer cache without checking as it could have a private buffer if direct I/O is involved. This defect was introduced by PHKL_15619. PHKL_15619: SR: 4701393819 CR: JAGaa11061 The vx_vn_bread() function holds a buffer busy while it tries to get the lock on the buffer's inode. There is a window through which another thread can obtain the inode lock and then wait for the buffer that vx_vn_bread() is holding, thus causing a dead lock. SR: 4701349175 DTS: DSDe435102 Classic "thundering herd" problem was made worse by the fact that the first thing each woken process did was to try to lock a "COMMON" spinlock. A process that gets the spinlock first, locks the INODE and releases the spinlock has to try hard to be able to get the spinlock a second time while it tries to unlock the same inode. SR: 4701393884 CR: JAGaa08709 The code in the 'lofs' file system allows removal of its mount point. SR: 5003413278 DTS: DSDe442455 During vxfs file system mount, a file system structure is allocated and initialized. If the initialization fails (eg. bad superblock, missing mount device), the backout code in the mount routine does not unlock the file system structure and free it from the file system list properly. Any processes that walk the file system list will hang. This defect was introduced by PHKL_15244. SR: 5003421628 DTS: JAGaa10135 bcfeeding_frenzy() is called to free up virtual space in buffer cache resource maps. In systems with large buffer cache defined, it is called excessively to balance virtual memory allocation in two buffer cache maps. PHKL_14803 introduces some code that has side effects aggravating this problem. The fix is to reduce the calling of bcfeeding_frenzy() and to backout some changes made in PHKL_14803. SR: 1653259408 DTS: DSDe441605 Problem with the fiber-channel hubs PVLinks performance improvement code. May cause Nike and Galaxy disk arrays to switch repeatedly between primary and alternate links when a link is restored or when a transient error on the primary link occurs. Backing out the above code also removes the problem introduced in PHKL_15199 that causes MC/Service Guard cluster system with Nike array to panic. SR: 4701393058 CR: JAGaa10826 When the VxFS file system is full, no extent is allocated and there is no room in extent map for new extent descriptor. In this case, the very first call to extent allocation fails to allocate an extent so the vx_extalloc structure remains uninitialized. A bug in the code assumes that an indirect address extent has been allocated and its descriptor must be added to the map. If the map has unused descriptor records, the existing descriptors are shifted to make room for a new one. We then add a bogus indirect address extent to the map. PHKL_7967: fuser does not report processes in LOCAL FILESYSTEMS lofs. To reproduce this problem, do following: mkdir /test #create new directory mount /home /test cd /test before the fix, "fuser -c /test" reports no process, after the fix, "ufser -c /test" reports the local shell. PHKL_15492: Before lvlnboot will permit the configuration of a dump partition, it checks the addressing range of the interface card's IODC. If the maximum address of the IODC is less than the size of the dump partition plus its offset from the start of the disk, then lvlnboot denies the request and issues the above message to the user. The determination of an interface card's max IODC address is done by the function get_max_iodc_addr() in dump_conf.c The function returns MAXINT (2G) by default, but also uses a hard-coded table which lists the hversion and sversion of each card known to be 4Gig capable. If the interface card in question is found in this table, the function returns MAXUINT (4G). Unfortunately, PCI cards do not contain h/sversion numbers therefore all requests to dump beyond 2G through these cards was denied, even though they are capable of it. This patch, augments get_max_iodc_addr() with a test, "isPCI," to determine of the interface card is a PCI device. If true, the routine returns MAXUINT(4G). PHKL_15495: After removing a buffer from its hash chain, vx_bcacheclear must set b_which_hlock when it inserts buffer onto the new hash chain, otherwise we can get hash chain corruption. It showed up here as a spinlock deadlock as we started walking one hash chain, but it pointed to a buffer that was actually on another hash chain, so it will never hit our loop termination condition. PHKL_15504: A system that uses DMAPI with extended information stored in inodes is unable to write extended information to existing files after a filesystem becomes full. An application like OmniStorage that uses DMAPI is unable to update existing inodes after the filesystem becomes full. This patch allows a DMAPI ENOSPACE event to be generated when the filesystem is nearly, but not completely, out of space. An application using large file support cannot use the KDM_IOC_WRITEINVIS DMAPI ioctl to do an invisible write. PHKL_15456: SR 5003418244, DTS JAGaa07539: In 10.X, setitimer() does not check for the validity of user arguments properly. When an application uses setitimer(2) with a negative interrupt timer value, it causes the kernel timer expiration routine to spin in a loop while holding the timer callout_lock. If any other process tries to grab the callout_lock at this time, it will result a spinlock deadlock panic. The fix is to check the validity of the arguments and return an EINVAL for negative values. SR 4701391730, DTS DSDe438419: Under certain conditions, the system could violate internal lock-order rules while mmap(2)ing; the fix was to give up and reacquire the region lock to avoid this. SR 1653177089, DTS DSDe429996: In 10.xx buffer caching was disabled for block devices. This produced degraded performance in reads/writes to block devices; this patch reenables buffer caching for block devices that are not mounted as filesystems, and is a re-implementation of PHKL_13680. PHKL_15321: From Veritas Incident report, HP has reported the problem described below on a V3 filesystem. Basically, we will fail to reorg V3 filesystems when the orgtype of the original inode is IORG_TYPED and the reorg inode has to grow to indirect. In fshp releases an inode is not switched to typed extent when an extent is entered through vx_ext4_enter(). The lack of the switch requires allocating fixed size extents of size fs->fs_iaddrlen for indirect extents of a reorg inode. This is not the case in vx_reorg_emap() when the reorg inode is growing to indirect. PHKL_15244: - DTS: DSDe442455 SR: 5003413278 When multiple processes compete in mounting a snapshot filesystem using the same LV, a race condition in VxFS causes buffers of one of the snapshots to contain partially initialized data. Flushing these buffers results system panic. - DTS: JAGaa02119 SR: 5003407601 During reboot, the reboot processor is handling the reboot process, while all other processors are in idle spin. When the reboot process runs into a situation that it has to wait (e.g. biowait() for I/O completion) and gets switched out, the reboot processor at this time enters idle() and it should pick up the runnable threads from the other processors and complete the processing. The defect is that the reboot processor fails to schedule runnable threads belonging to the other processors. If the reboot's biowait() depends on the completion of other threads, the system hangs indefinitely. PHKL_15199: LVM recovered PVLinks serially so in situations where 100's of links can fail simultaneously (eg. FibreChannel hubs) the time to switch all the links can be hours. The PVSparing defect resulted because when a lock could not be obtained for a key data structure the sparing code assumed that no spares were available instead of retrying the operation at a later time. The UFS defect appeared to have been intruduced with PHKL_14804. Excessive rmprobe calls were being made even when the VM for buffers exceeded the buffer_low watermark. PHKL_15145: Dirty buffers are not flushed to mirrored disk on lvsplit. PHKL_15085: The graphics_exit hook was being called in the wrong place. It was called after all of the pregions were released in the exec path, so graphics DMA buffers were not properly cleaned up, and then graphics_exit could not find them when it was called. The problem can be reproduced by having a process do graphics DMA with VISUALIZE-FX hardware and then call exec without first forking. PHKL_15057: The current first fit policy for allocating virtual addresses for shared objects causes a form of fragmentation that is preventing some user's applciations from running. Since the algorithm is first-fit, small allocation requests can cause a large block of free virtual address range to be broken up into small ranges, thereby preventing bigger allocation requests from succeeding. PHKL_14955: Any kernel booted on PA-RISC 2.0 will not be debuggable, due to firmware changes in PCX-U. PHKL_14953: I/O requests passing through the LVM layer in the process of being sent to the disk hang when the PV-link is broken by pulling the FC cable. The I/O requests wait on the wait queue as the primary LVM link is broken and also the disk is not accessible. But the LVM code was incorrectly setting the disk as unaccessible even after the link-switch, so after the alternate link is restored, the disk is still not accessible to those I/O requests. PHKL_14917: All SCSI timeouts were set to 30 seconds. With this patch, we identify the MO drives and set a longer (5 mins) timeout for those drives. PHKL_14856: Race condition on shared interrupt bit caused the driver to mishandle setting up future I/O jobs. PHKL_14803: SR: 5003407601 DTS: JAGaa02119 The reboot process is stuck at biowait() while sync'ing disks because of a failure in acquiring LVM physical buffers. The lv_reschedule() routine needs to ensure a successful retry in this case because there is no other process to trigger the emptying of the physical buffer wait queue during reboot. SR: 5003407619 DTS: JAGaa01516 When buffer cache allocation reaches the defined maximum, the allocation of new buffers from system memory stops. When buffers are freed, their physical memory spaces, instead of being returned to the system, are saved in a pool to be reused for new buffers. A bug in the getnewbuf() routine disallows the reclaiming of this available memory when bufpages reaches the ceiling. Further more, another bug in the routine that frees up space for the buffer cache resource map erroneously releases more buffers than necessary. The prohibition of reusing the memory from the reserved pool and the lost of free buffers result running out of buffers in the freelist, causing all I/O processes hung in sleep wait. PHKL_14740: Device resets on FibreChannel devices can overlap and interfere with subsequent VG activation. PHKL_14685: The master file had to be changed to point to libhp-ux.a instead of libflkmgr.a. PHKL_14613: This system hang is hard to reproduce. Once in a while, during heavy load on UFS filesystems if a LV is being created or extended, the UFS code deadlocks due to ordering problems in acquiring the inode lock and the device vnode lock. PHKL_14568: - SR:1653254987 DTS:JAGaa01797 The problem is an MP race condition caused by a defect in the routine lv_tbl_reimage_realloc(). It is freeing the lv_bitmap before pausing the LV. This results in I/Os possibly reaching scheduling routines (such as lv_parallel()) while lv_tbl_reimage_realloc() is in the middle of freeing the lv_bitmap. The fix is to call lv_pause() before calling KFREE() on lv_bitmap. - SR:4701379347 DTS:DSDe441470 Add flock manager driver functionality to the kernel. - SR:1653216952 DTS:DSDe437110 The data path in the kernel code that supports sleep(3C) is not wide enough to support parameter values larger than 21474836 seconds. If a larger value is passed, incorrect arithmetic is performed, with results varying from immediate return (with or without error) to sleeping for the wrong length of time. SR: 1653096131 1653138164 1653166066 1653166496 1653166983 1653172908 1653177089 1653179895 1653183699 1653189738 1653192294 1653194555 1653194977 1653199802 1653202754 1653207175 1653211607 1653213082 1653214338 1653215020 1653215467 1653216077 1653216606 1653216952 1653218065 1653220079 1653221820 1653221895 1653223404 1653227983 1653228106 1653230771 1653235176 1653236869 1653237842 1653239137 1653244012 1653247486 1653248690 1653253229 1653254987 1653258681 1653259408 1653260158 4701327338 4701327544 4701329292 4701329300 4701329417 4701329433 4701329441 4701330647 4701333419 4701334367 4701334698 4701334847 4701334995 4701335497 4701335935 4701336412 4701337394 4701339226 4701341362 4701341479 4701341644 4701341669 4701342089 4701342121 4701342147 4701344515 4701345843 4701346122 4701346791 4701347922 4701348359 4701349175 4701349431 4701350157 4701350975 4701351932 4701352278 4701352799 4701353078 4701353094 4701353102 4701353888 4701354274 4701354803 4701354837 4701354845 4701355123 4701355321 4701355560 4701355610 4701356766 4701356931 4701358143 4701358523 4701360693 4701360925 4701361188 4701361444 4701361758 4701362111 4701364182 4701365114 4701365791 4701371294 4701371617 4701372276 4701373050 4701374520 4701375816 4701375956 4701376269 4701376863 4701377226 4701377580 4701378117 4701379347 4701379354 4701380519 4701380808 4701381608 4701382564 4701383315 4701383612 4701388975 4701391094 4701391730 4701391797 4701393074 4701393819 4701393884 4701394163 4701394635 4701396200 5000698738 5000716225 5003281469 5003295238 5003314633 5003317487 5003318667 5003323493 5003325506 5003328237 5003329078 5003330746 5003330910 5003334961 5003341925 5003344630 5003345496 5003348425 5003353797 5003356345 5003357616 5003359414 5003359489 5003360024 5003360446 5003361766 5003363523 5003363820 5003364224 5003365692 5003366500 5003366971 5003367888 5003367979 5003368290 5003379156 5003380113 5003384586 5003385203 5003385393 5003387019 5003387183 5003387407 5003397174 5003398800 5003399188 5003407221 5003407601 5003407619 5003409185 5003413278 5003414540 5003418244 5003421628 5003425512 Patch Files: /usr/conf/h/_flkmgr.h /usr/conf/h/audit.h /usr/conf/h/dnlc.h /usr/conf/h/fss.h /usr/conf/h/mtio.h /usr/conf/io/dma.h /usr/conf/lib/libdmapi.a(kdm_core.o) /usr/conf/lib/libdmapi.a(vx_dmattr_table.o) /usr/conf/lib/libhp-ux.a(asm_rdb.o) /usr/conf/lib/libhp-ux.a(asm_rv.o) /usr/conf/lib/libhp-ux.a(asm_scall.o) /usr/conf/lib/libhp-ux.a(asm_utl.o) /usr/conf/lib/libhp-ux.a(asm_vm.o) /usr/conf/lib/libhp-ux.a(asm_vm_pdir.o) /usr/conf/lib/libhp-ux.a(audctl.o) /usr/conf/lib/libhp-ux.a(bcopy.o) /usr/conf/lib/libhp-ux.a(btlb.o) /usr/conf/lib/libhp-ux.a(bzero.o) /usr/conf/lib/libhp-ux.a(clock.o) /usr/conf/lib/libhp-ux.a(cpd.o) /usr/conf/lib/libhp-ux.a(dma_A.o) /usr/conf/lib/libhp-ux.a(dma_s700.o) /usr/conf/lib/libhp-ux.a(dump.o) /usr/conf/lib/libhp-ux.a(dump_conf.o) /usr/conf/lib/libhp-ux.a(eisa.o) /usr/conf/lib/libhp-ux.a(flipper.o) /usr/conf/lib/libhp-ux.a(flkmgr.o) /usr/conf/lib/libhp-ux.a(flkmgr_dom.o) /usr/conf/lib/libhp-ux.a(flkmgr_flk.o) /usr/conf/lib/libhp-ux.a(flkmgr_hp.o) /usr/conf/lib/libhp-ux.a(flkmgr_main.o) /usr/conf/lib/libhp-ux.a(flkmgr_mm.o) /usr/conf/lib/libhp-ux.a(flkmgr_pm.o) /usr/conf/lib/libhp-ux.a(gio_node.o) /usr/conf/lib/libhp-ux.a(hdl_fault.o) /usr/conf/lib/libhp-ux.a(hdl_init.o) /usr/conf/lib/libhp-ux.a(hdl_mprotect.o) /usr/conf/lib/libhp-ux.a(hdl_policy.o) /usr/conf/lib/libhp-ux.a(hdl_trans.o) /usr/conf/lib/libhp-ux.a(init_main.o) /usr/conf/lib/libhp-ux.a(interrupt.o) /usr/conf/lib/libhp-ux.a(io.o) /usr/conf/lib/libhp-ux.a(ios_int.o) /usr/conf/lib/libhp-ux.a(ios_mem.o) /usr/conf/lib/libhp-ux.a(kern_acct.o) /usr/conf/lib/libhp-ux.a(kern_exec.o) /usr/conf/lib/libhp-ux.a(kern_exit.o) /usr/conf/lib/libhp-ux.a(kern_fork.o) /usr/conf/lib/libhp-ux.a(kern_kload.o) /usr/conf/lib/libhp-ux.a(kern_mman.o) /usr/conf/lib/libhp-ux.a(kern_sig.o) /usr/conf/lib/libhp-ux.a(lbcopy.o) /usr/conf/lib/libhp-ux.a(lbzero.o) /usr/conf/lib/libhp-ux.a(lo_subr.o) /usr/conf/lib/libhp-ux.a(lo_vfsops.o) /usr/conf/lib/libhp-ux.a(lo_vnops.o) /usr/conf/lib/libhp-ux.a(lv_config.o) /usr/conf/lib/libhp-ux.a(lv_lvm.o) /usr/conf/lib/libhp-ux.a(lw_scall.o) /usr/conf/lib/libhp-ux.a(machdep.o) /usr/conf/lib/libhp-ux.a(outlaw.o) /usr/conf/lib/libhp-ux.a(pa_ccio.o) /usr/conf/lib/libhp-ux.a(pa_cdio.o) /usr/conf/lib/libhp-ux.a(pa_lvl1.o) /usr/conf/lib/libhp-ux.a(pa_map.o) /usr/conf/lib/libhp-ux.a(pci_debug.o) /usr/conf/lib/libhp-ux.a(pgcopy.o) /usr/conf/lib/libhp-ux.a(pm_clockint.o) /usr/conf/lib/libhp-ux.a(pm_config.o) /usr/conf/lib/libhp-ux.a(pm_context.o) /usr/conf/lib/libhp-ux.a(pm_core.o) /usr/conf/lib/libhp-ux.a(pm_getpid.o) /usr/conf/lib/libhp-ux.a(pm_policy.o) /usr/conf/lib/libhp-ux.a(pm_proc.o) /usr/conf/lib/libhp-ux.a(pm_procdup.o) /usr/conf/lib/libhp-ux.a(pm_ptrace.o) /usr/conf/lib/libhp-ux.a(pm_resource.o) /usr/conf/lib/libhp-ux.a(pm_rtsched.o) /usr/conf/lib/libhp-ux.a(pm_sendsig.o) /usr/conf/lib/libhp-ux.a(pm_signal.o) /usr/conf/lib/libhp-ux.a(pm_swtch.o) /usr/conf/lib/libhp-ux.a(pm_threads.o) /usr/conf/lib/libhp-ux.a(pm_timers.o) /usr/conf/lib/libhp-ux.a(protection.o) /usr/conf/lib/libhp-ux.a(pstat.o) /usr/conf/lib/libhp-ux.a(rdb.o) /usr/conf/lib/libhp-ux.a(rdb_boot.o) /usr/conf/lib/libhp-ux.a(rdb_com.o) /usr/conf/lib/libhp-ux.a(rdb_com_lan.o) /usr/conf/lib/libhp-ux.a(rdb_lan.o) /usr/conf/lib/libhp-ux.a(rdb_mp.o) /usr/conf/lib/libhp-ux.a(rdb_rs232.o) /usr/conf/lib/libhp-ux.a(resume.o) /usr/conf/lib/libhp-ux.a(scsi_c720.o) /usr/conf/lib/libhp-ux.a(scsi_ctl.o) /usr/conf/lib/libhp-ux.a(scsi_disk.o) /usr/conf/lib/libhp-ux.a(scsi_tape.o) /usr/conf/lib/libhp-ux.a(sem_alpha.o) /usr/conf/lib/libhp-ux.a(spec_vnops.o) /usr/conf/lib/libhp-ux.a(spinlock.o) /usr/conf/lib/libhp-ux.a(subr_ksleep.o) /usr/conf/lib/libhp-ux.a(subr_rmap.o) /usr/conf/lib/libhp-ux.a(subr_timers.o) /usr/conf/lib/libhp-ux.a(sysV_shm.o) /usr/conf/lib/libhp-ux.a(trap.o) /usr/conf/lib/libhp-ux.a(ufs_mchdep.o) /usr/conf/lib/libhp-ux.a(ulbcopy.o) /usr/conf/lib/libhp-ux.a(vfs.o) /usr/conf/lib/libhp-ux.a(vfs_bio.o) /usr/conf/lib/libhp-ux.a(vfs_dnlc.o) /usr/conf/lib/libhp-ux.a(vfs_scalls.o) /usr/conf/lib/libhp-ux.a(vfs_vm.o) /usr/conf/lib/libhp-ux.a(vfs_vnode.o) /usr/conf/lib/libhp-ux.a(vm_fault.o) /usr/conf/lib/libhp-ux.a(vm_kern.o) /usr/conf/lib/libhp-ux.a(vm_machdep.o) /usr/conf/lib/libhp-ux.a(vm_machreg.o) /usr/conf/lib/libhp-ux.a(vm_mmap.o) /usr/conf/lib/libhp-ux.a(vm_page.o) /usr/conf/lib/libhp-ux.a(vm_pdir1_1.o) /usr/conf/lib/libhp-ux.a(vm_pdir2_0.o) /usr/conf/lib/libhp-ux.a(vm_pregion.o) /usr/conf/lib/libhp-ux.a(vm_region.o) /usr/conf/lib/libhp-ux.a(vm_sched.o) /usr/conf/lib/libhp-ux.a(vm_superpage.o) /usr/conf/lib/libhp-ux.a(vm_text.o) /usr/conf/lib/libhp-ux.a(vm_vas.o) /usr/conf/lib/libhp-ux.a(vm_vhand.o) /usr/conf/lib/libhp-ux.a(wsio_scsi.o) /usr/conf/lib/libhp-ux.a(wsio_util.o) /usr/conf/lib/liblvm.a(lv_block.o) /usr/conf/lib/liblvm.a(lv_cluster_lock.o) /usr/conf/lib/liblvm.a(lv_defect.o) /usr/conf/lib/liblvm.a(lv_hp.o) /usr/conf/lib/liblvm.a(lv_ioctls.o) /usr/conf/lib/liblvm.a(lv_kdb.o) /usr/conf/lib/liblvm.a(lv_lvsubr.o) /usr/conf/lib/liblvm.a(lv_malloc.o) /usr/conf/lib/liblvm.a(lv_mircons.o) /usr/conf/lib/liblvm.a(lv_pbuf.o) /usr/conf/lib/liblvm.a(lv_phys.o) /usr/conf/lib/liblvm.a(lv_schedule.o) /usr/conf/lib/liblvm.a(lv_spare.o) /usr/conf/lib/liblvm.a(lv_strategy.o) /usr/conf/lib/liblvm.a(lv_stub.o) /usr/conf/lib/liblvm.a(lv_subr.o) /usr/conf/lib/liblvm.a(lv_syscalls.o) /usr/conf/lib/liblvm.a(lv_vgda.o) /usr/conf/lib/liblvm.a(lv_vgsa.o) /usr/conf/lib/liblvm.a(sh_vgsa.o) /usr/conf/lib/liblvm.a(slvm_comm.o) /usr/conf/lib/liblvm.a(slvm_schedule.o) /usr/conf/lib/libpci.a(dino3.o) /usr/conf/lib/libpci.a(dino_cdio.o) /usr/conf/lib/libpci.a(h2p_iface.o) /usr/conf/lib/libpci.a(pci.o) /usr/conf/lib/libpci.a(pci_cdio.o) /usr/conf/lib/libpci.a(pci_wsio.o) /usr/conf/lib/libprm.a(kern_fss.o) /usr/conf/lib/libufs.a(ufs_alloc.o) /usr/conf/lib/libufs.a(ufs_inode.o) /usr/conf/lib/libufs.a(ufs_vfsops.o) /usr/conf/lib/libufs.a(ufs_vnops.o) /usr/conf/lib/libvxfs_adv.a(vx_dmattr.o) /usr/conf/lib/libvxfs_adv.a(vx_full.o) /usr/conf/lib/libvxfs_adv.a(vx_kdmi.o) /usr/conf/lib/libvxfs_adv.a(vx_reorg.o) /usr/conf/lib/libvxfs_adv.a(vx_sample_dmattr.o) /usr/conf/lib/libvxfs_base.a(vx_alloc.o) /usr/conf/lib/libvxfs_base.a(vx_attr.o) /usr/conf/lib/libvxfs_base.a(vx_bio.o) /usr/conf/lib/libvxfs_base.a(vx_bmapext4.o) /usr/conf/lib/libvxfs_base.a(vx_bmaptyped.o) /usr/conf/lib/libvxfs_base.a(vx_bsdquota.o) /usr/conf/lib/libvxfs_base.a(vx_dirl.o) /usr/conf/lib/libvxfs_base.a(vx_dmstubs.o) /usr/conf/lib/libvxfs_base.a(vx_fsetsubr.o) /usr/conf/lib/libvxfs_base.a(vx_hpuxsubr.o) /usr/conf/lib/libvxfs_base.a(vx_iflush.o) /usr/conf/lib/libvxfs_base.a(vx_inode.o) /usr/conf/lib/libvxfs_base.a(vx_itrunc.o) /usr/conf/lib/libvxfs_base.a(vx_lite.o) /usr/conf/lib/libvxfs_base.a(vx_log.o) /usr/conf/lib/libvxfs_base.a(vx_mount.o) /usr/conf/lib/libvxfs_base.a(vx_rdwri.o) /usr/conf/lib/libvxfs_base.a(vx_replay.o) /usr/conf/lib/libvxfs_base.a(vx_vfsops.o) /usr/conf/lib/libvxfs_base.a(vx_vm.o) /usr/conf/lib/libvxfs_base.a(vx_vnops.o) /usr/conf/machine/cpu.h /usr/conf/machine/reg.h /usr/conf/master.d/core-hpux /usr/conf/master.d/flkmgr /usr/conf/space.h.d/core-hpux.h /usr/conf/space.h.d/flkmgr_globals.h /usr/conf/wsio/pci.h /usr/include/dmapi.h /usr/include/machine/cpu.h /usr/include/machine/reg.h /usr/include/sys/audit.h /usr/include/sys/dma.h /usr/include/sys/dnlc.h /usr/include/sys/fs/vx_hpux.h /usr/include/sys/fss.h /usr/include/sys/mtio.h /usr/include/sys/pci.h what(1) Output: Information removed by HP-UX Patch Administrators to reduce size. cksum(1) Output: Information removed by HP-UX Patch Administrators to reduce size. Patch Conflicts: None Patch Dependencies: s700: 10.20: PHCO_12922 PHCO_8871 PHNE_13245 Hardware Dependencies: None Other Dependencies: Please be advised that a savecore(1M) patch (PHCO_12822) may be needed to enable savecore to correctly handle a dump area that extends beyond the 2GB offset on the disk. Supersedes: PHKL_7776 PHKL_7870 PHKL_7899 PHKL_7951 PHKL_7967 PHKL_7987 PHKL_8028 PHKL_8084 PHKL_8128 PHKL_8187 PHKL_8203 PHKL_8294 PHKL_8331 PHKL_8346 PHKL_8481 PHKL_8506 PHKL_8532 PHKL_8683 PHKL_8716 PHKL_8755 PHKL_8908 PHKL_8953 PHKL_8999 PHKL_9075 PHKL_9151 PHKL_9153 PHKL_9273 PHKL_9361 PHKL_9365 PHKL_9370 PHKL_9372 PHKL_9517 PHKL_9529 PHKL_9569 PHKL_9711 PHKL_9909 PHKL_9919 PHKL_9931 PHKL_9965 PHKL_10064 PHKL_10176 PHKL_10199 PHKL_10234 PHKL_10257 PHKL_10288 PHKL_10316 PHKL_10421 PHKL_10452 PHKL_10554 PHKL_10643 PHKL_10675 PHKL_10689 PHKL_10755 PHKL_10756 PHKL_10757 PHKL_10769 PHKL_10800 PHKL_10821 PHKL_10930 PHKL_10932 PHKL_10953 PHKL_10966 PHKL_11002 PHKL_11006 PHKL_11013 PHKL_11039 PHKL_11055 PHKL_11085 PHKL_11164 PHKL_11238 PHKL_11244 PHKL_11247 PHKL_11316 PHKL_11321 PHKL_11332 PHKL_11339 PHKL_11351 PHKL_11358 PHKL_11406 PHKL_11408 PHKL_11471 PHKL_11519 PHKL_11545 PHKL_11561 PHKL_11607 PHKL_11614 PHKL_11632 PHKL_11637 PHKL_11696 PHKL_11730 PHKL_11733 PHKL_11766 PHKL_11860 PHKL_11902 PHKL_12042 PHKL_12073 PHKL_12088 PHKL_12100 PHKL_12110 PHKL_12217 PHKL_12306 PHKL_12378 PHKL_12397 PHKL_12409 PHKL_12601 PHKL_12633 PHKL_12660 PHKL_12662 PHKL_12669 PHKL_12901 PHKL_12963 PHKL_12997 PHKL_13014 PHKL_13155 PHKL_13206 PHKL_13237 PHKL_13247 PHKL_13260 PHKL_13305 PHKL_13452 PHKL_13508 PHKL_13514 PHKL_13680 PHKL_13684 PHKL_13713 PHKL_13744 PHKL_13761 PHKL_13768 PHKL_13795 PHKL_13868 PHKL_13874 PHKL_13911 PHKL_13986 PHKL_14009 PHKL_14012 PHKL_14049 PHKL_14126 PHKL_14183 PHKL_14225 PHKL_14321 PHKL_14323 PHKL_14490 PHKL_14568 PHKL_14613 PHKL_14685 PHKL_14740 PHKL_14803 PHKL_14856 PHKL_14917 PHKL_14953 PHKL_14955 PHKL_15057 PHKL_15085 PHKL_15145 PHKL_15199 PHKL_15244 PHKL_15321 PHKL_15456 PHKL_15492 PHKL_15495 PHKL_15504 PHKL_15619 PHKL_15742 PHKL_15766 PHKL_15787 Equivalent Patches: PHKL_15916: s800: 10.20 Patch Package Size: 3830 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 PHKL_15915 5a. For a standalone system, run swinstall to install the patch: swinstall -x autoreboot=true -x match_target=true \ -s /tmp/PHKL_15915.depot 5b. For a homogeneous NFS Diskless cluster run swcluster on the server to install the patch on the server and the clients: swcluster -i -b This will invoke swcluster in the interactive mode and force all clients to be shut down. WARNING: All cluster clients must be shut down prior to the patch installation. Installing the patch while the clients are booted is unsupported and can lead to serious problems. The swcluster command will invoke an swinstall session in which you must specify: alternate root path - default is /export/shared_root/OS_700 source depot path - /tmp/PHKL_15915.depot To complete the installation, select the patch by choosing "Actions -> Match What Target Has" and then "Actions -> Install" from the Menubar. 5c. For a heterogeneous NFS Diskless cluster: - run swinstall on the server as in step 5a to install the patch on the cluster server. - run swcluster on the server as in step 5b to install the patch on the cluster clients. By default swinstall will archive the original software in /var/adm/sw/patch/PHKL_15915. If you do not wish to retain a copy of the original software, you can create an empty file named /var/adm/sw/patch/PATCH_NOSAVE. Warning: If this file exists when a patch is installed, the patch cannot be deinstalled. Please be careful when using this feature. It is recommended that you move the PHKL_15915.text file to /var/adm/sw/patch for future reference. To put this patch on a magnetic tape and install from the tape drive, use the command: dd if=/tmp/PHKL_15915.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: - SR: 5003387407, DDTS: JAGaa00919 introduces two global variables: vx_enospace_factor vx_nwriters These variables control when DMAPI ENOSPACE events are generated. 'vx_enospace_factor' is the fraction of the filesystem below which we start checking write requests to see if they exceed available space. So a 'vx_enospace_factor' of 20 (default) means that no pessimistic ENOSPACE events will be checked until less than 1/20th of the filesystem is free. So, the smaller 'vx_enospace_factor', the earlier checking is done on a filesystem. Note that if 'vx_enospace_factor' is set to less than or equal to zero, the default value of 20 will be used. 'vx_nwriters' is the fraction of space left that a write must exceed to trigger a pessimistic ENOSPACE. If 'vx_nwriters' is 8, which is the default, then the size of a write must be greater than 1/8th the blocks free to trigger an ENOSPACE. So, the larger 'vx_nwriters' is, the more space will be left on the filesystem when we get the ENOSPACE event. Note that if 'vx_nwriters' is set to less than or equal to zero, the default value of 8 will be used. You can use 'adb' to set and check the values of these variables. For example, to set 'vx_nwriters' to 32 decimal: echo 'vx_nwriters/W 20'|adb -w /stand/vmunix /dev/kmem To read the value of the variable in decimal: echo 'vx_nwriters/D'|adb /stand/vmunix /dev/kmem ----- The global variable (flag) `use_bestfit' determines what allocation policy will be used. The default setting of this flag is 0, resulting in first-fit being used for all allocations for shared virtual addresses. To enable the system to use best-fit, this flag (use_bestfit) must be set to a non-zero value (say 1) using `adb.' The value can be set/reset at any time during system operation. The policy that will be used is based on the current value of this flag. ---- The patch is applied to the kernel being debugged on the target machine, not the host machine where the debugger is run. ---- - SR: 4701382564, DTS: DSDe441726 Two tunable variables have been defined for this patch. They are: kern_vm_pct - the threshold percentage. When the free sysmap space as a percentage of 1 GB falls below the value of kern_vm_pct, warning message is printed to notify the user of this condition. kern_vm_scan_rate - the time interval in seconds between subsequent checks that statdaemon makes to determine if the free kernel sysmap space as a percentage of 1GB is below the threshold percentage (kern_vm_pct) value or not; if below the threshold value print the warning message about the condition. By default both kern_vm_pct and kern_vm_scan_rate are set to 0 ie. by default the monitoring of the free kernel sysmap space is turned off. To turn on the feature you need to set kern_vm_scan_rate and kern_vm_pct variables to non zero value. eg. In file /stand/system * Tunable parameters kern_vm_pct 10 kern_vm_scan_rate 10 Threshold percentage is 10%; scan rate is 10 seconds. ---- CAUTION: Failure to follow the instructions in this section could result in undesired system behavior up to and including data corruption or a system panic! This kernel patch need to work with the command patch PHCO_12922; please install PHCO_12922 with this patch. Installed alone, this kernel patch will not solve the fsck problem. --- If you are planning to install the advanced VxFS product (AdvJournalFS.VXFS-ADV-KRN), it is imperative that this patch, and all listed superseded patches, be removed from the system via swremove(1M) before the actual product installation. After the installation of the advanced VxFS product has completed, this patch can be re-installed. (It is not necessary to re-install superseded patches.) All patches listed in the Supersedes field are subject to this behavior and need to be removed before installing the advanced VxFS product. After running swremove(1M), use the swlist(1M) command to insure that none of the previous patches were restored during the removal process. If one was, remove it using swremove(1M). --- When this patch is installed the default environment size is 20478 bytes. To enable the system to use the larger environment size of 2048000 bytes, the following steps must be followed. 1. A new tunable called `large_ncargs_enabled' must be defined in the sytem file in the following manner large_ncargs_enabled 1 2. A new kernel must be built (using this system file) and the system rebooted. To return to the default environment size, the new tunable needs to be either removed from the system file, or its value set to zero. A new kernel should then be built (using the modified system file) and the machine rebooted. --- Due to the number of objects in this patch, the customization phase of the update may take more than 10 minutes. During that time the system will not appear to make forward progress, but it will actually be installing the objects.