From owner-freebsd-geom@FreeBSD.ORG Fri Jan 12 21:32:24 2007 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2B07216A407 for ; Fri, 12 Jan 2007 21:32:24 +0000 (UTC) (envelope-from cyberleo@cyberleo.net) Received: from pizzabox.cyberleo.net (alpha.cyberleo.net [198.145.45.10]) by mx1.freebsd.org (Postfix) with ESMTP id DE77113C44B for ; Fri, 12 Jan 2007 21:32:23 +0000 (UTC) (envelope-from cyberleo@cyberleo.net) Received: (qmail 38116 invoked from network); 12 Jan 2007 21:32:23 -0000 Received: from adsl-69-212-1-127.dsl.chcgil.ameritech.net (HELO ?172.16.44.14?) (cyberleo@cyberleo.net@69.212.1.127) by alpha.cyberleo.net with ESMTPA; 12 Jan 2007 21:32:23 -0000 Message-ID: <45A7FE3F.3040505@cyberleo.net> Date: Fri, 12 Jan 2007 15:31:43 -0600 From: CyberLeo Kitsana User-Agent: Thunderbird 1.5 (X11/20051201) MIME-Version: 1.0 To: "R. B. Riddick" References: <765687.4465.qm@web30301.mail.mud.yahoo.com> In-Reply-To: <765687.4465.qm@web30301.mail.mud.yahoo.com> Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Geom Subject: Re: geom_raid5 livelock? X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jan 2007 21:32:24 -0000 R. B. Riddick wrote: > --- CyberLeo Kitsana wrote: >> ... > You could try to activate graid5's debugging by setting the debug level to 2: > sysctl kern.geom.raid5.debug=2 > Then u should see the requests in /var/log/messages... > I would be interested then in those messages during a suspected live lock (just > wait for that strange condition and then set the debug level to 2 for some > seconds until u feel u have enough data...)... http://home.cyberleo.net/cyberleo/workspace/Zip/graid5-testing.png As shown in top, one rsync and one find process are stuck in biord waiting for data from the filesystem, while the CPU is otherwise mostly quiescent. I can't find evidence anywhere of what could be using the raid5 and mirror providers so much, though. The frozen processes are one locate database update (find) and one rsync process copying data from an old backup machine to the new one. The frozen processes do not respond to attempts to kill them until the filesystem begins responding. Also, tuning the sysctl had no effect prior to, nor during, the livelock. Nothing new appeared in /var/log/messages while set to 1 or 2. Thanks! -- Fuzzy love, -CyberLeo Technical Administrator CyberLeo.Net Webhosting http://www.CyberLeo.Net Furry Peace! - http://www.fur.com/peace/