From owner-freebsd-questions@FreeBSD.ORG Sat Jan 10 16:25:26 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 C82B416A4CE for ; Sat, 10 Jan 2004 16:25:26 -0800 (PST) Received: from ness.plymouth.edu (ness.plymouth.edu [158.136.1.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0C5A343D31 for ; Sat, 10 Jan 2004 16:25:24 -0800 (PST) (envelope-from ted@ness.plymouth.edu) Received: from ness.plymouth.edu (localhost [127.0.0.1]) by ness.plymouth.edu (8.12.9p2/8.12.4) with ESMTP id i0B0PNCG002501 for ; Sat, 10 Jan 2004 19:25:23 -0500 (EST) Received: (from ted@localhost) by ness.plymouth.edu (8.12.9p2/8.12.9/Submit) id i0B0PNxL002500 for freebsd-questions@freebsd.org; Sat, 10 Jan 2004 19:25:23 -0500 (EST) (envelope-from ted) From: Ted Wisniewski Message-Id: <200401110025.i0B0PNxL002500@ness.plymouth.edu> To: freebsd-questions@freebsd.org Date: Sat, 10 Jan 2004 19:25:22 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL88 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Subject: 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 00:25:26 -0000 Here is a description of the problem... 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 I have experienced the same problem on a number of hardware types (Servers like New Dell Power edge 6550's and variety of PC's). For some reason, it appears that data cannot be read or written to/from the disk. Possibly due to some lock never being released. So, the only way to get rid of the process is to reboot... During the reboot, the system complains about not being able to flush buffers and "gives up" and on boot, all the filesystems are "dirty" and must be FSCK'ed. Originally, I thought it had something to do with the server model, but it does occur on a number of Desktop model (a variety of vendors) machines as well. I did send in a PR or two a couple of weeks ago)... but since I see RELEASE tag... Anyway, If someone could shed any light on why... I have not been able to repeat this behavior on 4.9. Ted