From owner-freebsd-questions@FreeBSD.ORG Sat Jan 10 20:05:57 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9EAE116A4CE for ; Sat, 10 Jan 2004 20:05:57 -0800 (PST) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6338B43D55 for ; Sat, 10 Jan 2004 20:05:56 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.12.10/8.12.10) id i0B45tS6030387; Sat, 10 Jan 2004 22:05:55 -0600 (CST) (envelope-from dan) Date: Sat, 10 Jan 2004 22:05:55 -0600 From: Dan Nelson To: Ted Wisniewski Message-ID: <20040111040555.GD3393@dan.emsphone.com> References: <200401110025.i0B0PNxL002500@ness.plymouth.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200401110025.i0B0PNxL002500@ness.plymouth.edu> X-OS: FreeBSD 5.2-CURRENT X-message-flag: Outlook Error User-Agent: Mutt/1.5.5.1i cc: freebsd-questions@freebsd.org Subject: Re: 5.2-RELEASE - Show stopper problem X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Jan 2004 04:05:57 -0000 In the last episode (Jan 10), Ted Wisniewski said: > In 5.2-RC and 5.2-RELEASE there appears to be some issue with > filesystem or I/O subsystem under 5.2-X. Now, You can install and do > the normal kind of things, however, when you create a lot of I/O on > the disk there seems to be a problem actually reading/writing it > to/from disk. For example, If I do a "make buildworld"... It > appears to go along ok. However, I have had a number of (repeatable) > situations where the "make installworld" will go so far then will not > be able to complete. In this case, there is an attempt to write data > to disk that cannot complete; the process goes into a disk wait state > (it cannot be killed, and will stay in this state ... forever). > > For example the standard daily security script: > > 727 p0 T 0:00.00 sh 100.chksetuid > 737 p0 T 0:02.14 find /usr -xdev -type f ( -perm -u+x -or -perm -g+x -or -perm -o+x ) ( -perm -u+s -or -perm -g+s The 'T' state usually means that someone sent the process a STOP signal. Try running "kill -CONT 727 737" to start them back up. Processes waiting on disk I/O will be in the 'D' state, and you can run "ps axO wchan" to print the specific part of the kernel it's waiting in. -- Dan Nelson dnelson@allantgroup.com