From owner-freebsd-current Mon Sep 21 21:41:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA13232 for freebsd-current-outgoing; Mon, 21 Sep 1998 21:41:54 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA13226 for ; Mon, 21 Sep 1998 21:41:46 -0700 (PDT) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.7/8.8.5) with ESMTP id WAA05997; Mon, 21 Sep 1998 22:40:07 -0600 (MDT) Message-Id: <199809220440.WAA05997@pluto.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Robert Crowe cc: "Justin T. Gibbs" , Robert Crowe , current@FreeBSD.ORG, bob@carlsbad.ipinc.com Subject: Re: Problems with DPT/CAM and RAIDed drives under 3.0-CURRENT In-reply-to: Your message of "Mon, 21 Sep 1998 14:42:25 PDT." <199809212142.OAA09587@osomil.carlsbad.ipinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 21 Sep 1998 22:33:40 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I can't reproduce it right now (machine is in use), but it seems like about >20 or so seconds after the npx0 probe. It could have been 60, but it didn't >seem like it. My RAID 5 volume worked fine. I decided to try out a RAID 1 configuration and sure enough, it failed as you described. After several hours of going through the DPT driver code trying to determine what was wrong I stumbled upon the unexpected. DPT RAID 1 volumes cannot handle multi-lun probes. Further, they won't tolerate requests for device serial numbers. Why it is that the RAID 5 volumes are immune to this, I have no idea, but I would not have expected this kind of behavior from products built by a company claiming to be the world leader of SCSI RAID technology. I'll be checking in a DPT quirk entry shortly. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message