From owner-freebsd-current@FreeBSD.ORG Tue Jan 27 07:36:25 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 1C6B116A4CE for ; Tue, 27 Jan 2004 07:36:25 -0800 (PST) Received: from mail.gactr.uga.edu (mail.gactr.uga.edu [128.192.37.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id D1AD743D72 for ; Tue, 27 Jan 2004 07:36:13 -0800 (PST) (envelope-from robin.blanchard@gactr.uga.edu) Received: from 127.0.0.1 (localhost [127.0.0.1]) by dummy.domain.name (Postfix) with SMTP id 275D177418 for ; Tue, 27 Jan 2004 10:36:11 -0500 (EST) Received: from EBE1.gc.nat (E2K1.gc.nat [10.10.11.21]) by mail.gactr.uga.edu (Postfix) with ESMTP id DEBCB773F8 for ; Tue, 27 Jan 2004 10:36:10 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Tue, 27 Jan 2004 10:36:10 -0500 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Processes blocked on ufs or getblk Thread-Index: AcPj1YRJw9Pd3u7NSGa0pNIQYwoMawBFTsjA From: "Robin P. Blanchard" To: "Andre Guibert de Bruet" , "Ken Smith" , "Kris Kennaway" , Subject: RE: Processes blocked on ufs or getblk 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, 27 Jan 2004 15:36:25 -0000 > I'm reviving this thread as I have more information that=20 > might help track this problem down. The offending process in=20 > this case is gqview but it could have been 'find /' or any=20 > other process running when there's high system load (such as daylies). >=20 > >From the emails that I've gotten it appears that this bug=20 > affects users > that are using either ccd or hardware raid (amr driver in my=20 > case). I've attached the output of a ddb ps and a 'show lockednods'. >=20 > Every time the getblk hang rears it's ugly head, I've seen > "amr0: bad slot x completed" (where x is an integer between 0=20 > to 4) printed on the serial console. >=20 > This makes me think that there's a failure mode or special=20 > state that isn't being checked with the amr driver. Perusing=20 > the code shows that the bad slot message is a result of a=20 > NULL busy command. I'm no storage driver and my VFS knowledge=20 > is somewhat limited. Anyone out there want to have a look at=20 > this? I'm willing to try out any patches on this system. As seen previously on this list, I'm also seeing processes getting stuck = in in "getblk" state. I'm seeing this on a dell 2650 (smp enabled, acpi = enabled, aac filesystem). I'm also more than willing to try out any patches = anyone may cook up.=20 --------------------------------------- Robin P. Blanchard Systems Integration Specialist Georgia Center for Continuing Education fon: 706.542.2404 < > fax: 706.542.6546 ---------------------------------------