From owner-freebsd-current@FreeBSD.ORG  Fri Mar  9 23:03:47 2007
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: freebsd-current@freebsd.org
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 8F3F016A401;
	Fri,  9 Mar 2007 23:03:47 +0000 (UTC)
	(envelope-from mjacob@freebsd.org)
Received: from ns1.feral.com (ns1.feral.com [192.67.166.1])
	by mx1.freebsd.org (Postfix) with ESMTP id 33F5713C428;
	Fri,  9 Mar 2007 23:03:47 +0000 (UTC)
	(envelope-from mjacob@freebsd.org)
Received: from ns1.feral.com (localhost [127.0.0.1])
	by ns1.feral.com (8.13.8/8.13.8) with ESMTP id l29MSp73061518;
	Fri, 9 Mar 2007 14:28:59 -0800 (PST)
	(envelope-from mjacob@freebsd.org)
Received: from localhost (mjacob@localhost)
	by ns1.feral.com (8.13.8/8.13.8/Submit) with ESMTP id l29MSoPO061515;
	Fri, 9 Mar 2007 14:28:51 -0800 (PST)
	(envelope-from mjacob@freebsd.org)
X-Authentication-Warning: ns1.feral.com: mjacob owned process doing -bs
Date: Fri, 9 Mar 2007 14:28:50 -0800 (PST)
From: mjacob@freebsd.org
To: Ivan Voras <ivoras@fer.hr>
In-Reply-To: <45F1C77C.8010103@fer.hr>
Message-ID: <20070309142834.S61513@ns1.feral.com>
References: <esruhl$8s9$1@sea.gmane.org> <45F18183.7050405@FreeBSD.org>
	<45F182F2.10604@fer.hr> <ess83u$j2c$1@sea.gmane.org>
	<70e8236f0703091240q65d45300u836121454d799c64@mail.gmail.com>
	<45F1C77C.8010103@fer.hr>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org,
	Matt Jacob <mjacob@freebsd.org>
Subject: Re: MFC request: QLogic 24xx FibreChannel controller
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: mjacob@freebsd.org
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Mar 2007 23:03:47 -0000


The GEOM multipath code hasn't been MFC'd yet.


On Fri, 9 Mar 2007, Ivan Voras wrote:

> Joao Barros wrote:
>> On 3/9/07, Ivan Voras <ivoras@fer.hr> wrote:
>>> I'm not familiar with this hardware, but I'm curious why I see the one
>>> test drive I assigned to it twice. I seem to recall reading somewhere a
>>> discussion for Linux in which it's been mentioned that one of these
>>> should be a read-write and another "read-only" device, but is this
>>> correct? I can write to both drives.
>>
>> I'd say because you have a multipath setup, the driver being the exception.
>> I guess the in house isp guru Matt Jacob can give you a better
>> explanation ;)
>
> I don't think it's because of multipath (as far as I understand it)
> because both disks are atached to isp0:
>
> da1 at isp0 bus 0 target 0 lun 0
> da2 at isp0 bus 0 target 1 lun 0
>
> There are two FC switches, but AFAIK a multipath setup would have, for
> example one disk coming from isp0 and the other from isp1, as isp0 and
> isp1 are connected to two switches...
>
> It's entirely possible that something's ill defined in the FC management
> console (I din't do it - it's another guy's responsibility :) )
>
>