Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 7 Dec 2015 19:12:55 +0000 (UTC)
From:      Pallav Bose <pallav_bose@yahoo.com>
To:        Polytropon <freebsd@edvax.de>
Cc:        "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org>
Subject:   Re: Meaning behind target ID in the output of camcontrol and MegaCli
Message-ID:  <1898250304.15775171.1449515575563.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To: <20151205012052.77256a47.freebsd@edvax.de>
References:  <20151205012052.77256a47.freebsd@edvax.de>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
Thank you for replying, Polytropon. Given that my setup has exactly one LUN=
 per target, the mapping from MegaCli to camcontrol - [adapter,slot,target =
ID] =3D> [adapter,target ID,device name] is accurate? And device enumeratio=
n is stored in the RAID controllers' firmware?=C2=A0Regards,Pallav=20


    On Friday, December 4, 2015 4:20 PM, Polytropon <freebsd@edvax.de> wrot=
e:
=20

 On Fri, 4 Dec 2015 22:29:28 +0000 (UTC), Pallav Bose via freebsd-questions=
 wrote:
> My understanding is that the target ID links a disk in a particular
> slot on a particular adapter to its device name. This can be gathered
> from the MegaCli configuration output above and the camcontrol output
> below. MegaCli gives us the 3-tuple [adapter,slot,target ID] and
> camcontrol gives us the 3-tuple [adapter,target ID,device name]. So,
> I now know what device name does a physical disk (configured as a
> RAID 0) in a particular slot on a particular adapter map to.

The numbering B:T:L (or B:T:U) is typical regarding how SCSI
enumerates devices. B is the bus number, T the target number
(the device on that bus), and L is the LUN (logical unit number)
depending on the device, which can have more than one "unit"
(slot, drive, whatever).

In ye olden times one SCSI bus could have up to 8 devices,
numbered 0 - 6, and 7 being the controller itself. The number
of a device ("target") usually was configured via jumpers on
that device.

Today, ATA and SATA, as well as other mass storage means, have
adopted CAM ("SCSI language"), so some terminology is still
being used. But device enumeration isn't coded in hardware
anymore. Modern SCSI BIOSs typically do that in firmware.

See this for example:

% camcontrol devlist
<HL-DT-ST DVDRAM GSA-H42N RL00>=C2=A0 =C2=A0 at scbus0 target 0 lun 0 (pass=
0,cd0)
<Generic Flash HS-CF 4.55>=C2=A0 =C2=A0 =C2=A0 =C2=A0 at scbus3 target 0 lu=
n 0 (da0,pass1)
<Generic Flash HS-MS/SD 4.55>=C2=A0 =C2=A0 =C2=A0 at scbus3 target 0 lun 1 =
(da1,pass2)
<Generic Flash HS-SM 4.55>=C2=A0 =C2=A0 =C2=A0 =C2=A0 at scbus3 target 0 lu=
n 2 (da2,pass3)

As you can see, there are a bus 0 and bus 3, each with only one
device, but target 3:0 has three LUNs.

In your case, it's a lot easier:

> # camcontrol devlist
> <DELL PERC H730 Mini 4.25>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0 at scbus0 target 0 lun 0 (pass0,da0)
> <DELL PERC H730 Mini 4.25>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0 at scbus0 target 1 lun 0 (pass1,da1)
> <DELL PERC H730 Mini 4.25>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0 at scbus0 target 2 lun 0 (pass2,da2)
> <DELL PERC H730 Mini 4.25>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0 at scbus0 target 3 lun 0 (pass3,da3)
> <DELL PERC H730 Mini 4.25>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0 at scbus0 target 4 lun 0 (pass4,da4)
> <DELL PERC H730 Mini 4.25>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0 at scbus0 target 5 lun 0 (pass5,da5)
> <DELL PERC H730 Mini 4.25>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0 at scbus0 target 6 lun 0 (pass6,da6)
> <DELL PERC H730 Mini 4.25>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0 at scbus0 target 7 lun 0 (pass7,da7)
> <DELL PERC H730 Mini 4.25>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0 at scbus0 target 8 lun 0 (pass8,da8)
> <DELL PERC H730 Mini 4.25>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0 at scbus0 target 9 lun 0 (pass9,da9)
> <DELL PERC H730 Mini 4.25>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0 at scbus0 target 10 lun 0 (pass10,da10)
> <DELL PERC H730 Mini 4.25>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0 at scbus0 target 11 lun 0 (pass11,da11)
> <DELL PERC H730 Mini 4.25>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0 at scbus0 target 12 lun 0 (pass12,da12)
> <DELL PERC H730 Mini 4.25>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0 at scbus0 target 13 lun 0 (pass13,da13)
> <DELL PERC H730 Mini 4.25>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0 at scbus0 target 14 lun 0 (pass14,da14)
> <DELL PERC H830 Adp 4.25>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 at scbus2 target 0 lun 0 (pass15,da15)
> <DELL PERC H830 Adp 4.25>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 at scbus2 target 1 lun 0 (pass16,da16)
> <Kingston DataTraveler 3.0 PMAP>=C2=A0=C2=A0 at scbus4 target 0 lun 0 (da=
17,pass17)

