From owner-freebsd-current@FreeBSD.ORG Tue Jul 13 13:05:21 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E150916A4CE; Tue, 13 Jul 2004 13:05:21 +0000 (GMT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 89D0743D39; Tue, 13 Jul 2004 13:05:21 +0000 (GMT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.12.10/8.12.10) with ESMTP id i6DD5LWg025257 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 13 Jul 2004 09:05:21 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.12.9p2/8.12.9/Submit) id i6DD5G65030788; Tue, 13 Jul 2004 09:05:16 -0400 (EDT) (envelope-from gallatin) From: Andrew Gallatin Message-ID: <16627.56844.22088.901721@grasshopper.cs.duke.edu> Date: Tue, 13 Jul 2004 09:05:16 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Gary Stanley In-Reply-To: <6.1.2.0.2.20040712142407.02d38a98@64.124.166.215> References: <6.1.2.0.2.20040712142407.02d38a98@64.124.166.215> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid cc: alc@freebsd.org cc: freebsd-current@freebsd.org Subject: sendfile problem (Re: Network related procs hang in unusual sfpbsy state) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jul 2004 13:05:22 -0000 Gary Stanley writes: > New current kernel from about 3 days ago, certain processes hang after > about a day in this state; > > 80 599 1 0 -16 -2 59020 53548 sfpbsy D< ?? 1141:08.65 > /mnt/zeus/web/bin/zeus.web This means that the webserver was trying to send a file via sendfile(), it encountered a busy page, and went to sleep waiting for that page to be not-busy. But nothing ever woke it up... You might be able to work around this temporarily by disabling sendfile on your web server. But its something which needs to be fixed. It would be interesting to look at the page in question to see if its still busy. Do you have a gdb which can do kernel debugging? (apparently ports/dev/gdb53 can..) Drew