From owner-freebsd-hackers@FreeBSD.ORG  Fri Oct  5 11:55:13 2007
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id CD05616A419
	for <freebsd-hackers@freebsd.org>; Fri,  5 Oct 2007 11:55:13 +0000 (UTC)
	(envelope-from anderson@freebsd.org)
Received: from ns.trinitel.com (186.161.36.72.static.reverse.ltdomains.com
	[72.36.161.186])
	by mx1.freebsd.org (Postfix) with ESMTP id 90BE013C47E
	for <freebsd-hackers@freebsd.org>; Fri,  5 Oct 2007 11:55:13 +0000 (UTC)
	(envelope-from anderson@freebsd.org)
Received: from proton.storspeed.com (209-163-168-124.static.twtelecom.net
	[209.163.168.124]) (authenticated bits=0)
	by ns.trinitel.com (8.14.1/8.14.1) with ESMTP id l95BtAPq032970;
	Fri, 5 Oct 2007 06:55:12 -0500 (CDT)
	(envelope-from anderson@freebsd.org)
Message-ID: <4706261B.1050202@freebsd.org>
Date: Fri, 05 Oct 2007 06:55:07 -0500
From: Eric Anderson <anderson@freebsd.org>
User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728)
MIME-Version: 1.0
To: Sharad Chandra <sharadc@in.niksun.com>
References: <200710041725.00842.sharadc@in.niksun.com>
	<4704E8F1.8070000@freebsd.org>
	<200710051646.17618.sharadc@in.niksun.com>
In-Reply-To: <200710051646.17618.sharadc@in.niksun.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00 autolearn=ham
	version=3.1.8
X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on ns.trinitel.com
Cc: freebsd-hackers@freebsd.org
Subject: Re: SCSI and SAN
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Oct 2007 11:55:13 -0000

Sharad Chandra wrote:
 > On Thursday 04 October 2007 6:51 pm, Eric Anderson wrote:
 >> Sharad Chandra wrote:
 >>> Hello,
 >>>
 >>> 	How to distinguish if /dev/da* devices are internal scsi drivers 
or LUNs
 >>> of external SAN?
 >> camcontrol devlist -v
 >>
 >> Might help you..
 >>
 >> Eric

> Yes, right by analyzing camcontrol devlist it can be told, but i guess not 
> always.
> 
> [root@qa7 ~]# camcontrol devlist
> <IFT A16F-G2422 348C>              at scbus0 target 0 lun 0 (da0,pass0)
> <IFT A16F-G2422 348C>              at scbus0 target 0 lun 1 (da1,pass1)
> <IFT A16F-G2422 348C>              at scbus0 target 0 lun 2 (da2,pass2)
> <IFT A16F-G2422 348C>              at scbus0 target 0 lun 3 (da3,pass3)
> 
> Here luns are increasing, so it is SAN confirmed by tool. Now my point is if i 
> have a SAN of less than 1TB and i make only 1 LUN. what should be output?
> guessing: similar to
> <IFT A16F-G2422 348C>              at scbus0 target 0 lun 0 (da0,pass0)
> 
> Then it will be difficult to tell, whether it is regular SCSI drives or SAN. 
> Then we need a tool that can tell this da0 belongs to SAN/SCSI or not

Notice the -v to camcontrol.  It will tell you which controller the 
device belongs to, and the controller will help you determine whether it 
is connected to a SAN or not.

Other than that, I'm not sure of the distinction that could be made 
between the devices whether it is on a SAN or not.  It could be a 
directly connected fiber channel device, in which case, it isn't quite a 
SAN, yet the FreeBSD system doesn't know (or care) how it's connected.

Eric