Date: Fri, 5 Oct 2007 18:20:17 +0530 From: Sharad Chandra <sharadc@in.niksun.com> To: Tom Evans <tevans.uk@googlemail.com> Cc: freebsd-hackers@freebsd.org Subject: Re: SCSI and SAN Message-ID: <200710051820.17587.sharadc@in.niksun.com> In-Reply-To: <1191584942.1475.92.camel@localhost> References: <200710041725.00842.sharadc@in.niksun.com> <1191584622.1475.86.camel@localhost> <1191584942.1475.92.camel@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200710051820.17587.sharadc>