PROBLEM: (QAR 47190) (Patch ID: OSF375-047) ******** This patch fixes a situation in which a kernel memory fault can occur. This panic will only occur if the system is currently running the auditd demon and auditing msfs_syscall calls. These are the AdvFs system calls. The panic is most likely to occur if there is a heavy system load and paging is occuring. The trace back will be: 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: (TKTC51NLS, QAR 29248) (Patch ID: OSF375-360041) ******** This patch fixes a problem in which the getrusage system call returns zero for the values of ru_inblock and ru_outblock on an AdvFS file system. To observe the problem on a system where /usr is an AdvFS file system, do the following as root: csh cp /vmunix /usr/vmunix.tmp1 time cp /usr/vmunix.tmp1 /usr/vmunix.tmp2 # the time command shows 0+0io (before applying the patch) rm /usr/vmunix.tmp1 /usr/vmunix.tmp2 PROBLEM: (CLD SOO100812) (Patch ID: OSF375-360051) ******** This fix corrects a problem when remote NFS clients crash and reboot while holding locks againsts files on an AdvFS files system. Prior to this fix the daemon.log file would receive messages similar to the following: Jul 9 13:24:56 lockd[649]: can't clear locks after crash of client : Invalid argument This patch corrects the problem. PROBLEM: (9WAB62151, QAR 46315, QAR 34257, QAR 35785) (Patch ID: OSF375-052) ******** This patch fixes a problem in which a system using AdvFS can run out of metadata space when the AdvFS domain still has some free space available. The system will display error messages such as 'no space left on device'. The problem may occur on a heavily fragmented system with many small files, such as an Internet News server or Mail server. To handle this problem, please use the -p and -x options when using the mkfdmn command to create an AdvFS domain that is expected to have many small files. Specifying the new -p option to the mkfdmn command pre-allocates internal AdvFS structures and the erroneous 'out of space' messages will not occur. NOTE: Please run the mkfdmn command with no options or arguments to list the updated mkfdmn man page and the -p and -x option descriptions. PROBLEM: (HPXQ43C4D, TKTR52185, QAR 46016) (ref info Patch ID: OSF375-055) ******** This patch fixes some hangs that may occur after the message "syncing disks..." is printed when the system panics. When these hangs occur, the completion of the "syncing disks..." message - the word "failed" or "done" does not get printed, and the system does not take a dump. In addition to fixing these known hangs, a timout mechanism is added to the "syncing disks" logic that will improve the reliability of getting a dump by using the system clock to break out of the "syncing disks" path and take a dump if no progress is being made on reducing the number of buffers to be flushed. The numbers printed periodically between the "syncing disks..." and "done" messages are the number of buffers left to flush. This patch also makes it more likely that AdvFS buffers will be flushed to disk during the "syncing disks..." processing after a system panic. There is still no guarantee that writes in progress at the time of a panic will be completed. PROBLEM: (mcpm75130) (Patch ID: OSF375-360067) ******** The system can crash with a kernel memory fault in ubc_page_alloc(). A typical trace is: ... 5 panic("kernel memory fault") [src/kerubr_prf.c:719] 6 trap() [src/kernel/arch/alpha/trap.c:1243([] 8 ubc_page_alloc() [src/kernel/vfs/vfs_ubc.c:2112] 9 ubc_lookup() [src/kernel/vfs/vfs_ubc.c:1811] 10 ufs_getapage() [src/kernel/ufs/ufs_vnops.c:4728] 11 ufs_getpage() [src/kernel/ufs/ufs_vnops.c:5141([([([] 15 rwuio()[src/kernel/bsd/sys_generic.c:1069] 16 read() [src/kernel/bsd/sys_generic.c:1021] 17 syscall() [src/kernel/arch/alpha/syscall_trap.c:519] 18 _Xsyscall() [l/arch/alpha/locore.s:1094] PROBLEM: (HPXQ42587) (Patch ID: OSF375-360071) ******** On an AdvFS system, a broadcast message will cause the idle time to be reset to zero. PROBLEM: (QAR46333,QAR40839,ZPOT90826) (Patch ID: OSF375-350324) ******** This patch fixes a problem that occurs with the telnet and ftp commands. Telnet or ftp processes that are no longer in use, are left on the system indefinitely. When a user tries to log in, the login process hangs after displaying the last login message. PROBLEM: (MGO102584) (Patch ID: OSF375-360088) ******** This patch fixes AdvFS to prevent the following two panics: o AdvFS Exception Module = 1, line = 1891 o kernel memory fault with the following stack trace: _XentMM() bs_refpg_int() bs_refpg() tagdir_get_info() bs_bfdmn_activate() bs_bfdmn_tbl_activate() fs_fset_get_info() msfs_real_syscall() msfs_syscall() syscall() _Xsyscall() PROBLEM: (MANBCP087,QAR 50227) (Patch ID: OSF375-360090) ******** This patch fixes a problem that occurs on AdvFS systems in which the system panics with the following error message: AdvFS exception Module=26 line=1483 This problem follows an I/O error, and may also cause memory and/or data corruption without causing a system panic. The stacktrace of the panic thread will be as follows: panic() advfs_sad() ftx_fail_2() ftx_fail() fs_write() msfs_write() vn_write() rwuio() write() syscall() _Xsyscall() The problem may have also led to memory and/or data corruption, without the above panic. PROBLEM: (UTO101199, HPAQ30ETE, QAR 51485, QAR 52365) (Patch ID: OSF375-077) ******** This patch corrects a problem with an NFS V3 mounted AdvFS file system where under heavy I/O load, data 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: (GOZ100774) (Patch ID: OSF375-360112) ******** This patch fixes a problem that occurs on AdvFS systems. The system will panic with an error message similar to the following: AdvFS I/O error faulting virtual address: 0x000000000000003c pc of faulting instruction: 0xfffffc00003998d0 ra contents at time of fault: 0xfffffc000039ac70 sp contents at time of fault: 0xffffffffb7d0f480 panic (cpu 0): kernel memory fault The following is a sample stack trace: 0 thread_block() 1 thread_preempt() 2 boot() 3 panic() 4 trap() 5 _XentMM() 6 imm_get_first_xtnt_desc() 7 imm_get_first_hole() 8 frag_list_extend() 9 bs_frag_alloc() 10 fs_create_frag() 11 close_one_int() 12 close_int() 13 bs_vfs_close() 14 msfs_inactive() 15 vrele() 16 utimes() 17 syscall() 18 _Xsyscall() PROBLEM: (QAR 54852) (Patch ID: OSF375-137) ******** Fixes a system panic when shutting down to single user mode using either one of the following commands when AdvFS is the root or usr filesystem: # shutdown now # init s The cause of this problem is subject to the timing of several kernel threads, therefore the symptoms or panic may occur intermittently and on different platforms. The example stack trace is as follows: > 0 boot(0x0, 0x4, 0x1, 0x1, 0xfffffc00004893b8) ["../../../../src/kernel/arch/alpha/machdep.c":1795, 0xfffffc00004f4a6c] 1 panic(s = 0xfffffc0000630098 = "panic stuck syncing disks") ["../../../../src/kernel/bsd/subr_prf.c":673, 0xfffffc0000450eb8] 2 hardclock(pc = 0xfffffc0000281388 = "@", ps = 0x2) ["../../../../src/kernel/bsd/kern_clock.c":736, 0xfffffc0000437044] 3 _XentInt(0x2, 0xfffffc0000281388, 0xfffffc0000681bd0, 0xfffffc0006152de0, 0x1) ["../../../../src/kernel/arch/alpha/locore.s":917, 0xfffffc00004f1764] 4 ufs_fsync_clrflag_wakeup(ip = 0xfffffc0006152cb0, dolock = 0x6152c00) ["../../../../src/kernel/ufs/ufs_vnops.c":6242, 0xfffffc0000281384] 5 ufs_inactive(vp = 0xfffffc0006152c00) ["../../../../src/kernel/ufs/ufs_inode.c":1231, 0xfffffc000026f180] 6 vrele(vp = 0xfffffc0002196400) ["../../../../src/kernel/vfs/vfs_subr.c":2234, 0xfffffc00004638ec] 7 mntbusybuf(mountp = (nil)) ["../../../../src/kernel/vfs/vfs_bio.c":1356, 0xfffffc0000460d30] 8 boot(0x0, 0x0, 0xffffffff887fb4c8, 0x36, 0x8000000000) ["../../../../src/kernel/arch/alpha/machdep.c": 1751, 0xfffffc00004f4978] 9 panic(s = 0xffffffff887fb4c8 = "N1 = 2") ["../../../../src/kernel/bsd/subr_prf.c":757, 0xfffffc0000451074] 10 advfs_sad(0x1a, 0xae7, 0xfffffc000062ac30, 0x0, 0x2) ["../../../../src/kernel/msfs/bs/bs_misc.c":345, 0xfffffc00003e85dc] 11 log_donerec_nunpin(ftxp = 0xfffffc0007cd8008, dmnp = (nil), lrdp = (nil)) ["../../../../src/kernel/msfs/bs/ftx_routines.c":2790, 0xfffffc00003c0218] 12 ftx_done_urdr(ftxH = (...), agentId = FTA_BS_BMT_UPDATE_REC_V1, undoOpSz = 0x0, undoOp = (nil), rootDnOpSz = 0x0, rootDnOp = (nil), redoOpSz = 0x0, redoOp = (nil)) ["../../../../src/kernel/msfs/bs/ftx_routines.c":1225, 0xfffffc00003bda38] 13 ftx_done_n(ftxH = (...), agentId = 30914472) ["../../../../src/kernel/msfs/bs/ftx_routines.c":978, 0xfffffc00003bd5bc] 14 bmtr_update_rec_int(0xffffffff80287ef8, 0xff, 0xfffffc0007d61498,0x58, 0x0) ["../../../../src/kernel/msfs/bs/bs_bmt_util.c":1816, 0xfffffc00003b6308] 15 bmtr_update_rec(0x400fe001f003c00, 0xff, 0xfffffc0007d61498, 0x58,0x0) ["../../../../src/kernel/msfs/bs/bs_bmt_util.c":1646, 0xfffffc00003b5fe8] 16 fs_flush_saved_stats(0xfffffc000041cfa0, 0x0, 0x13000004b0273001, 0x2c000009f7000055, 0xfffffc0007cc0018) ["../../../../src/kernel/msfs/fs/fs_create.c":1100, 0xfffffc000041e1a8] 17 cleanup_bfap_with_saved_stats(bfap = 0xfffffc000041cfb8) ["../../../../src/kernel/msfs/bs/bs_access.c" :766, 0xfffffc00003e5674] 18 fs_cleanup_thread(0x0, 0xfffffc0007d61488, 0x130000018e0169, 0x281f00000000, 0xa80000053d0000) ["../../../../src/kernel/msfs/fs/fs_dir_init.c":906, 0xfffffc000041cfb4] PROBLEM: (QAR 52529, QAR 49940) (Patch ID: OSF375-115) ******** This patch corrects a problem with domain panics that could possibly cause the system to panic. A new AdvFS error number (E_DOMAIN_PANIC) (-1028) was created. The problem occurs when a domain panic occurs and the system is unable to handle or deal with the situation and it panics in turn. This patch corrects all known cases where the domain might panic. PROBLEM: (QAR 52961) (Patch ID: OSF375-122) ******** This patch fixes a problem that occurs on AdvFS file systems where, under certain circumstances, modifications to mmaped data are not written to disk. This may result in data corruption. PROBLEM: (QAR 54548, QAR 51121) (Patch ID: OSF375-127) ******** This patch fixes a kernel memory fault problem that occurs on AdvFS file systems. The system displays the following error message: panic: kernel memory fault at spec_reclaim() A sample stack trace is shown in the following example: > 0 boot() 1 panic(s = 0xfffffc000068ed00 = "kernel memory fault") 2 trap() 3 _XentMM() 4 spec_reclaim() 5 msfsspec_reclaim(vp = 0xfffffc000186e200) 6 msfs_inactive() 7 vrele(vp = 0xfffffc000029eca0) 8 vn_close() 9 closef() 10 close() 11 syscall() 12 _Xsyscall() End Trace for machine_slot[paniccpu].cpu_panic_thread: PROBLEM: (QAR 56366, QAR 56062) (Patch ID: OSF375-144) ******** This patch corrects a situation where a quotacheck can cause a system panic. The problem occurs in a system call in a race condition with umount. The panic looks similiar to: 0 stop_secondary_cpu(do_lwc = 0) 1 panic(s = 0xfffffc0000682f48 = "event_timeout: panic request") 2 event_timeout(func = 0xfffffc000027ef20, arg = 0xfffffc0000730908) 3 xcpu_puts(s = (nil), prfbufp = 0xfffffc0000730908) 4 printf() 5 panic(s = 0xffffffffa93634b8 = "bs_bf_htop: invalid handle\n N1 = 0") 6 advfs_sad() 7 bs_bf_htop() 8 bs_frag_has_stg(bfSetH = struct { setH = 0 dmnH = 0 }, fragId = struct { frag = 0 type = BF_FRAG_ANY }) 9 msfs_real_syscall() 10 msfs_syscall() 11 syscall() 12 _Xsyscall() PROBLEM: (QAR 57625,QAR 57639,QAR 58959,QAR 58241) (Patch ID: OSF375-155) ******** 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 55640, QAR 51918) (Patch ID: OSF375-162) ******** This patch fixes AdvFS performance problems. PROBLEM: (QAR 57258, QAR 56851) (Patch ID: OSF375-164) ******** This patch corrects a problem where the mcellCount on-disk was not being updated as files were being migrated and this resulted in a panic situation. The panic would produce a message like: bs_frag_alloc: pinpg faild\n N1 = -1035 PROBLEM: (EVT102509 GOZ100927 QAR 60509) (Patch ID: OSF375-171) ******** 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 57426,QAR 57942) (Patch ID: OSF375-172) ******** 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 59953, QAR 59419) (Patch ID: OSF375-173) ******** 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 57450) (Patch ID: OSF375-183) ******** 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 60129, QAR 62613) (Patch ID: OSF375-231) ******** 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 62617, QAR 62299, QAR 51568, HPAQ60W1F) (Patch ID: OSF375-244) ******** This patch fixes a problem in AdvFS. AdvFS does not return an error when a user opens a file in O_SYNC mode and power is lost on the disk drive. PROBLEM: (QAR 61304, QAR 60584) (Patch ID: OSF375-188) ******** 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: OSF375-197) ******** This patch fixes a problem with AdvFS, which caused a system panic with the following messge: 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()