From owner-freebsd-hackers@FreeBSD.ORG Fri Oct 5 12:53:27 2007 Return-Path: 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 68E7216A418; Fri, 5 Oct 2007 12:53:27 +0000 (UTC) (envelope-from sharadc@in.niksun.com) Received: from in.niksun.com (210.18.76.166.sify.net [210.18.76.166]) by mx1.freebsd.org (Postfix) with ESMTP id 018E413C48A; Fri, 5 Oct 2007 12:53:26 +0000 (UTC) (envelope-from sharadc@in.niksun.com) Received: from sharadc.in.niksun.com (unknown [10.60.5.27]) by in.niksun.com (Postfix) with ESMTP id 376635DE9; Fri, 5 Oct 2007 18:31:29 +0530 (IST) From: Sharad Chandra Organization: NIKSUN To: Tom Evans Date: Fri, 5 Oct 2007 18:20:17 +0530 User-Agent: KMail/1.9.4 References: <200710041725.00842.sharadc@in.niksun.com> <1191584622.1475.86.camel@localhost> <1191584942.1475.92.camel@localhost> In-Reply-To: <1191584942.1475.92.camel@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200710051820.17587.sharadc@in.niksun.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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Oct 2007 12:53:27 -0000 That's very right, but it needs a manual setup. Whereas I need to work on storage disks attached to system, to accomplish that i have to write a script and know in itself whether it is attached to SAN or not. I know mainly there are "sysctl kern.disks" storage attached to system, nothing else. Thanks Sharad Chandra On Friday 05 October 2007 5:19 pm, Tom Evans wrote: > On Fri, 2007-10-05 at 12:43 +0100, Tom Evans wrote: > .... > > Excuse the formatting, my keyboard went nuts and decided I was done > editing :o > > In addition to the example I showed, I was just going to say that the > purpose of glabel is to stop referring to /dev/da[0-9]* and instead be > able to refer to /dev/label/san_0_lun_0 (or whatever you like). I don't > know of a way to automagically determine if a disk is in fact a SAN, but > it cannot be too hard to figure out from dmesg + information about the > disk. > > Once you have identified it LABEL IT! Then there is no more ambiguity. > > Regards > > Tom