PROBLEM: (CLD UTO101199,HPAQ30ETE,QAR 51485,52365) (Patch ID: OSF425-061) ******** This patch corrects a problem with an NFS V3 mounted AdvFS file system where under heavy I/O load, data being written to a file may be lost. Additionally, because file stats are not being saved, the file modification time may revert to a previous value. PROBLEM: (QAR 57918) (Patch ID: OSF425-135) ******** This patch provides a performance improvement for AdvFS systems. A read() system call from an AdvFS file for a length less than 16K whose starting offset within an 8K page falls such that the read() request crosses into the next page, currently requires two disk I/O operations if the file pages are not already cached in the UBC from prior read() or write() requests. This performance change to AdvFS will prefetch the second page with a concurrent disk I/O operation. This means the requesting thread will only be put to sleep for I/O one time while processing the read() system call. PROBLEM: (MCPM31DX7) (Patch ID: OSF425-157) ******** This patch fixes a problem that occurs on SMP systems with an AdvFS filesystem in which the system panics with the following message: simple_lock: time limit exceeded The problem occurs when the lock is taken by a thread that calls the msfs_unmount routine, as can be seen from lock structure in pmsgbuf: pc of caller: 0xfffffc00003d756c lock address: 0xfffffc00574e12f8 current lock state: 0x00000000003d6a49 (cpu=0,pc=0xfffffc00003d6a48,busy) The pc in "current lock state" was code executed by that thread. This code can be further defined by printing it in dbx: dbx>0xfffffc00003d6a48/i [msfs_unmount:2035] PROBLEM: (QAR 57938, QAR 50417) (Patch ID: OSF425-169 ) ******** This patch corrects a problem in AdvFS where a data structure field is not initialized until after an AdvFS mount which is too late. This results in the inability for example to see the files after a remount. An example of this problem would be the ls command not being able to list files on an AdvFS mounted filesystem that is NFS exported. PROBLEM: (UVO105368) (Patch ID: OSF425-180) ******** This patch fixes a problem where the vrestore program does not report failed exit status appropriately on incomplete or incorrect commands, corrupt or invalid saved sets, or file open failures. PROBLEM: (TKTRA2376) (Patch ID: OSF425-410118) ******** This patch fixes a problem with the vrestore command. When restoring a multi-volume tape archive, if the tapes that follow the first tape are write-protected, the following error message is displayed: vrestore: can't open device file PROBLEM: ( QAR 56531,56516,56530,56529) (Patch ID: OSF425-400437) ******** Commands vquota, vedquota will sometimes display the incorrect error message for non-english locales. PROBLEM: (QAR 54607,QAR 56125) (Patch ID: OSF425-400443) ******** This patch fixes a problem that occurs on AdvFS systems. The chfsets function returns incorrect exit values and inappropriate error messages. This problem occurs when an inactive domain is specified along with an explicit list of filesets. In this case, a successful exit code is returned, which is incorrect. If an inactive domain is specified without any filesets then it fails properly. PROBLEM: (QAR 57625,58959,58241) (Patch ID: OSF425-194) ******** This patch fixes an AdvFS problem that causes a lockmode 4 system panic. A sample stack trace is as follows: 0 boot() 1 panic() 2 thread_block() 3 thread_preempt() 4 boot() 5 panic() 6 lock_fault() 7 lock_read() 8 prom_getenv() 9 lk201_reset_keyboard() 10 wsputc() 11 sccputc() 12 cnputc() 13 cons_puts() 14 printf() 15 lock_fault() 16 lock_write() 17 fuser() 18 syscall() 19 _Xsyscall() PROBLEM: (QAR 58329,52954,56575,56330) (Patch ID: OSF425-197) ******** This patch fixes an AdvFS domain panic causing a system panic which has the following error message: SMP Assertion failed If a panic is not encountered, verify will show inconsistencies. Some sample stack traces are as follows: 1 panic() 2 hardclock() 3 _XentInt() 4 mntbusybuf() 5 boot() 6 panic() 7 advfs_sad() 8 tagdir_tag_to_freelist() 9 close_one_int() 10 close_int() 11 bs_vfs_close() 12 msfs_inactive() 13 vrele() 14 msfs_remove() 15 unlink() 16 syscall() 17 _Xsyscall() The following is partial stack trace: 7 panic() 8 advfs_sad() 9 tagdir_remove_tag() 10 bs_delete_rtdn_opx() 11 ftx_recovery_pass() 12 ftx_bfdmn_recovery() 13 bs_bfdmn_activate() 14 bs_bfdmn_tbl_activate() 15 bs_bfset_activate_int() 16 bs_bfset_activate() 17 advfs_mountfs() 18 msfs_mount() 19 local_mount() 20 mount1() 21 mount() 22 syscall() Running verify can result with the following information: Checking tag directories ... check_tagdir_page: bad allocated tag count set tag: -2.0 (0xfffffffe.0x00000000) tag: 1.32769 (0x00000001.0x00008001) tag directory page: 0 real count: 699, expected count: 680 check_tagdir_page: bad free tag count set tag: -2.0 (0xfffffffe.0x00000000) tag: 1.32769 (0x00000001.0x00008001) tag directory page: 0 real count: 322, expected count: 341 check_one_tagdir: bad free tag count set tag: -2.0 (0xfffffffe.0x00000000) tag: 1.32769 (0x00000001.0x00008001) real count: 1344, expected count: 1363 PROBLEM: (Patch ID: OSF425-205) ******** This patch fixes a problem in which vrestore can cause an occasional core dump (Floating Exception). PROBLEM: (HPAQ20W8R) (Patch ID: OSF425-207) ******** A system using an AdvFS clone fileset can panic with either a kernel memory fault in bs_real_invalidate_pages(), or with the panic string: "bs_real_invalidate_pages: buf refd or pinned". The kernel memory fault would have a faulting virtual address of 0x040, and a stack trace which goes through msfs_reclaim and bs_real_invalidate_pages. A typical stack trace would be: 5 panic(s = "kernel memory fault") 6 trap 7 _XentMM 8 bs_real_invalidate_pages 9 msfs_reclaim 10 vclean 11 vgone 12 vflush 13 msfs_unmount 14 dounmount 15 unmount 16 syscall 17 _Xsyscall The panic with the string "bs_real_invalidate_pages: buf refd or pinned" would also go through msfs_reclaim and bs_real_invalidate_pages. A typical stack trace would be: 5 panic(s = "bs_real_invalidate_pages: buf refd or pinned") 6 advfs_sad 7 bs_real_invalidate_pages 8 msfs_reclaim 9 vclean 10 vgone 11 getnewvnode 12 vdealloc 13 vrele 14 namei 15 unp_connect 16 uipc_usrreq 17 sosend 18 sendit 19 sendto 20 syscall 21 _Xsyscall PROBLEM: (MCGMC03FC,HPAQ11P4K,EVT102458,MGO103284,58879) (Patch ID: OSF425-215) ******** This patch fixes a problem that occurs on AdvFS file systems. A kernel memory fault occurs on the AdvFS file system when accessing nfs-mounted files. The error log contains the following information: trap: invalid memory read access from kernel mode faulting virtual address: 0x0000000000000050 pc of faulting instruction: 0xfffffc0000362224 ra contents at time of fault: 0xfffffc0000362218 sp contents at time of fault: 0xffffffffa9a73768 Possible stack: 15 _XentMM() 16 msfs_getattr() 17 rfs3_getattr() 18 rfs_dispatch() 19 nfs_rpc_recv() 20 nfs_rpc_input() 21 nfs_input() PROBLEM: (MCGM305VX) (Patch ID: OSF425-219) ******** This patch prevents a "kernel memory fault" in the sbm_init() routine on systems using AdvFS. The stack trace will look similar to the following: 0 boot 1 panic 2 trap 3 _XentMM 4 sbm_init 5 set_vd_mounted 6 bs_bfdmn_activate 7 bs_bfdmn_tbl_activate 8 bs_bfset_activate_int 9 bs_bfset_activate 10 advfs_mountfs 11 msfs_mount 12 mount1 13 mount 14 syscall 15 _Xsyscall PROBLEM: (EVT102509 GOZ100927) (Patch ID: OSF425-224) ******** This patch prevents a "kernel memory fault" in the msfs_reclaim() routine on systems using AdvFS. The stack trace will look similar to the following: 0 boot 1 panic(s = "kernel memory fault") 2 trap 3 _XentMM 4 msfs_reclaim 5 vclean 6 vgone 7 getnewvnode PROBLEM: (QAR 58822,59748) (Patch ID: OSF425-234) ******** This patch fixes an kernel memory fault panic. The system displays the following error message: trap: invalid memory read access from kernel mode The stack trace is as follows: 1 panic() 2 event_timeout() 3 xcpu_puts() 4 printf() 5 panic() 6 trap() 7 _XentMM() 8 bs_real_invalidate_pages() 9 bs_invalidate_rsvd_access_struct() 10 vd_remove() 11 bs_bfdmn_deactivate() 12 bs_bfset_activate_int() 13 bs_bfset_activate() 14 fs_fset_get_stats() 15 msfs_real_syscall() 16 msfs_syscall() 17 syscall() 18 _Xsyscall PROBLEM: (QAR 47047,51352) (Patch ID: OSF425-237) ******** This patch fixes a problem that occurs when the user attempts to fill an AdvFS: the system crashes and displays the following panic: lock_write: hierarchy violation The panic information would be similar to the following: lock_write: hierarchy violation pc of caller: 0xfffffc0000375ccc lock address: 0xfffffc00e7e73180 lock info addr: 0xfffffc000073c220 lock class name: domainT.scLock class already locked: vdT.mcell_lk current spl level: 0 panic (cpu 2): lock_write: hierarchy violation simple_lock: lock already owned by cpu pc of caller: 0xfffffc0000563e8c lock address: 0xfffffc00ffe2ac48 lock info addr: 0xfffffc000073d260 lock class name: cam_isp current lock state: 0xc400012600565025 (cpu=0,pc=0xfffffc0000565024,busy simple locks held PROBLEM: (QAR 52487,58963) (Patch ID: OSF425-241) ******** This patch fixes a problem caused by the vrestore command. The command would fail when restoring multiple savesets from a TZS20 tape drive. The vrestore command would fail when it attempted to restore the second saveset from the tape. The error message returned was: vrestore: unable to use save-set; invalid or corrupt format PROBLEM: (CLD SOO101109) (Patch ID: OSF425-251) ******** This patch fixes a problem that occurred when an AdvFS panic crashed the customer's system but the visible symptom was a crash due to a kernel memory fault. The kernel memory fault was caused by an internal conversion routine as it was attempting to format the string that reported the AdvFS panic. The following shows the crash footprint: dbx> p *pmsgbuf (also can use "pmsgbuf/100s") : : ADVFS EXCEPTION Module = ftx_routines.c, Line = 2879 trap: invalid memory read access from kernel mode faulting virtual address: 0xfffffffffffffbd8 pc of faulting instruction: 0xfffffc0000294bbc ra contents at time of fault: 0xfffffc0000293dec sp contents at time of fault: 0xffffffff" PROBLEM: (QARs57927,58380,57750) (Patch ID: OSF425-239) ******** This patch adds a feature to the AdvFS verify utility. The verify utility now detects and reports some filesystem corruption problems that were previously ignored. PROBLEM: (QAR 54322,57034) (Patch ID: OSF425-232) ******** This patch fixes a problem caused by the vdump command. When a user entered Ctrl/C to terminate a vdump operation, the command returned an incorrect status and mistakenly updated the /etc/vdumpdates file. PROBLEM: (QAR 58850,60147) (Patch ID: OSF425-238) ******** This patch fixes a problem in the defragment utility. Defragment is migrating more than 1 gigabyte of data at a time causing data to be lost and displaying the following message: log half full PROBLEM: (QAR 58740) (Patch ID: OSF425-244) ******** This patch fixes an AdvFS response time problem that occurred when an application with many random access reads of many files was being slowed down by the resulting number of writes to disk. To fix the problem, there are three new features: o atimes and noatimes options are added to the mount -o option list for AdvFS file systems o the read system call has additional code to perform the operation requested by the noatimes option o a configurable parameter, AdvfsPreallocAccess, for tuning the number of access structures in the freelist at startup The AdvFS mount option noatimes changes AdvFS behavior for regular files in the specified fileset. AdvFS updates the file access time in memory on a read system call from a regular file, but does not write the stat structure for the file with the new access time out to disk until some other file modification is made. After a file is closed (and when the fileset is unmounted), the in memory updated access time can be lost. Therefore, this mount noatimes option should not be used in conjunction with utilities or applications which gather statistics or make decisions based on file access times, such as migrating unaccessed files to slower backing storage. ******RELEASE NOTE INFORMATION ***** mount(8), in the AdvFS Options section of the mount -o Flag Options: atimes Flushes to disk the file access time changes for reads of regular files. This is the default XPG4 behavior. noatimes Marks file access time changes for reads of regular files in memory, but does not flush them to disk until other file modifications occur. This behavior does not comply with industry standards and is used to reduce disk writes for applications with no dependencies on file access times. read(2): [DIGITAL] If the file is a regular file and belongs to an AdvFS fileset mounted with the AdvFS option noatimes, the read, readv, or pread function marks the st_atime field of the file for update. If the file otherwise remains unchanged, the new st_atime value is not flushed to disk. See mount(8) for more information on the noatimes mount option. System Configuration and Tuning Guide Appendix B Section 1, "AdvFS Subsystem Attributes": AdvfsPreallocAccess AdvFS will allocate this number of access structures to the AdvFS access structure freelist at startup. The minimum value is 128, the maximum value is 65536. The actual value allocated at startup will be adjusted to honor the AdvfsAccessMaxPercent configurable. Default value: 128 On larger systems, a larger value than the default value of 128 may improve performance by slowing the rate of access structure recycling, allowing cached file metadata to stay in main storage. PROBLEM: (QAR 57426,QAR 57942) (Patch ID: OSF425-247) ******** This patch fixes a problem with the chfsets command. When a root user exceeded the fileset quota (which root is allowed to do), the chfsets command reported negative values for the free and available blocks in the fileset. PROBLEM: (QAR 60606, QAR 58912) (Patch ID: OSF425-257) ******** This patch fixes a problem with AdvFS in which the following panic occurs: clone: str_stripe_clone err A sample stack trace is as follows: 0 boot() 1 panic() 2 advfs_sad() 3 clone() 4 bs_cow() 5 bmtr_update_rec() 6 fs_update_stats() 7 msfs_close() 8 vn_close() 9 closef() 10 close() 11 syscall() 12 _Xsyscall() PROBLEM: (QAR 57158, QAR 60574) (Patch ID: OSF425-262) ******** This patch modifies the vd_remove() function to set domain panic instead of panicing the system. PROBLEM: (QAR 57163,QAR 56892) (Patch ID: OSF425-275) ******** This patch fixes a problem that crashed the system while it was running a "collision" test. A process would hang on a lock, never be woken, and crash the system. PROBLEM: (QAR 59968, QAR 57858) (Patch ID: OSF425-276) ******** This patch fixes an AdvFS problem that occurs when unmounting a domain. An unmount thread was waiting on a variable to be set to zero before continuing, but the routine that was to set the variable to zero never did. The stack trace is: 0 thread_block() 1 thread_sleep() 2 _cond_wait() 3 vd_free() 4 vd_remove() 5 bs_bfdmn_deactivate() 6 bs_bfset_deactivate() 7 msfs_unmount() 8 dounmount() 9 unmount(0xfffffc0000578af0, 0x16, 0xfffffc00006fbe00, 0xffffffff88b6c PROBLEM: (QAR 57450) (Patch ID: OSF425-281) ******** This patch fixes a problem with the AdvFS fs_write routine, which would mishandle partial writes after detecting an error. Now when the fs_write routine detects an error, it breaks out of the write page loop and decides either to exit immediately with an error (if no bytes have been written) or to commit the partial changes to disk and return the number of successfully-written bytes. PROBLEM: (QAR 61304, QAR 60584) (Patch ID: OSF425-292) ******** This patch corrects a problem where a panic would occur when running rmtrashcan on a clone. The panic would look like: panic (cpu 0): bmtr_put_rec error in detach_undel_dir N1 = -1114 PROBLEM: (QAR 61395, QAR 61336) (Patch ID: OSF425-301) ******** This patch fixes a problem with AdvFS, which caused a system panic with the following message: log_flush_sync: pingpg error The system panic occurred when the AdvFS domain had already issued a domain panic and a user application then attempted to close a file in that domain. The stack trace is listed below: 7 panic() 8 advfs_sad() 9 log_flush_sync() 10 lgr_writev_ftx() 11 log_donerec_nunpin() 12 ftx_done_urdr() 13 ftx_done_n() 14 msfs_close() 15 vn_close() 16 closef() 17 close() 18 syscall() 19 _Xsyscall() PROBLEM: (QAR 60151, QAR 61769) (Patch ID: OSF425-305) ******** This patch fixes a problem with AdvFS, which would corrupt a clone fileset when it truncated the original fileset. PROBLEM: (ECP EALC8003) (Patch ID: OSF425-315) ******** This patch provides performance improvements for writes to AdvFS files which have had Atomic Write Data Logging enabled on them. Write performance improvements are for O_SYNC opens of such files and are realized for both local and NFS access. PROBLEM: (QAR 55008,QAR 60308) (Patch ID: OSF425-321) ******** This patch fixes a problem in AdvFS that produced the following system panic: bs_logflush_start: cannot write lsn PROBLEM: (QAR 61553) (Patch ID: OSF425-327) ******** This patch fixes a problem with messages in system logs that reported AdvFS user and group quota limits. The messages were unclear: the user could not determine from them which users or groups were reaching the quota limits. Part of the problem was the term "inode," which is not an AdvFS entity. The term was replaced in the messages with "file." PROBLEM: (QAR 46502, QAR 52854, QAR 55893, QAR 59488, QAR 59854, QAR 61274) (Patch ID: OSF425-359) ******** This patch fixes several problems associated with AdvFS tag files and directories. Specific problems fixed in this patch are: 1. The tag file interface caused the vdf, showfile, and other commands to display erroneous data. 2. When a tag directory was opened, a vnode was assigned to an illegal mount point, causing an ENODEV error return or a system panic. 3. The routine that tested for referenced tag directories was incorrectly causing the system to panic with the following message: lock_write: lock already owned by thread and the following stack trace resulted: 8 panic() 9 lock_fault() 10 lock_write() 11 bf_get_l() 12 bf_get() 13 msfs_lookup() 14 namei() 15 _F64_stat1() 16 _F64_lstat() 17 syscall() 18 _Xsyscall() 4. When using the tags interface to access nonexisting reserved files, the system would panic with the following message: SMP Assertion failed and the following stack trace resulted: 1 panic() 2 advfs_sad() 3 imm_init_sub_xtnt_map() 4 load_from_xtnt_rec() 5 load_inmem_xtnt_map() 6 x_create_inmem_xtnt_map() 7 bs_map_bf() 8 rbf_access_one_int() 9 rbf_access_int() 10 rbf_vfs_access() 11 bf_get_l() 12 bf_get() 13 msfs_lookup() 14 namei() 15 _F64_stat1() 16 _F64_lstat() 17 syscall() 18 _Xsyscall() PROBLEM: (QAR 60129, QAR 62613) (Patch ID: OSF425-371) ******** This patch fixes a problem in AdvFS locking code which causes the following panic: kernel memory fault The stack trace is listed below: 0 boot() 1 panic() 2 trap() 3 _XentMM() 4 bs_pinpg_clone() 5 bs_pinpg_ftx() 6 rbf_pinpg() 7 alloc_mcell() 8 bmt_alloc_prim_mcell() 9 new_mcell() 10 rbf_int_create() 11 rbf_create() 12 fs_create_file() 13 msfs_mkdir() 14 mkdir() 15 syscall() 16 _Xsyscall() PROBLEM: (QAR 62673,QAR 61388) (Patch ID: OSF425-385) ******** This patch fixes a problem in AdvFS, which causes a system panic when a truncate operation is performed on a file. The panic is: log half full Here's the stack trace: > 0 boot() ["../../../../src/kernel/arch/alpha/machdep.c":1890, ] 1 panic(s = 0xffffffff8bc3af98 = "release_dirty_pg: log half full") ["../../../../src/kernel/bsd/sub r_prf.c":834, 0xfffffc000028c024] 2 advfs_sad() ["../../../../src/kernel/msfs/bs/bs_misc.c":556, ] 3 release_dirty_pg() ["../../../../src/kernel/msfs/bs/ms_logger.c":2005,] 4 lgr_writev_ftx() ["../../../../src/kernel/msfs/bs/ms_logger.c":1576, ] 5 log_donerec_nunpin() ["../../../../src/kernel/msfs/bs/ftx_routines.c":2825, ] 6 ftx_done_urdr() ["../../../../src/kernel/msfs/bs/ftx_routines.c":1246, ] 7 ftx_done_u() ["../../../../src/kernel/msfs/bs/ftx_routines.c":1060, ] 8 bmt_link_mcells() ["../../../../src/kernel/msfs/bs/bs_bmt_util.c":3770, ] 9 odm_create_xtnt_map() ["../../../../src/kernel/msfs/bs/bs_extents.c":1707, ] 10 dealloc_stg() ["../../../../src/kernel/msfs/bs/bs_stg.c":6388, ] 11 remove_stg() ["../../../../src/kernel/msfs/bs/bs_stg.c":5897, ] 12 stg_remove_stg_start() ["../../../../src/kernel/msfs/bs/bs_stg.c":5743, ] 13 bf_setup_truncation() ["../../../../src/kernel/msfs/bs/bs_access.c":4189, ] 14 msfs_setattr() ["../../../../src/kernel/msfs/osf/msfs_vnops.c":1725, ] 15 vtruncate() ["../../../../src/kernel/vfs/vfs_syscalls.c":3488, ] 16 ftruncate() ["../../../../src/kernel/vfs/vfs_syscalls.c":3418, ] 17 syscall() ["../../../../src/kernel/arch/alpha/syscall_trap.c":627, ] 18 _Xsyscall() ["../../../../src/kernel/arch/alpha/locore.s":1409, ] End Trace for machine_slot[paniccpu].cpu_panic_thread: PROBLEM: (QAR 63522) (Patch ID: OSF425-395) ******** This patch fixes a problem in AdvFS that was causing a memory leak. An internal routine was not always deallocating buffers that were returned to it. PROBLEM: (QAR 62299, QAR 51568, QAR 62617, HPAQ60W1F, QAR 63703, QAR 63686) (Patch ID: OSF425-401) ******** This patch fixes the following problems in AdvFS: 1.) AdvFS does not return an error when a user opens a file in O_SYNC mode and power is lost on the disk drive. 2.) A locking error in the AdvFS fs_write() routine. PROBLEM: (QAR 61275, QAR 61777) (Patch ID: OSF425-404) ******** This patch fixes a problem with AdvFS that caused a page fault and the following panic: panic (cpu 0): kernel memory fault A stack trace would be similar to the following: 0 boot() 1 panic() 2 trap() 3 _XentMM() 4 bs_logpage_dirty() 5 lgr_read() 6 ftx_fail_2() 7 ftx_fail() 8 stg_add_stg_no_cow() 9 stg_add_stg() 10 rbf_add_overlapping_stg() 11 fs_write_add_stg() 12 fs_write() 13 msfs_write() 14 vn_write() 15 rwuio() 16 write() 17 syscall() 18 _Xsyscall() PROBLEM: (QAR 62114,QAR 58469 , QAR 62503,QAR 49186) (Patch ID: OSF425-406) ******** This patch fixes two AdvFS problems: 1. An error message was misleading when a DIGITAL UNIX Version 4 system attempted to access a file domain created by DIGITAL UNIX Version 5. 2. A state field in an AdvFS data structure was initialized, but not maintained. PROBLEM: (QAR 63937, QAR 64709) (Patch ID: OSF425-437) ******** This patch fixes a problem where user files or the AdvFS frag file could lose data, if they are updated during an AdvFS migration (that is, during a balance, defragment, migrate, or rmvol of their AdvFS domain). PROBLEM: (QAR 54246,QAR 57344) (Patch ID: OSF425-279) ******** This patch fixes a problem with the vrestore command. The command had returned a success status code even though it had restored an incomplete file during the operation. PROBLEM: (QAR 57304,QAR 50820,QAR 57898,QAR 59077) (Patch ID: OSF425-370) ******** This patch fixes three verify command problems: 1. The command was displaying a large volume of meaningless data. [A -q flag and message suppression was added to the utility.] 2. When it encountered a nonrecoverable error, the command did not properly exit. [The nonrecoverable error returns were improved.] 3. The command sent some error messages to stderr, some to stdout. [Error messages are directed to stderr.] PROBLEM: (QAR 59953, QAR 59419) (Patch ID: OSF425-249) ******** This patch fixes a problem that occurs on AdvFS systems. The system will panic with the following error message: malloc_overflow: guard space corruption A sample stack trace is as follows: 6 panic() 7 malloc_debug() 8 free() 9 _ms_free() 10 free_dmntbl_setname() 11 msfs_real_syscall() 12 msfs_syscall() 13 syscall() 14 _Xsyscall() PROBLEM: (QAR 61224) (Patch ID: OSF425-296) ******** This patch fixes a problem with AdvFS, which produced the following error while attempting to migrate a sparse file: E_CANT_MIGRATE_HOLE The AdvFS migration code can now migrate a hole to the volume that contains the first real extent following the hole. PROBLEM: (QAR 60888, QAR 61768, QAR 58064) (Patch ID: OSF425-320) ******** This patch fixes the following problems in the AdvFS system: o The log file corruption caused panics during recovery and failures and display one of the following messages: ftx_fail: lgr_read failure -or- ftx_fail: dirty page not allowed Sample stack trace is listed below: 28 panic() 29 advfs_sad() 30 ftx_fail_2() 31 ftx_fail() 32 fs_create_file() 6 advfs_sad() 7 _ms_free() 8 ftx_fail_2() 9 ftx_recovery_pass() o kernel memory fault Sample stack trace is listed below: 0 boot() 1 panic() 2 trap() 3 _XentMM() 4 add_cache() 5 load_x_cache() 6 sbm_find_space() 7 alloc_from_bitmap() 8 alloc_from_one_disk() 9 stg_alloc_from_one_disk() 10 stg_alloc_from_svc_class() 11 alloc_append_stg() 12 alloc_stg() 13 add_stg() 14 stg_add_stg_no_cow() 15 stg_add_stg() 16 rbf_add_overlapping_stg() 17 fs_write_add_stg() 18 fs_write() 19 msfs_write() 20 vn_write() 21 rwuio() 22 write() 23 syscall() 24 _Xsyscall() o The error message: "can't set a bit twice". Sample stack trace is listed below: 0 panic("alloc_bits_page: can't set a bit twice!") 1 advfs_sad() 2 CANT_SET_TWICE() 3 sbm_set_pg_bits() 4 init_sbm() o The error message: "can't clear a bit twice". Sample stack trace is listed below: 0 panic(ADVFS INTERNAL ERROR: dealloc_bits_page: can't clear a bit twice!\n") 1 advfs_sad() 2 CANT_CLEAR_TWICE() 3 dealloc_bits_page() PROBLEM: (QAR 60725) (Patch ID: OSF425-360) ******** This patch fixes a problem in the AdvFS logging code. The way locking was implemented was causing degraded performance. PROBLEM: (BCSM51Q5C) (Patch ID: OSF425-418) ******** This patch corrects an I/O subsystem performance bottleneck. A system which experiences periodic system slowdowns may need this patch. PROBLEM: (UVO106018, QAR 61185) (Patch ID: OSF425-362) ******** This patch fixes a operating system hang condition. The hang condition exists due to processes deadlocking in the Advfs code. PROBLEM: (QAR 61441) (Patch ID: OSF425-410) ******** This patch fixes a problem with AdvFS performance. The patch provides a performance improvement to the msync system call when it is called for an AdvFS mmapped file. AdvFS msync processing is changed to only flush file dirty pages in the mmapped address range passed to the msync system call. Prior to this change, AdvFS would flush all dirty pages for the file. PROBLEM: (QAR 60922, QAR 55002, QAR 46115) (Patch ID: OSF425-278) ******** This patch fixes an AdvFS problem that occurs when the rmvol command is stopped before the commmand successfully removes a volume from a domain. As a result, the showfdmn and addvol commands interpreted the volume as still in the domain (although with no data available) and a balance operation returned the following AdvFS error message: get vol params error EBAD_VDI (-1030) PROBLEM: (QAR 64168, QAR 61092) (Patch ID: OSF425-429) ******** This patch fixes a problem with the defragment command, where the -V option is not being parsed properly. PROBLEM: (QAR 60371) (Patch ID: OSF425-430) ******** This patch fixes a problem in AdvFS that produced the following system panic: malloc_overflow: guard space corruption The panic will only occur when the kernel memory debugging option, kmem_debug, has its KMEM_DEBUG_OVERFLOW bit set. The panic occurs because AdvFS may not allocate enough memory to hold the domain and fileset names if the combined length of the domain name and fileset name given to the mount command totals 60 bytes or more. A typical stack trace would be: panic("malloc_overflow: guard space corruption") src/kernel/bsd/subr_prf.c : 791 malloc_overflow src/kernel/bsd/kern_malloc.c : 3002 malloc_debug src/kernel/bsd/kern_malloc.c : 2897 free src/kernel/bsd/kern_malloc.c : 1510 _ms_free src/kernel/msfs/bs/ms_mode.c : 220 advfs_mountfs src/kernel/msfs/osf/msfs_vfsops.c : 1432 msfs_mount src/kernel/msfs/osf/msfs_vfsops.c : 1312 mount1 src/kernel/vfs/vfs_syscalls.c : 1024 mount src/kernel/vfs/vfs_syscalls.c : 771 syscall src/kernel/arch/alpha/syscall_trap.c : 556 _Xsyscall src/kernel/arch/alpha/locore.s : 1177 PROBLEM: (QAR 60886) (Patch ID: OSF425-436) ******** This patch fixes a problem with the vdump command, which was modifying the atime file attribute whenever files were backed up, thereby eliminating the ability to determine when the files were last accessed by a user. The change was actually made to the fcntl system call, which now provides the correct atime attribute values. PROBLEM: (QAR 64441) (Patch ID: OSF425-450) ******** This patch enhances the AdvFS verify utility to detect incorrect "holes" in frags file. PROBLEM: (QAR 57532) (Patch ID: OSF425-451) ******** Threads which perform asyncronous I/O modify the state of the associated buffer after the request gets enqueued onto the lazy queue. If the lazy queue gets bypassed, then it is possible for the I/O to complete before the issuing thread modifies the buffer. Once the I/O completes, the buffer could be reassigned. The issuing thread still attempts to modify the buffer state, leading to an inconsistency and possibly a panic. PROBLEM: (QAR 62761, QAR 63890, QAR 56860) (Patch ID: OSF425-453) ******** This patch fixes a problem in the AdvFS system. The system hangs due to a deadlock between update daemon sync() syscall processing in AdvFS and the truncation of AdvFS file. The stack trace for update daemon hangs with: 0 thread_block() 1 lock_read() 2 msfs_putpage() 3 ubc_flush_dirty() 4 msfs_sync() 5 sync() 6 syscall() 7 7 _Xsyscall() The stack trace for the deadlocking with the update daemon is: 0 thread_block() 1 ubc_invalidate() 2 bs_real_invalidate_pages() 3 stg_remove_stg_start() 4 bf_setup_truncation() 5 msfs_setattr() 6 vn_open_ftrunc() 7 vn_open() 8 copen() 9 open() 10 syscall() 11 _Xsyscall() PROBLEM: (QAR 65404 QAR 61571 BCSM40F2Q) (Patch ID: OSF425-454) ******** If vrestore is being run from a script and a control C is typed in order to abort vrestore, vrestore continues to run. PROBLEM: (QAR 63709, EVT102691) (Patch ID: OSF425-459) ******** This patch changes the way some of the ADVFS advanced utilities (rmvol, migrate, balance and defragment) work internally. Under heavy I/O, the utilities could fail to migrate some files from one volume in an ADVFS domain to another. The errors for the customer seeing this problem will be similar to the following: balance: Balancing domain 'test_domain' balance: Can't move file /test/test.file balance: Error = E_INVOLUNTARY_ABORT (-1185) balance: Balanced domain 'test_domain' PROBLEM: (QAR 60578) (Patch ID: OSF425-461) ******** This patch corrects a problem observed when using the edquota command under the Advanced File System (AdvFS). The edquota command may display an incorrect grace period. The default grace period is a special case where the default of "0" is interpreted to mean "7 days." This was not being handled correctly by the edquota command functions, which incorrectly displayed "0" instead of the correct period of 7 days. PROBLEM: (QAR 64393, 65683) (Patch ID: OSF425-462) ******** This patch fixes a problem whereby rmvol(8) did not correctly handle files that have more than one stripe on a volume and incorrectly assumed that there was only one stripe per volume. Informational messages similar to the following may be seen when running rmvol: rmvol: Striped file will be suboptimal. The rmvol utility may also fail with error messages similar to the following: rmvol: Error = EBAD_VDI (-1030) rmvol: Can't move file rmvol: Can't remove volume '' from domain '' PROBLEM: (HPAQ60H3T,HPAQ70WKD) (Patch ID: OSF425-470) ******** This patch fixes the following problems with the vrestore command: - vrestore is slow to complete when a partial restore operation is requested. - vrestore fails to ignore extended attribute records for those files that are not requested in a vrestore operation. PROBLEM: (QAR 63409) (Patch ID: OSF425-473) ******** This patch fixes two AdvFS problems: 1) When an AdvFS volume is nearly full, AdvFS files may become corrupt as they are closed. The verify utility can be used to detect this "overlapped frag corruption" problem. 2) The truncation of the fragment bitfile was erroneously being turned off. This feature allows AdvFS to give back disk space periodically. PROBLEM: (QAR 64808, QAR 65442) (Patch ID: OSF425-479) ******** This patch fixes a panic in the AdvFS system. The panic has the following error message: lock_read: hierarchy violation The stack trace follows: 5 panic() 6 lock_fault() 7 lock_read() 8 u_map_fault() 9 vm_fault() 10 trap() 11 _XentMM() 12 nofault_bcopy() PROBLEM: (QAR 65739, 64945) (Patch ID: OSF425-481) ******** QAR 65739: The system can hang when inactivating an AdvFS domain. A domain is inactivated when the last fileset in the domain is unmounted or when a command like showfset is issued and no filesets in the domain are mounted. Inactivating a domain inactivates each volume in the domain. The fix allows more I/O to be started even though the volume is being inactivated. QAR 64945: Under some unusual circumstances (for example, mis administration or some ASE failovers), some volumes in a domain will not be specified in /etc/fdmns/. When this happens, activating the domain will change the state of the volumes specified in /etc/fdmns but not on other volumes that should belong to the domain. When the links in /etc/fdmns are restored, the domain will not be mountable because the volume states do not match. The fix prevents the state of the volumes from being changed unless all volumes in the domain conform to a prescribed set of requirements. PROBLEM: (QAR 66511) (Patch ID: OSF425-493) ******** The source code for the vdump command was mistakenly changed to include time structures supported only by a future release of the system. This fix removes that change. PROBLEM: (QAR 58502,QAR 59094,QAR 61399,QAR 67023) (Patch ID: OSF425-498) ******** This patch provides the following fixes and enhancements to AdvFS: - AdvFS volumes were not setting the default I/O byte transfer size to the preferred size reported by the disk drives. This caused I/O consolidations to be smaller than is optimal for the disks. This patch now assigns the driver's preferred I/O transfer byte size to all new AdvFS volumes created with mkfdmn and addvol. - AdvFS chvol read and write transfer size range was increased. With this patch the transfer size range is now between 16 and 3276 512-byte blocks. - The read-ahead algorithm was modified to improve performance under certain conditions. The algorithm now sanity checks the number of pages that it would attempt to prefetch and apply the following restrictions when doing its calculations: - only read-ahead the number of pages remaining in the file - use a predetermined percentage of the buffer pool for use as read-ahead buffers. PROBLEM: (QAR 62648,QAR 62577) (Patch ID: OSF425-504) ******** This enhancement for the /sbin/advfs/verify utility allows it to detect loops in the list of free frags kept in the frags file. PROBLEM: (MGO103758, DJOB91545, SOO101204) (Patch ID: OSF425-513) ******** This patch fixes a problem where a system can panic with a kernel memory fault in overlay_xtnt_map() when any of the AdvFS migration utilities (migrate,balance, rmvol, or defragment) are run on an AdvFS domain. A typical stack trace looks like: _XentMM overlay_xtnt_map switch_stg migrate_normal mig_migrate bs_migrate msfs_real_syscall msfs_syscall PROBLEM: (QAR 67000, QAR 67281) (Patch ID: OSF425-514) ******** This patch fixes a problem in which a system using AdvFS can Kernel Memory Fault when truncating a frag file for a fileset that is not mounted. A typical stack trace would include: panic trap _XentMM lock_write bs_fragbf_thread PROBLEM: (QAR 60215) (Patch ID: OSF425-516) ******** Make vrestore work with QIC-120 and QIC-150 tapes PROBLEM: (BCSM91B1D, BCSM91NTC, QAR 66901) (Patch ID: OSF425-519) ******** This patch fixes an AdvFS hang that is caused by a deadlock between the_XentMM() and msfs_mmap() system calls. Some sample stack traces are the following: Stack trace 1: --------------- 0 thread_block() 1 u_map_entry_grow() 2 u_map_enter() 3 u_vp_create() 4 msfs_mmap() 5 smmap() 6 syscall() 7 _Xsyscall() Stack trace 2: -------------- 0 thread_block() 2 msfs_mmap() 3 smmap() 4 syscall() 5 _Xsyscall() PROBLEM: (QAR 67785, QAR 67460, CLDS MGO103947,BCSMC0NRQ, HPAQC0W3M, HPAQ10S59) (Patch ID: OSF425-538) ******** This patch fixes a problem in which a system can hang because cleanup_closed_list() can go into a loop. PROBLEM: (QAR 66683) (Patch ID: OSF425-539) ******** DECthreads was not properly changing the priority of a suspended thread, adversely effecting Java programs. The routine pthread_setschedparam() was not properly handling threads that are suspended. PROBLEM: (QAR 66254) (Patch ID: OSF425-539) ******** The routines, pthread_mutex_trylock() and tis_mutex_trylock(), as coded in the libpthread and libc, respectively, can cause uncontested lock operations to take the "slow path" when they would not have to otherwise. This shows a significant performance problem for the malloc mutex under heavy load. PROBLEM: (QAR 60355) (Patch ID: OSF425-539) ******** A bug in DECthreads affected the preemption of realtime SCS threads. In once instance a low priority SCS thread would run before a higher priority SCS threads. Another problem occurred when one SCS thread joined with another SCS thread, by calling the pthread_join() function before the "target" SCS thread had terminated. In that situation, the joiner thread may never be unblocked from the wait. PROBLEM: (CLD HPAQ81B6C) (Patch ID: OSF425-539) ******** Multithreaded applications can experience performance problems if they are run on multi-cpu systems and make heavy use of any of the functions on the malloc(3) manpage. This includes C++ applications making heavy use of "new" and "delete". The primary fix for this problem exists within libc, however DECthreads contained inefficiencies in the mutex logic code which made the problem worse. PROBLEM: (XIP100014, XIO100017) (Patch ID: OSF425-540) ******** This patch fixes a problem on systems using the AdvFS filesystem, where the system can panic with the panic string: "del_clean_mcell_list: no primary xtnt record". The stack trace will be similar to: advfs_sad del_clean_mcell_list bs_bfdmn_activate bs_bfdmn_tbl_activate fs_fset_get_info msfs_real_syscall msfs_syscall syscall _Xsyscall PROBLEM: (QAR 54840, QAR 60476, QAR 58938) (Patch ID: OSF425-547) ******** This patch fixes a problem in AdvFS where a complex lock in the ddl_wait_for_active_entry() routine would cause the thread to hang and possibly blocking other threads. If the system is set with lockmode = 4, a system panic would occur. PROBLEM: (QAR 65927 QAR 68369 CLD BCPMB0JP3) (Patch ID: OSF425-555) ******** Due to a problem with truncation during multiplication of 2 integers, the wrong offset was being calculated. This caused the update daemon to hang. PROBLEM: (HPAQC0B99) (Patch ID: OSF425-559) ******** This patch fixes a problem in AdvFS with auditing enabled. During a rmvol operation, the system can panic with a "kernel memory fault" with a stack trace that is similar to the following: > 0 boot() 1 panic(s = 0xfffffc00005b60a8 = "kernel memory fault") 2 trap() 3 _XentMM() 4 audit_rec_build() 5 audit_call() 6 msfs_audit_syscall() 7 msfs_real_syscall() 8 msfs_syscall() 9 syscall() 10 _Xsyscall() PROBLEM: (MGO103845, MGO103895) (Patch ID: OSF425-576) ******** This patch fixes an AdvFS Domain Panic that occurs with the following message on the console: "load_x_cache: bad status from bs_refpg of sbm" Example stack traces are as follows. Note: These are obtained from a system panic and not from the domain panic itself. 5 panic 6 advfs_sad 7 load_x_cache 8 sbm_find_space 9 alloc_from_bitmap 10 alloc_from_one_disk 11 stg_alloc_from_one_disk 12 alloc_copy_stg 13 migrate_normal 14 mig_migrate 15 bs_migrate 16 msfs_real_syscall 17 msfs_syscall 18 syscall 19 _Xsyscall OR 5 panic 6 advfs_sad 7 log_flush_sync 8 lgr_writev_ftx 9 log_donerec_nunpin 10 ftx_done_urdr 11 ftx_done_n 12 quota_deactivate 13 msfs_unmount 14 dounmount 15 unmount 16 syscall 17 _Xsyscall PROBLEM: (BCPM117VX) (Patch ID: OSF425-597) ******** This patch fixes a problem where the "statfs" system call was reporting incorrect block usage on AdvFS filesets. As a side effect of this problem, the sendmail utility may sleep needlessly (waiting for space to become available). PROBLEM (QAR 64688) (Patch ID: OSF425-537) This patch fixes kernel memory fault system panic in routine spec_relcaim. A sample stack trace is as follows: 0 stop_secondary_cpu() 1 panic() 2 event_timeout() 3 xcpu_puts() 4 printf() 5 panic() 6 trap() 7 _XentMM() 8 spec_reclaim() 9 vgone() PROBLEM (QAR 66544) (Patch ID: OSF425-537) This patch fixes a problem with executing the "file" command against a lat (BSD) special device in which the "file" process will hang. The system needs to be rebooted in order to remove the hung process. PROBLEM (QAR 67757) (Patch ID: OSF425-537) This patch fixes a problem on multiCPU systems where hangs can occur in the revoke system call when multiple threads attempt to call "revoke" at the same time. A sample stack trace is as follows: 0 thread_block() 1 clearalias() 2 revoke() 3 syscall() 4 _Xsyscall() PROBLEM: (BCGM703PQ,BCPM70WFJ,HPAQ920JJ,BCGMC0NZ8,HPAQA225S,BCGM210JL, HPAQ20Z8V) (Patch ID: OSF425-586) ******** This patch fixes a problem where several processes accessing the same AdvFS file can hang with the following stack trace: thread_block ubc_lookup page_lookup bs_refpg_int bs_refpg fs_read msfs_read vn_read rwuio read syscall _Xsyscall PROBLEM: (QAR 62615,QAR 59463) (Patch ID: OSF425-354) ******** This patch fixes a problem with the showfile command, which incorrectly returned an error status when it attempted to display a file that was a symbolic link. This patch fixes a problem sith an unclear AdvFS message. When trying to mount an AdvFS fileset on a system that did not have AdvFS installed, the following message was displayed: No such device Now, in similar cases, the following AdvFS message is displayed: Cannot mount AdvFS fileset, AdvFS not installed PROBLEM: (QAR 60168) (Patch ID: OSF425-405408) ******** This patch fixes a problem with AdvFS and links in the /etc/fdmns directory. Previously, AdvFS did not ensure that every link in a directory entry pointed to block device. Now it does. PROBLEM: (QAR 62614) (Patch ID: OSF425-447) ******** This patch fixes a problem with the mount command where it sometimes kills other processes. This randomly occurs if the file where mountd stores its pid, /var/run/mountd.pid, is out-of-date. PROBLEM: (UVO106367) (Patch ID: OSF425-625) ******** This patch fixes a problem where the vdump program would dump core with the following message: "nnnn Resources lost(coredump)" The program aborted with the following stack: 0 __pthread_mutex_destroy() 1 cma_mutex_delete() 2 pthread_mutex_destroy() 3 main() PROBLEM: (MGO104093,MGO104098,DSAT31W43) (Patch ID: OSF425-632) ******** This patch corrects a problem in AdvFS which causes single-CPU systems to hang and causes multiple-CPU systems to panic with a "simple lock time limit exceeded" message specifying lock class name BfAccessTblMutex. This problem was originally reported when sys_check was being used to report on systems where there are more than 256 AdvFS filesets. The same problem could occur with any form of file access with that many filesets. Kernel Rebuild required. PROBLEM: (QAR 65862) (Patch ID: OSF425-640) ******** This patch corrects a problem that caused invalid fragment information to be reported for an AdvFS file. The invalid information was returned in response to a verify command. PROBLEM: (QAR 66397) (Patch ID: OSF425-644) ******** This patch fixes a problem that caused the system to hang when AdvFS tests were run in lockmode 4. The fix allows xfer_xtnts_to_clone to recover after a crash. PROBLEM: (QAR 65628, 65698) (Patch ID: OSF425-645) ******** This patch fixes a problem with the AdvFS addvol command. Prior to this patch, if the advol command was interrupted and a second addvol command was run, the AdvFS domain would be rendered unusable. PROBLEM: (QARS 51397 58069 59749) (Patch ID: OSF425-647) ******** This patch fixes a problem in which system panics due to advfs lock hierarchy violation. PROBLEM: (QARS 67054 66241) (Patch ID: OSF425-649) ******** This patch fixes a problem with the defragment command. Prior to this patch the defragment command could fail and display inacurate error descriptions. The problem was caused by uninitialized variables for the command. PROBLEM: (QAR 70283) (Patch ID: OSF425-689) ******** This patch fixes the problem where the system panics if AdvFS detects an inconsistency in the free list of mcells that is kept on a per-volume basis in an AdvFS domain. The panic string seen with this panic is "alloc_mcell: bad mcell free list". PROBLEM: (UVO106494) (Patch ID: OSF425-701) ******** This patch fixes a problem where "update" takes too long to sync mmap files when using an AdvFS file system. PROBLEM: (QAR 65106) (Patch ID: OSF425-704) ******** This patch fixes the potential directory corruption,when system crashes during rmdir. PROBLEM: (QAR 66264) (Patch ID: OSF425-713) ******** This patch fixes the problem where the system panics whenever nextFlushSeq reaches the max.This fix allows nextFlushSeq (and other buffer lsn's) to roll over. PROBLEM: (CLD ALC-08618, QAR 69288) (Patch ID: OSF425-715) ******** This patch corrects a problem where a "can't clear a bit twice" panic occurs after an unanticipated system crash and an improperly handled AdvFS recovery operation. Note: Although the system will have paniced with a "can't clear a bit twice" panic message, the AdvFS file domain is often still good. On the following reboot the system will not mount the affected AdvFS domain complaining that the domain is in an "inconsistent state". To recover the domain, use dbx to set the variable AdvfsFixUpSBM to 1: dbx dbx>a AdvfsFixUpSBM = 1 dbx>quit Then use the AdvFS verify utility to check the domain. If the recovery is successful, verify will report no errors and the domain will be mountable. Please remember to set AdvfsFixUpSBM back to zero when you have finished recovering the domain. PROBLEM: (QARS 70619 68822 72776 72391) (Patch ID: OSF425-720) ******** This patch fixes the following two problems in AdvFS: - When a "log half full" or "log full" problem occurs, an entire system will panic. With this patch, only the AdvFS domain will panic instead of bringing down the entire system. - The erorr message "ftx_bfdmn_recovery:bad record size\n N1 = 1" is received when the wordCnt, as returned by lgr_read, is not enough to hold the ftxDoneLRT record that preceeds each log record in a log page. This caused the log page trailer to overwrite the ftxDoneLRT record in a log record. This patch now leaves enough room to write a log header at the end of a log page. PROBLEM: (KAOQ22635, STLQ32088) (Patch ID: OSF425-729) ******** This patch fixes a problem where vdump will output the message, "can't reset atime" for each file it is backing up when used with an NFS mounted file system. PROBLEM: (MGO103900) (Patch ID: OSF425-630) ******** This patch corrects a problem in AdvFS where unmounting a domain that is already in a panicked state could result in the following system panic message: log_flush_sync: pinpg error\n N1 = 5 Note: In this instance an I/O error (EIO = 5) caused the original domain panic. Stack trace: 6 advfs_sad() 7 log_flush_sync() 8 lgr_writev_ftx() 9 log_donerec_nunpin() 10 ftx_done_urdr() 11 ftx_done_n() 12 quota_deactivate() 13 msfs_unmount() Kernel Rebuild required. PROBLEM: (QARS 61528 61453 61531 61552) (Patch ID: OSF425-654) ******** This patch fixes problems in the AdvFS verify command as follows: Changes to error messages given when the AdvFS utility verify(8) detects mcells that are marked as belonging to a file, but not linked into its mcell chains. The new message warns of metadata corruption as follows: Metadata corruption in the BMT of disk 3: found mcell labelled as belonging.... The patch also corrects a problem whereby "verify -d" was unable to delete files with no directory entries. PROBLEM: (QAR 61627) (Patch ID: OSF425-686) ******** This patch ensures all AdvFS root fileset buffers are flushed on shutdown. Fixed 'simple lock held' error on shutdown with AdvFS root and lockmode = 4. PROBLEM: (BCPM2048V) (Patch ID: OSF425-631) ******** This patch fixes the defragment program to properly report on extremely large (>4.3GB) freespace holes. Previously it would report "Free space" percentages larger than 100% and would add these large holes to the smallest range (<100K) instead of the largest range (>10M) where they belong. PROBLEM: (CFS.67765) (Patch ID: OSF425-669) ******** This patch corrects a kernel memory fault that occurs when entering the "mount -o dual" command. 9 _XentMM() 10 bs_bfdmn_sweep() 11 bs_bfdmn_activate() 12 bs_bfdmn_tbl_activate() 13 bs_bfset_activate_int() 14 bs_bfset_activate() 15 advfs_mountfs() PROBLEM: (QAR 71271, QAR 71674) (Patch ID: OSF425-747) ******** This patch fixes a problem in AdvFS. AdvFS may skip filesystem recovery after aborted domain activation. PROBLEM: (QAR 67315, QAR 66478) (Patch ID: OSF425-753) ******** This patch fixes a problem in AdvFS. The system panics with the following error message: SMP Assertion failed A sample stack trace is listed below: 11 panic() 12 advfs_sad() 13 access_invalidate() 14 bfs_invalidate() 15 bfs_dealloc() PROBLEM: (QARS 67026 67442) (Patch ID: OSF425-760) ******** This patch fixes a problem in which it prevents a system panic if str_stripe_clone returns an error. PROBLEM: (HPAQ60H3T,HPAQ70WKD, QAR 72177) (Patch ID: OSF425-768) ******** This patch fixes two problems with the vrestore command. First, the command was slow to complete when a partial restore operation was requested. Second, the command failed to ignore extended attribute records for the files which were not requested for a vrestore operation. In addition this patch corrects intermittent failures to display archive records for the above files (compressed or not) when the list option was selected. PROBLEM: (QAR 67989, QAR 71541) (Patch ID: OSF425-769) ******** This patch prevents the corruption of the file system when the verify command is invoked with the '-r' and '-f' flags on an active domain. Now, when the user specifies the -r flag with either the -f or the -d flag, the command returns a usage message. PROBLEM: (QARS 60046 61355 64219 65937 71015) (Patch ID: OSF425-786) ******** This patch fixes following problems with the /sbin/vdump command: o Non-zero level dumps on links that point to a mounted file system can now be performed. o To prevent danglinkg links after a vrestore, directory entries are now created instead of re-creating links that points to a mount file system. o vdump no longer ignores valid nfs mounts with inodes = 5 or 4. PROBLEM: (QAR 74075) ******** This patch fixes a problem that may cause panics to occur when msfs_getpage() receives an error return from fs_write_add_stg() when attempting to write to an AdvFS domain that is out of disk space. PROBLEM: (QAR 74052, QAR 73883) (Patch ID: OSF425-796) ******** This patch fixes a problem in AdvFS. A fileset is busy when attempting to unmount giving an EBUSY error even though the fileset has no open files. PROBLEM: (CLS HPAQ11GRF, QAR 74870) (Patch ID: OSF425-808) ******** This patch fixes problem with vrestore where vrestore fails to restore certain files and directories having ACLs from a compressed vdump saveset, reporting: vrestore: error setting extended attributes 22 PROBLEM: (QAR 73692) (Patch ID: OSF425-823) ******** This patch fixes a problem in the AdvFS system. A panic occurs with the following error message: lock_read: hierarchy violation PROBLEM: (QAR 59006, QAR 55188 QAR 65875) (Patch ID: OSF425-825) ******** The patch fixes a problem with the AdvFS system. A panic occurs with the following error message: lock_read: hierarchy violation A sample stack trace is: lock_read: hierarchy violation pc of caller: 0xfffffc00003815e4 lock address: 0xfffffc000084ea10 lock info addr: 0xfffffc0000a0c180 lock class name: BfsDeleteLock class already locked: vm_umap.vm_lock current spl level: 0 PROBLEM: (QAR 75161) (Patch ID: OSF425-832) ******** This patch fixes a situation in which a domain that is being recovered can cause a slight Advfs memory leak. The problem can possibly result in a system panic whenever a domain is recovered via the mount command. The panic is due to a memory corruption. PROBLEM: (DJOB71733) (Patch ID: OSF425-850) ******** This patch fixes a problem where a single cpu system using AdvFS can hang in cleanup_closed_list(). PROBLEM: (MGO67225A,TKTBA0006,BCSMA1GK5,EVT79308A,STLBB3923) (Patch ID: OSF425-851) ******** This patch corrects AdvFS problems involving clone filesets. The statfs syscall (used by df) was incorrectly returning zero blocks USED for clones. The read-ahead code was incorrectly passing up opportunities to do read-ahead on clone filesets, resulting in a large performance penalty. PROBLEM: (MGO05514A) (Patch ID: OSF425-692) ******** This patch corrects two problems in AdvFS property list handling: 1) Creation of property lists entries in AdvFS filesets with no available mcells will result in kernel memory fault (kmf). Abbreviated stack: 17 _XentMM() 18 msfs_pl_pin_cur() 19 msfs_pl_create_rec() 20 msfs_pl_findhead_setdata() 21 msfs_pl_set_entry() 22 msfs_setproplist_int() 23 msfs_setproplist() 24 setproplist() 25 proplist_syscall() 26 syscall() 27 _Xsyscall() 2) The get_proplist_entry function (used to disassemble the property list buffer returned by the "getproplist" system call) returned incorrect name length on property list names longer than 127 characters. PROBLEM: (QAR 73764, QAR 59328) (Patch ID: OSF425-750) ******** This patch fixes a problem with the parameter checking code of the fcntl system call. As a result, incorrectly coded fcntl() parameters in user programs no longer panic the system. PROBLEM: (QAR 67156,QAR 61985,QAR 66890) (Patch ID: OSF425-775) ******** This patch fixes the AdvFS race between extending and reading subextent maps and avoids the panic occured in advfs bs_get_bf_xtnt_map code (qar 61985). This patch also fixes the race with removing storage causing kernel memory fault (qar 66890). QAR 61985:Panic occurred in advfs bs_get_bf_xtnt_map code. stack trace: ----------- (dbx) t > 0 boot(0x400000000, 0x4, 0xfffffc00007a7330, 0x0, 0x4) ["../../../../src/kernel/arch/alpha/machdep.c":2350, 0xfffffc0000590d74] 1 panic(s = 0xfffffc00006f0748) ["../../../../src/kernel/bsd/subr_prf.c":1163, 0xfffffc00002883f4] 2 hardclock(pc = 0xfffffc000052e7c8, ps = (unallocated - symbol optimized aw ay)) ["../../../../src/kernel/bsd/kern_clock.c":1163, 0xfffffc000025a3f0] 3 _XentInt(0x2, 0xfffffc000052e7c8, 0xfffffc00006d5af0, 0xfffffc00081a4000, 0xc00000cd0052f94a) ["../../../../src/kernel/arch/alpha/locore.s":1487, 0xfffffc000058d0f4] 4 vdealloc() ["../../../../src/kernel/vfs/vfs_subr.c":1374, 0xfffffc000052e7c4] 5 vrele(vp = 0x1d9) ["../../../../src/kernel/vfs/vfs_subr.c":2370, 0xfffffc000052f984] 6 mntbusybuf(mountp = 0xfffffc0002c83540) ["../../../../src/kernel/vfs/vfs_bio.c":1509, 0xfffffc0000527ab4] 7 boot(0x0, 0xfffffc0009920700, 0xfffffc0000000000, 0x2c0000002c, 0x32) ["../../../../src/kernel/arch/alpha/machdep.c":2305, 0xfffffc0000590c7c] 8 panic(s = 0xfffffc000076c050) ["../../../../src/kernel/bsd/subr_prf.c":1248, 0xfffffc00002885e4] 9 trap(a0 = (...), a1 = (...), a2 = (...), code = 0xfffffc00003fcfb4, exc_fr ame = 0xffffffff8cfe3 538) ["../../../../src/kernel/arch/alpha/trap.c":1877, 0xfffffc0000598af8] 10 _XentMM(0x0, 0xfffffc00003fcfb4, 0xfffffc00006d5af0, 0xffffffff8096e008, 0 x1) ["../../../../src/kernel/arch/alpha/locore.s":2091, 0xfffffc000058d594] 11 bs_get_bf_xtnt_map(0xffffffff8cfe37a8, 0xfffffc00021f4008, 0xfffffc0001fbf c08, 0xfffffc00021f40 20, 0x1) ["../../../../src/kernel/msfs/bs/bs_params.c":578, 0xfffffc00003fcfb0] 12 msfs_real_syscall(0xfffffc00021f4008, 0xfffffc0009e16a80, 0x0, 0x0, 0x0) ["../../../../src/kernel/msfs/bs/bs_misc.c":2809, 0xfffffc00003f8bfc] 13 msfs_syscall(0x0, 0x0, 0x0, 0x41, 0xfffffc00005962f0) ["../../../../src/kernel/msfs/osf/msfs_syscalls.c":145, 0xfffffc00002d103c] 14 syscall(0x20, 0xfffffc000023e8a1, 0x1, 0x13e2e3588136e, 0x0) ["../../../../src/kernel/arch/alpha/syscall_trap.c":718, 0xfffffc00005962ec ] 15 _Xsyscall(0x8, 0x3ff8123da08, 0x3ffc05cbe00, 0x60003, 0x11fff7190) ["../../../../src/kernel/arch/alpha/locore.s":1796, 0xfffffc000058d354] QAR 66890:"invalid memory read access" in imm_page_to_sub_xtnt_map(): stack trace: ----------- 5 panic(0xfffffc0000ae6300, 0xfffffc0000775698, 0x0, 0x46, 0x29211) ["../../../../src/kernel/bsd/ subr_prf.c":804, 0xfffffc000028a498] 6 trap(a0 = (...), a1 = (...), a2 = (...), code = 0xfffffffeae0bf490, exc_ frame = 0xfffffffeae0bf 388) ["../../../../src/kernel/arch/alpha/trap.c":1747, 0xfffffc0000576644] 7 _XentMM(0x0, 0xfffffc00003eb6c4, 0xfffffc00007cb0e0, 0x5cb0, 0xfffffc00d8 6ec908) ["../../../../ src/kernel/arch/alpha/locore.s":1736, 0xfffffc000056aed4] 8 imm_page_to_sub_xtnt_map(0x0, 0xfffffc00003eb6c4, 0xfffffc00007cb0e0, 0x5 cb0, 0xfffffc00d86ec90 8) ["../../../../src/kernel/msfs/bs/bs_inmem_map.c":2290, 0xfffffc00003eb6c0] 9 x_page_to_blk(0xfffffffeae0bf548, 0x5cb0, 0xfffffffe00c5d3f0, 0x800100000 001, 0x100000010) [".. /../../../src/kernel/msfs/bs/bs_stg.c":6113, 0xfffffc000040497c] 10 x_page_to_blkmap(0x2000, 0x0, 0xfffffffe00e259a4, 0x0, 0x0) ["../../../../src/kernel/msfs/bs/bs _stg.c":5836, 0xfffffc0000404718] 11 x_page_mapped(0x0, 0x2, 0xfffffc000000003d, 0x1, 0xfffffffeae0bf568) ["../../../../src/kernel/m sfs/bs/bs_stg.c":6189, 0xfffffc0000404a9c] 12 bs_frag_has_stg(bfSetH = struct { setH = 0x5cb0 dmnH = 0x0 }, fragId = struct { frag = 0x2e587 type = BF_FRAG_6K }) ["../../../../src/kernel/msfs/bs/bs_bitfile_sets.c":2166, 0xfffffc00003c7a8 0] 13 msfs_getattr(vp = 0x1, vap = 0xfffffffeae0bf648) ["../../../../src/kernel/msfs/osf/msfs_vnops.c ":1475, 0xfffffc000043d8cc] 14 pacl_vnperm(0x367c099f000ebbfa, 0x8003000ebbfa, 0x0, 0x2000, 0x0) ["../../../../src/kernel/sec/ sec_acl.c":614, 0xfffffc000024f2a8] 15 paclaccess(0x0, 0xfffffc00d234fc80, 0xfffffc000024f1bc, 0xfffffc00a2ef880 0, 0x1) ["../../../../ src/kernel/sec/sec_acl.c":906, 0xfffffc000024f7c4] 16 sp_vnaccess(0xfffffc000024f1bc, 0xfffffc00a2ef8800, 0x1, 0x1, 0xfffffc000 043d308) ["../../../.. /src/kernel/sec/sec_acl.c":579, 0xfffffc000024f1b8] 17 msfs_access(vp = 0xfffffc00a2ef8800, cred = 0xfffffc007f201c00) ["../../../../src/kernel/msfs/o sf/msfs_vnops.c":1251, 0xfffffc000043d304] 18 vn_open(0xfffffc000051a83c, 0xfffffffeae0bf8f0, 0xfffffc0000000003, 0xfff ffffeae0bf840, 0xfffff ffeae0bf838) ["../../../../src/kernel/vfs/vfs_vnops.c":614, 0xfffffc00005271b4 ] 19 copen(0x0, 0x3, 0xfffffc00d1f3b880, 0xfffffc008bc2d220, 0xfffffffeae0bf8e 0) ["../../../../src/k ernel/vfs/vfs_syscalls.c":2420, 0xfffffc000051a900] 20 open(0xfffffc00d1f3b880, 0xfffffc008bc2d220, 0xfffffffeae0bf8e0, 0x12, 0x fffffc0000573d28) PROBLEM: (QAR 51449, QAR 70650) (Patch ID: OSF425-797) ******** This patch fixes a panic in AdvFS which can have the following error messages: panic (cpu 1): bs_cow_pg: pin clone err -OR- panic (cpu 1): bs_cow_pg: cannot get blkMap PROBLEM: ('QAR 73644') (Patch ID: OSF425-816) ******** This patch fixes a problem with making a msfs_putpage() call. The length argument may get its upper bits truncated which will result in an incorrect length calculation. PROBLEM: (QAR 73827 71974) (PATCH ID: OSF425-860) ******** This patch fixes a problem in which an invalid error status is returned from the remove_entry system call. PROBLEM: (74687) (PATCH ID: OSF425-869) ******** This patch fixes a problem in AdvFS. The system panics with a kernel memory fault. PROBLEM: (71207, 71531) (PATCH ID: OSF425-870) ******** This patch fixes a problem in AdvFS. A system panic occured with the following error message: panic: del_dealloc_stg(): cant ref bmt page PROBLEM: (69193, 75226, 71876, 75211) (PATCH ID: OSF425-883) ******** This patch fixes the following /sbin/advfs/verify command problems: 1.) Verify fails to complete on a large number of files. After the command is terminated, filesets are left mounted. An error message like the following is produced: insert_set_tag: can't get bitfile set params error: -1093, E_NO_SUCH_BF_SET (-1093) set tag: 7.32772 (0x00000007.0x00008004) 2.) Verify will core dump when an offset into mountd[] array that is used to pull out the fileset name is corrupted. The fix is not use the corrupted number as an offset into the mounted[] array, but instead use the bogus offset to produce an error. 3.) Verify incorrectly reports errors on BMT's that have multiple extent records for domains created with the mkfdmn -p switch. This can produce an error message like the following: Checking mcell list ... set_mcell_position: position field already set disk: 2, mcell id (page.cell): 0.7 set tag: -2.0 (0xfffffffe.0x00000000) tag: -12.0 (0xfffffff4.0x00000000) 4.) Verify fails when lseeking on very large domains. The fix is instead of multimultiplying two 'ints' and assigning them into a long, causing a '32' bit roll over error, typecast one of the 'ints' to 'long' then perfom the multiplication. PROBLEM: (STLN70427, 71131, 74649) (PATCH ID: OSF425-887) ******** This patch fixes a problem that caused AdvFS to incorrectly calculate metadata file size for files greater than 4GB. This incorrect calculation resulted in the following errors: - Reads of metadata files that are larger than 4GB incorrectly report End-of -File - Reads of files whose extent maps occur more than 4GB from the beginning of the BMT, incorrectly report End-of-File - An incorrect file size of a metadata file is returned by "ls -ls" - Incorrect output is returned by the showfile command -The verify program reports incorrect errors PROBLEM: (77157, 76777) (PATCH ID: OSF425-893) ******** This patch fixes a problem where the output of a "ps" command, the PAGEIN column reports 0 for all processes. After installing this patch, the ps PAGEIN value increases as advfs accesses the disk for vm accesses (but not for normal file read). PROBLEM: (73321, 73943) (PATCH ID: OSF425-902) ******** This patch fixes a problem in Advfs. A panic occurs with the following error message: lock_read: hierarchy violation Two relevant stack traces are listed below: Stack Trace #1 1 panic() 2 thread_block() 3 thread_preempt() 4 boot() 5 panic() 6 cpu_ip_intr() 7 _XentInt() 8 simple_lock() 9 sq_wrapper() 10 csq_lateral() 11 runq_run() 12 netisr_thread() Stack Trace #2 1 panic() 2 event_timeout() 3 xcpu_puts() 4 printf() 5 panic() 6 lock_fault() 7 lock_read() 8 x_load_inmem_xtnt_map() 9 page_is_mapped() 10 bs_pinpg_one_int() 11 bs_pinpg_clone() 12 bs_pinpg_ftx() 13 rbf_pinpg() 14 alloc_mcell_undo() 16 ftx_fail() 17 stg_add_stg_no_cow() 18 stg_add_stg() 19 bmt_extend() 20 alloc_mcell() 21 bmt_alloc_prim_mcell() 22 new_mcell() 23 rbf_int_create() 24 rbf_create() 25 fs_create_file() 26 msfs_create() 27 vn_open() 28 copen() 29 open() 30 syscall() 31 _Xsyscall() PROBLEM: (FNO86520A) (PATCH ID: OSF425-916) ******** This patch fixes the problem of user/group quota underflow messages from appearing on the console. It also fixes the problem of inconsistent AdvFS quotas found when comparing vrepquota and vquota. An example of a console message that can be seen is: vmunix: chk_bf_quota: group quota underflow vmunix: chk_bf_quota: user quota underflow PROBLEM: (72111, 74264) (PATCH ID: OSF425-918) ******** This patch fixes a problem with verify. When verify is run on a brand new domain, nfs warnings are displayed even though no nfs related activity is being done. PROBLEM: (BCGMC0WVV) (PATCH ID: OSF425-926) ******** This patch fixes a system hang that could last up to a few minutes with large files when performing synchronous IO requests. The fix is to split up msync() requests into manageable pieces so users can continue working. PROBLEM: (76352) (PATCH ID: OSF425-938) ******** This patch fixes an AdvFS problem which caused the system to crash with a kernel memory fault. The stack trace is listed below: 8 panic() 9 trap() 10 _XentMM() 11 msfs_real_syscall() 12 msfs_syscall() 13 syscall() 14 _Xsyscall() PROBLEM: (75494, 75997) (PATCH ID: OSF425-956) ******** This patch fixes a problem with a kernel memory fault in AdvFS. The stack trace is listed below: 5 panic() 6 trap() 7 _XentMM() 8 bmtr_scan_mcells() 9 bmtr_get_rec_n_lk() 10 bf_get_l() 11 bf_get() 12 msfs_lookup() 13 namei() 14 vn_open() 15 copen() 16 open() 17 syscall() 18 _Xsyscall() PROBLEM: (QAR 74313 QAR 74121) (Patch ID: OSF425-857 ) ******** This patch fixes a problem in which the chfile utility can return an invalid error status. PROBLEM: (71353, 73768) (PATCH ID: OSF425-910) ******** This patch fixes a problem in AdvFS where putpage_lk/pg_busy deadlock causes hangs in the system. The stack traces are listed below: 0 thread_block 1 ubc_invalidate 2 bs_real_invalidate_pages 3 stg_remove_stg_start 4 bf_setup_truncation 5 msfs_setattr 6 vtruncate 7 ftruncate 8 syscall 9 _Xsyscall 0 thread_block 1 lock_wait 2 lock_read 3 msfs_putpage 4 ubc_memory_purge 5 vm_pageout PROBLEM: (HPAQB09J5) (PATCH ID: OSF425-889) ******** This patch fixes the following vrestore problems: - a previous patch caused incomplete restores - a warning message is displayed when the path for the first file in a group of hardlinks is created without using original protection codes and property lists. - a warning message is displayed and vrestore aborts if it fails to malloc space for a property list - a message which had been inserted at the end of the message file, had the wrong message category (could cause messaging confusion) - an uninitialized variable in the code that restores property lists could cause malloc failures, memory faults, "error setting extended attributes" and infinite loops using the '-l' option - corrupted property list information could cause an infinite loop PROBLEM: (74210, 74577) (PATCH ID: OSF425-990) ******** This patch fixes an AdvFS kernel memory fault caused by a race condition between migrate and chfile -L in bfflush_start. The stack trace is listed below: 5 panic("kernel memory fault") 6 trap() 7 _XentMM() 8 bfflush_start() 9 bs_bf_flush_nowait() 10 cp_copy_page_range() 11 migrate_normal() 12 mig_migrate() 13 bs_migrate() 14 msfs_syscall_op_migrate() 15 msfs_real_syscall() 16 msfs_syscall() 17 syscall() 18 _Xsyscall() PROBLEM: (75266, 74605) (PATCH ID: OSF425-1014) ******** This patch fixes a problem in AdvFS. The following error messages can occur: panic: simple_lock: uninitialized lock -or- kernel memory fault: simple_lock: minimum spl violation Stack trace is listed below for the panic: 0 boot src/kernel/arch/alpha/machdep.c : 1985 1 panic src/kernel/bsd/subr_prf.c : 755 2 lock_fault src/kernel/kern/lock.c : 2328 3 lock_write src/kernel/kern/lock.c : 627 4 ubc_bufalloc src/kernel/vfs/vfs_ubc.c : 1417 5 ufs_rwblk src/kernel/ufs/ufs_vnops.c : 4872 6 ufs_writepages src/kernel/ufs/ufs_vnops.c : 5873 7 ufs_putpage src/kernel/ufs/ufs_vnops.c : 5700 8 ubc_flush_dirty src/kernel/vfs/vfs_ubc.c : 3287 9 mntflushbuf src/kernel/vfs/vfs_bio.c : 1537 10 boot src/kernel/arch/alpha/machdep.c : 1914 11 panic src/kernel/bsd/subr_prf.c : 842 12 simple_lock_fault src/kernel/kern/lock.c : 2393 13 simple_lock_valid_violation src/kernel/kern/lock.c : 2412 14 grab_bsacc src/kernel/msfs/bs/bs_access.c : 3499 15 rbf_access_one_int src/kernel/msfs/bs/bs_access.c : 2619 16 rbf_access_int src/kernel/msfs/bs/bs_access.c : 2497 17 rbf_vfs_access src/kernel/msfs/bs/bs_access.c : 2369 18 bf_get_l src/kernel/msfs/osf/msfs_misc.c : 1303 19 msfs_lookup src/kernel/msfs/osf/msfs_lookup.c : 866 20 namei src/kernel/vfs/vfs_lookup.c : 592 21 vn_open src/kernel/vfs/vfs_vnops.c : 600 The stack trace is listed below for the kernel memory fault: 0 boot src/kernel/arch/alpha/machdep.c : 1985 1 panic src/kernel/bsd/subr_prf.c : 755 2 lock_fault src/kernel/kern/lock.c : 2328 3 lock_write src/kernel/kern/lock.c : 627 4 ubc_bufalloc src/kernel/vfs/vfs_ubc.c : 1417 5 ufs_rwblk src/kernel/ufs/ufs_vnops.c : 4872 6 ufs_writepages src/kernel/ufs/ufs_vnops.c : 5898 7 ufs_putpage src/kernel/ufs/ufs_vnops.c : 5700 8 ubc_flush_dirty src/kernel/vfs/vfs_ubc.c : 3287 9 mntflushbuf src/kernel/vfs/vfs_bio.c : 1537 10 boot src/kernel/arch/alpha/machdep.c : 1914 11 panic src/kernel/bsd/subr_prf.c : 842 12 trap src/kernel/arch/alpha/trap.c : 1753 13 _XentMM src/kernel/arch/alpha/locore.s : 1736 14 prf src/kernel/bsd/subr_prf.c : 1101 15 printf src/kernel/bsd/subr_prf.c : 405 16 simple_lock_fault src/kernel/kern/lock.c : 2362 17 simple_lock_minspl_violation src/kernel/kern/lock.c : 2426 18 grab_bsacc src/kernel/msfs/bs/bs_access.c : 3499 19 rbf_access_one_int src/kernel/msfs/bs/bs_access.c : 2619 20 rbf_access_int src/kernel/msfs/bs/bs_access.c : 2497 21 rbf_vfs_access src/kernel/msfs/bs/bs_access.c : 2369 22 bf_get_l src/kernel/msfs/osf/msfs_misc.c : 1303 23 msfs_lookup src/kernel/msfs/osf/msfs_lookup.c : 866 24 namei src/kernel/vfs/vfs_lookup.c : 592 25 vn_open src/kernel/vfs/vfs_vnops.c : 600 PROBLEM: (73942, 72418, 78280) (PATCH ID: OSF425-1002) ******** This patch fixes a problem in AdvFS in which a system that had already domain panic'ed results in a system panic. PROBLEM: (EVT29385A, 77833) (PATCH ID: OSF425-1004) ******** This patch fixes a problem where the vdump command will sometimes store symbolic link files as directories in the vdump archive. PROBLEM: (77274, 78605) (PATCH ID: OSF425-999) ******** This patch fixes a problem with AdvFS. An AdvFS domain becomes inaccessible when using the mount -d option. PROBLEM: (73864, 74625) (PATCH ID: OSF425-1001) ******** This patch fixes a problem with AdvFS in which a hang occurs due to a deadlock between bsbuf.state and bmt extent map lock. PROBLEM: (73035, 75406, 74962) (PATCH ID: OSF425-985) ******** This patch fixes a problem with AdvFS where all processes are waiting for buffers causing the system to hang. PROBLEM: (78020, 78520) (PATCH ID: OSF425-1009) ******** This patch fixes a problem in AdvFS where user data may be lost when a clone file is migrated. PROBLEM: (71455, 72062) (PATCH ID: OSF425-989) ******** This patch fixes a panic in AdvFS with the following error message: ftx_fail_2: dirty page not allowed PROBLEM: (MGO02694A) (PATCH ID: OSF425-1097) ******** This patch fixes hangs in AdvFS fileset operations such as clone creation and deletion when I/O errors or device full conditions resulted in the operation being "undone". PROBLEM: (75600, 75998) (PATCH ID: OSF425-1037) ******** This patch fixes a lock hierarchy violation in AdvFs. The trace from the crash will typically look like the following: 1 panic() 2 event_timeout(0) 3 xcpu_puts() 4 printf() 5 panic() 6 lock_fault() 7 lock_write( 8 bs_cow_pg() 9 bs_cow( ) 10 bs_pinpg_clone() 11 bs_pinpg_ftx() 12 rbf_pinpg() 13 bs_frag_dealloc() 14 fs_delete_frag() 15 msfs_setattr() 16 vn_open_ftrunc() 17 vn_open() 18 copen() 19 open() 20 syscall() 21 _Xsyscall() PROBLEM: (EVT0523123) (PATCH ID: OSF425-1086) ******** This patch fixes a memory leak when named pipes (FIFOs) are used. PROBLEM: (68328, 68412) (PATCH ID: OSF425-1028) ******** This patch prevents a system panic from occurring while using ADVFS. A typical stack trace may look similar to this: 5 panic(s = "SMP Assertion failed") 6 advfs_sad() 7 vd_htop_already_valid() 8 migrate_normal() 9 mig_migrate() 10 bs_migrate() 11 msfs_syscall_op_migrate() 12 msfs_real_syscall() 13 msfs_syscall() 14 syscall() 15 _Xsyscall() PROBLEM: (EVT18628A, 59132) (PATCH ID: OSF425-1090) ******** This patch modifies advfs kernel code and several utilities. AdvFS will no longer panic with the following error: ADVFS EXCEPTION : panic cpu(0) : bad frag free list. The code is modified so that during frag allocation when advfs determines that the frag group header's free list has been corrupted, it stops using it and marks it BAD. It is then removed from the free list so no more allocations can take place AND no deallocations are performed. The verify, shfragbf and vfragpg programs are modified to report BAD frag groups. PROBLEM: (74608, 74224) (PATCH ID: OSF425-1023) ******** This patch fixes a problem in which rmvol can hang in a wait state. PROBLEM: (ALC-2-076) (PATCH ID: OSF425-1091) ******** This patch fixes a potential problem flushing data to disk when using data logging with sparse files in an AdvFS filesystem. PROBLEM: (ALC-2-076) (PATCH ID: OSF425-1075) ******** This patch provides support for activating temporary atomic write data logging on all files within the mount point. The data logging is turned off when the fileset is unmounted. PROBLEM: (MGO69211A) (PATCH ID: OSF425-1079) ******** This patch fixes an AdvFS hang that is caused by a thread waiting for flushCv notification and is holding resources that other threads want. This type of hang has been experienced when shutting the system down. PROBLEM: (MGO10736A, EVT0396650, TPOB36405, BCSM10NZK) (PATCH ID: OSF425-1084) ******** This patch fixes a problem where threads can hang in x_load_inmem_xtnt_map() when called from x_page_to_blkmap(). A typical hung thread will have the following calls at the top of its stack trace: 0 thread_block 1 lock_read 2 x_load_inmem_xtnt_map 3 x_page_to_blkmap 4 x_page_to_iolist 5 blkmap PROBLEM: (HGO053280) (PATCH ID: OSF425-1078) ******** This patch fixes a problem where a system can crash with the panic string, "bs_pinpg_one_int: nextflushseq(2) rollover". A typical stack trace of the panicing thread might look like: panic advfs_sad bs_pinpg_one_int bs_pinpg_clone bs_pinpg fs_write msfs_write vn_write5 rwuio write syscall _Xsyscall PROBLEM: (83661, 85312, STL111443) (PATCH ID: OSF425-1082) ******** This patch fixes a problem where the setgid bit of a directory was not being set when created, if its parent directory has the setgid bit set. PROBLEM: (78711, 78577, 78703, 78751, 79066) (PATCH ID: OSF425-1038) ******** This patch fixes a panic in AdvFS which has the following error message: panic: Unaligned kernel space access from kernel mode The stack trace is listed below: 21 afault_trap() 22 _XentUna() 23 seq_search() 24 msfs_lookup() 25 cfs_comm_lookup() 26 cfscall_lookup() 27 cfs_lookup() 29 _F64_stat1() 30 lstat() 31 syscall() 32 _Xsyscall() PROBLEM: (ALC-2-076) (PATCH ID: OSF425-1093) ******** This patch fixes a timing window where flushing data to disk can be incomplete when a system is going down. Note this can only occur if all of these conditions are true: o More than one thread calls the reboot() system call without first going through shutdown, /sbin/reboot, or /sbin/halt (note the operating system itself does not do this, it would have to be an application program which is calling reboot()). o O_SYNC is not in use. o AdvFS data logging is not in use. PROBLEM: (STL069451) (PATCH ID: OSF425-1049) ******** This patch corrects a problem in which a single application's creating and removing of files repeatedly in the absence of other applications working on the same fileset can cause poor 'update' daemon performance due to a flawed kernel hashing algorithm. PROBLEM: (HPAQ21K51, HPAQ412CK) (PATCH ID: OSF425-1073) ******** This patch fixes the following problems in the following commands: vdump: - failed to flag compressed extended attributes records that are split across a vdump BLOCK boundary - Correct "Rewinding" message to avoid a segfault with Internationalized messages. - overrides the -D option when the source path describes a root fileset NOTE: If you want to backup quota files you must not use the -D option. vrestore: - fails to properly handle extended attributes records in compressed archives. This results in malloc failures, proplist corruption, program abort, program crashes due to segfault or invalid memory access, and the display of the error message "error setting extended attributes" - fails to set extended attributes due to confusion over selective restore of the file or directory associated. Also results in display of error message "error setting extended attributes". - selective restore of hardlinked files is incomplete when they exist in different directories (fails to create directory for second occurrence of file with same inode number) - The -Q option is added to vrestore to allow the user to request that we ignore the quota files (thus avoiding the time that it takes to process them) PROBLEM: (GB_G00942) (PATCH ID: OSF425-1085) ******** While performing the rmfset operation, AdvFS panic'd with the following error message: "rbf_delete_int: can't find bf attributes"