This patch corrects the following: - Corrects a problem where the mcellCount on-disk was not being updated as files were being migrated and this resulted in a panic situation. - Fixes AdvFS performance problems. - Fixes an AdvFS problem that causes a lockmode 4 system panic. - Corrects a situation where a quotacheck can cause a system panic. - 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() - 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. - 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. - 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 - Fixes system panic with the following error message: panic (cpu 0): kernel memory fault - Fixes 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. - Fixes system panic with the following error message: AdvFS exception Module=26 line=1483 - Fixes to prevent the following two panics: o AdvFS Exception Module = 1, line = 1891 o kernel memory fault - 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. - Idle time is reset on broadcast message when AdvFS is the root file system. - System panics with "kernel memory fault" in ubc_page_alloc(). - 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. - A panic that is seen when running the auditd and auditing msfs_syscall. There will most likely be a lot of memory contention as well for this panic to be triggered. - A problem in which the getrusage system call returns zero for the values of ru_inblock and ru_outblock on an AdvFS file system. - Fixes NFS rpc.lockd "can't clear lock after crash of client" when AdvFS is being used. - Prevents a "kernel memory fault" in the msfs_reclaim() routine on systems using AdvFS. - 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. - Fixes a problem that occurs on AdvFS systems. The system will panic with the following error message: malloc_overflow: guard space corruption - Fixes a problem with the AdvFS fs_write routine, which would mishandle partial writes after detecting an error. - Fixes a problem in AdvFS locking code which causes the following panic: kernel memory fault - 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. - Corrects a problem where a panic would occur when running rmtrashcan on a clone. - 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.