SCSI and SAN

[Tom Evans]

On Fri, 2007-10-05 at 16:46 +0530, Sharad Chandra wrote:
> Yes, right by analyzing camcontrol devlist it can be told, but i guess not 
> always.
> 
> [root at 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
> 
> Thanks for any suggestion.
> Sharad Chandra
> 
> 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

Hi

As previously suggested, glabel(8) your da devices so you can
distinguish between them. Example:


glabel label -v usr /dev/da2
           newfs /dev/label/usr
           mount /dev/label/usr /usr
           [...]
           umount /glabel stop usr
glabel unload
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: This is a digitally signed message part
Url : http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20071005/f6b57abf/attachment.pgp