From owner-freebsd-drivers@FreeBSD.ORG Mon Sep 22 23:24:26 2008 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 33B6E1065671 for ; Mon, 22 Sep 2008 23:24:26 +0000 (UTC) (envelope-from sbruno@miralink.com) Received: from plato.miralink.com (mail.miralink.com [70.103.185.20]) by mx1.freebsd.org (Postfix) with ESMTP id 08D2F8FC0C for ; Mon, 22 Sep 2008 23:24:18 +0000 (UTC) (envelope-from sbruno@miralink.com) Received: from localhost (localhost.localdomain [127.0.0.1]) by plato.miralink.com (Postfix) with ESMTP id A220D1A9101; Mon, 22 Sep 2008 16:20:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at X-Spam-Flag: NO X-Spam-Score: -4.399 X-Spam-Level: X-Spam-Status: No, score=-4.399 tagged_above=-10 required=6.6 tests=[ALL_TRUSTED=-1.8, BAYES_00=-2.599] Received: from plato.miralink.com ([127.0.0.1]) by localhost (plato.miralink.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u9KlxhWgi3vv; Mon, 22 Sep 2008 16:20:00 -0700 (PDT) Received: from [10.0.0.40] (iago.office.miralink.com [10.0.0.40]) by plato.miralink.com (Postfix) with ESMTP id 318871A90E4; Mon, 22 Sep 2008 16:20:00 -0700 (PDT) Message-ID: <48D82921.3010904@miralink.com> Date: Mon, 22 Sep 2008 16:24:17 -0700 From: Sean Bruno User-Agent: Thunderbird 2.0.0.16 (X11/20080723) MIME-Version: 1.0 To: Dieter References: <200809222203.WAA20882@sopwith.solgatos.com> In-Reply-To: <200809222203.WAA20882@sopwith.solgatos.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-drivers@freebsd.org Subject: Re: [RELENG_6] ATARAID oddity X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Sep 2008 23:24:26 -0000 Dieter wrote: >> I.e. if you insert a drive that was part of a volume from an Adaptec >> RAID controller into another system, the new system will attempt to >> treat that disk as though it were associated with a HOST Raid controller. >> >> I don't think that this is the desired behavior. Even if the host raid >> meta-data is detected, the system shouldn't attempt to treat the disk as >> part of a HOST raid set without the appropriate controller in the system. >> > > Even if there *is* an appropriate controller in the system, presumably it > isn't going to work unless the disk is connected to that controller. > > We want the ability to migrate a disk from Adaptec to some other > controller without screwy things happening. > _______________________________________________ Looking over the ata-raid.c code that controls the detection, it's pretty obvious that it doesn't check to see if the disk belongs to a controller. Moreover it blindly tries to use ANY drive in the system(LSI will do this as well) if it detects meta data. I'm working on a simple patch for this, but I need to figure out which cards are using the Adaptec metadata format. Any ideas where I should look? I seem to have 1 card available(3010S) that I can validate against. -- Sean Bruno MiraLink Corporation 6015 NE 80th Ave, Ste 100 Portland, OR 97218 Phone 503-621-5143 Fax 503-621-5199 MSN: sbruno@miralink.com Google: seanwbruno@gmail.com Yahoo: sean_bruno@yahoo.com