Bus 0 with 15 targets, each with one LUN, and bus 2 with two of
them. They represent two "SCSI adapters", each one representing
a disk as a _single_ target (with one LUN). It could have been
a different setup, for example, one target per four disks with
LUNs 0 - 3...



--=20
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...

  
From owner-freebsd-questions@freebsd.org  Mon Dec  7 19:21:17 2015
Return-Path: <owner-freebsd-questions@freebsd.org>
Delivered-To: freebsd-questions@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9BB849D2BF5
 for <freebsd-questions@mailman.ysv.freebsd.org>;
 Mon,  7 Dec 2015 19:21:17 +0000 (UTC)
 (envelope-from will.senn@gmail.com)
Received: from mail-qk0-x229.google.com (mail-qk0-x229.google.com
 [IPv6:2607:f8b0:400d:c09::229])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 587BB1FBE
 for <freebsd-questions@freebsd.org>; Mon,  7 Dec 2015 19:21:17 +0000 (UTC)
 (envelope-from will.senn@gmail.com)
Received: by qkdb5 with SMTP id b5so37614320qkd.0
 for <freebsd-questions@freebsd.org>; Mon, 07 Dec 2015 11:21:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=subject:to:references:from:message-id:date:user-agent:mime-version
 :in-reply-to:content-type:content-transfer-encoding;
 bh=IXucdrNkaOaKzJs4p4Wla5xJanQLkWxBAHDFM6cvEDY=;
 b=p9qgdVZud+GYST60t+uBmFauwQz6p9+F60gGkQU8ysrWmjOQc+qiJ8E0H1WV8lED6S
 GMlahkoiIuEoS9bItoecVsoxyoOMeFcgGNsQbZKbo3LstNtoZjHYk6ScUM2mkoaD9q9u
 Su+rqJ88ADSstnzaY91UhuWoIjHxceYpWLq+GsdF3GtejlvlIo/D3a0uKH8/mhF1Hz/8
 5p0ftCXLWPLFpp9f7glXwJ0sFq2Otz8kvU61P2tY8hXOWU3sSi/HNxdofchhc6C8FN2P
 j3n/v1AksOiR/16nfDfCOHmfcfXoBCIQMWRHSjUpIhCcQWIPDddkEktD277tDoCO2mpM
 sc7g==
X-Received: by 10.129.153.148 with SMTP id q142mr23065194ywg.260.1449516076203; 
 Mon, 07 Dec 2015 11:21:16 -0800 (PST)
Received: from [192.168.0.4] ([206.251.219.82])
 by smtp.gmail.com with ESMTPSA id i204sm19805912ywb.9.2015.12.07.11.21.15
 for <freebsd-questions@freebsd.org>
 (version=TLSv1/SSLv3 cipher=OTHER);
 Mon, 07 Dec 2015 11:21:15 -0800 (PST)
Subject: Re: Migrating to FreeBSD from Debian
To: freebsd-questions@freebsd.org
References: <CAO-kBwffucnPVphm_ajbtAejjFiAv_Cp+v7jZ-xCTX7YTqk36w@mail.gmail.com>
 <86poyiuynx.fsf@gmail.com>
 <CAA2O=b_p-HPx+pPyFOgJMe02d5xrJe_aXJ8ZG9z+dHZCNwh91Q@mail.gmail.com>
 <56659FC8.8020904@FreeBSD.org>
 <CAA2O=b-dQMpnq=nJ6RMSvwBCa4kP4PB2k4c7nbTVrwtQkzStBg@mail.gmail.com>
 <5665A68C.40007@ravexdata.com>
From: Will Senn <will.senn@gmail.com>
Message-ID: <5665DC2A.4070801@gmail.com>
Date: Mon, 7 Dec 2015 13:21:14 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0)
 Gecko/20100101 Thunderbird/38.4.0
MIME-Version: 1.0
In-Reply-To: <5665A68C.40007@ravexdata.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>;
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Dec 2015 19:21:17 -0000


On 12/7/15 9:32 AM, Paul Stuffins wrote:
>> But we should warn then about not mixing ports & packages. I agree,
>> pkg is a good choice [when pkg only].
> I have not set up the system yet, so there is no worry about mixing 
> ports and packages from the off.

As a fellow Debian user turned FreeBSD user, I just use pkg unless I 
need something exotic.  In my view, pkg serves the same basic function 
and it's even simpler to use than apt-get (hard to believe, I know). I 
have to admit that both Debian's flavor of Linux and FreeBSD are similar 
in terms capability and of being rock solid, but I truly appreciate 
FreeBSD's  approach to documentation and community over Debian's. This 
combined with an operating system that is more coherent that most of the 
Linuxes out there, even Debian (a significant userland is part of the OS 
as opposed to separately packaged) has made the experience of switching 
a very positive one, but not a painless one (printing, in particular was 
challenging).

-will



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?1898250304.15775171.1449515575563.JavaMail.yahoo>