From owner-freebsd-fs@FreeBSD.ORG Sun Apr 22 03:42:54 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E7A3716A401 for ; Sun, 22 Apr 2007 03:42:54 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id D725F13C44C for ; Sun, 22 Apr 2007 03:42:54 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 18B821A4D89; Sat, 21 Apr 2007 20:43:15 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 253B151428; Sat, 21 Apr 2007 23:42:54 -0400 (EDT) Date: Sat, 21 Apr 2007 23:42:53 -0400 From: Kris Kennaway To: Wes Morgan Message-ID: <20070422034253.GA88705@xor.obsecurity.org> References: <20070421223552.F969@volatile.chemikals.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070421223552.F969@volatile.chemikals.org> User-Agent: Mutt/1.4.2.2i Cc: freebsd-fs@freebsd.org Subject: Re: apparent filesystem-related hangs X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Apr 2007 03:42:55 -0000 On Sat, Apr 21, 2007 at 10:51:10PM -0400, Wes Morgan wrote: > I have several filesystems built on top of a gconcat volume consisting of > 2 300gb and 1 500gb drive. The /usr partition constitutes the bulk of it. > The volume is sitting around 95% full, and twice I've had the system > become "hung" in what I believe are filesystem operations. It seems to > crop up when rtorrent tries to create files that would fill up the system, > but of course it doesn't actually reserve it until it is used. Any running > process remains responsive until it needs to access the disk. > > The system was running a fairly recent 6.2-stable, March 29, but I've > since updated to the most recent -stable. > > If anyone can give me some pointers as to how to tell exactly where these > processes are hanging, I can try to reproduce it... But it takes a while > to fsck the volume so I don't want to have to try too many things. If it's > not a known problem I can then submit a PR. DEBUG_LOCKS, DEBUG_VFS_LOCKS, INVARIANTS, INVARIANT_SUPPORT, then 'show lockedvnods' and 'alltrace' from ddb via the serial console when it hangs. Kris