From owner-freebsd-current Fri May 29 16:14:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA26866 for freebsd-current-outgoing; Fri, 29 May 1998 16:14:30 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA26841 for ; Fri, 29 May 1998 16:14:19 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id PAA01191; Fri, 29 May 1998 15:08:25 -0700 (PDT) Message-Id: <199805292208.PAA01191@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: shimon@simon-shapiro.org cc: Michael Hancock , "freebsd-current@freebsd.org" , tcobb , Karl Pielorz Subject: Re: DPT driver fails and panics with Degraded Array In-reply-to: Your message of "Fri, 29 May 1998 15:21:17 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 29 May 1998 15:08:25 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I am routinely running a Dual DPT with 38 drives on 6 busses. On > 3.0-CURRENT SMP. The system did lose disk drives, either intentionally, or > by accident. I cannot confirm any of Mr. Cobb's finding. I have not been > funished with any data, including the panic point, which I suspect is not > in the DPT code. I am still waiting for such data. I'd just like to point out that the "biodone: buffer not busy" panic doesn't come from the DPT driver, but may be caused by it calling biodone() on a buffer that the system does not believe is busy. These situations are worth analysing, and I hope to see you and Troy resolving this one, even if it means that you point the finger elsewhere. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message