From owner-freebsd-questions@freebsd.org Mon Dec 7 19:18:39 2015 Return-Path: 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 E45B59D26EB for ; Mon, 7 Dec 2015 19:18:39 +0000 (UTC) (envelope-from pallav_bose@yahoo.com) Received: from nm44-vm10.bullet.mail.gq1.yahoo.com (nm44-vm10.bullet.mail.gq1.yahoo.com [67.195.87.215]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BE1161A40 for ; Mon, 7 Dec 2015 19:18:39 +0000 (UTC) (envelope-from pallav_bose@yahoo.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1449515758; bh=JCLFujSz/dPoX1R03eSkXOR7z6keHuFndH2bFReQQ8s=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject; b=nhtBgTzSs74HjT5u5EKNd6upl/L7Of/hJti9AR6dehwGpAxKwwt18z+8PQeMhViauNm0dXupDBWhPAu60jJh6IE33Ty1i4h9im9sUr6CTyoT9IgVxDRd4LXYCuIk/sr8K2vFf5y3wofXYiGBCpvH3t08i7i5pZbMUw3RA1W8ad8mFbtvsk9ht7IZDNfanT3hVmwnrA1yFtUyCieH3fGamOkmoBbCYuBhBdXa3LvgEjmNQpF16gCDq49VdZKgB+6xO71QXYQ27bB0Zkk1CopIiEXOZoESaMuth3RtBZZ+JPmCw9brimaIDaIKbIrz75E6g4E5KY2jVVPqtqVa1fEZjA== Received: from [127.0.0.1] by nm44.bullet.mail.gq1.yahoo.com with NNFMP; 07 Dec 2015 19:15:58 -0000 Received: from [98.137.12.59] by nm44.bullet.mail.gq1.yahoo.com with NNFMP; 07 Dec 2015 19:12:57 -0000 Received: from [98.137.12.193] by tm4.bullet.mail.gq1.yahoo.com with NNFMP; 07 Dec 2015 19:12:57 -0000 Received: from [127.0.0.1] by omp1001.mail.gq1.yahoo.com with NNFMP; 07 Dec 2015 19:12:57 -0000 X-Yahoo-Newman-Property: ymail-4 X-Yahoo-Newman-Id: 260623.80430.bm@omp1001.mail.gq1.yahoo.com X-YMail-OSG: Fe5_VqMVM1m_lNPCpw5ig8erHdW3yZ20Oj4InjK1TmVu9FyswL3jkH9ysP7raQl f1WN2Vjbd3mJcXXJ7zDu3H26Lm8q8wKhFVVI3aBpLbKHHxCefu4vQOmPjHtTvdeWpZ6rORRHvEWG X29sBnGmvWQ9CWiS4cySZOfthdPa.Bica5onhhXpMvs5iJdfyd8Rer43AFq3XVNaB2q0fISGgywD IGvI9ck6BNRuQ7rldUurT669BrWM51NY4E0FJ1Taik99CnvkLJXN_Cwnz1lO701xSyO8MGAsx0SO 3TZ9uOISaG6oAZj3bt.tK6omfSkzZokLj9pk8pzCQIkLYDT2UPFLoHMnFi80Bdxbe0C_TfCkoCtP c.jqXgFZLccK74ThptYd_3CtBui3KAyBmfLpOxL7CLXY3cmIxeN7hMLgAJEIGUFXhF8KIFSg41XM r4qkQpGUd5PbbwliyhqluJdCl_7eADD6RWD3kRgMqFcyQYb0Zk1HbzUQVoc8mU5qYFBnijD61JMQ Y9FMWhB3LLVev5x2CMjlTPA-- Received: by 216.39.60.209; Mon, 07 Dec 2015 19:12:56 +0000 Date: Mon, 7 Dec 2015 19:12:55 +0000 (UTC) From: Pallav Bose Reply-To: Pallav Bose To: Polytropon Cc: "freebsd-questions@freebsd.org" Message-ID: <1898250304.15775171.1449515575563.JavaMail.yahoo@mail.yahoo.com> In-Reply-To: <20151205012052.77256a47.freebsd@edvax.de> References: <20151205012052.77256a47.freebsd@edvax.de> Subject: Re: Meaning behind target ID in the output of camcontrol and MegaCli MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Dec 2015 19:18:40 -0000 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 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 =C2=A0 =C2=A0 at scbus0 target 0 lun 0 (pass= 0,cd0) =C2=A0 =C2=A0 =C2=A0 =C2=A0 at scbus3 target 0 lu= n 0 (da0,pass1) =C2=A0 =C2=A0 =C2=A0 at scbus3 target 0 lun 1 = (da1,pass2) =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 > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0 at scbus0 target 0 lun 0 (pass0,da0) > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0 at scbus0 target 1 lun 0 (pass1,da1) > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0 at scbus0 target 2 lun 0 (pass2,da2) > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0 at scbus0 target 3 lun 0 (pass3,da3) > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0 at scbus0 target 4 lun 0 (pass4,da4) > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0 at scbus0 target 5 lun 0 (pass5,da5) > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0 at scbus0 target 6 lun 0 (pass6,da6) > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0 at scbus0 target 7 lun 0 (pass7,da7) > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0 at scbus0 target 8 lun 0 (pass8,da8) > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0 at scbus0 target 9 lun 0 (pass9,da9) > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0 at scbus0 target 10 lun 0 (pass10,da10) > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0 at scbus0 target 11 lun 0 (pass11,da11) > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0 at scbus0 target 12 lun 0 (pass12,da12) > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0 at scbus0 target 13 lun 0 (pass13,da13) > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0 at scbus0 target 14 lun 0 (pass14,da14) > =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) > =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) > =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: 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 ; 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 ; Mon, 7 Dec 2015 19:21:17 +0000 (UTC) (envelope-from will.senn@gmail.com) Received: by qkdb5 with SMTP id b5so37614320qkd.0 for ; 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 (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: <86poyiuynx.fsf@gmail.com> <56659FC8.8020904@FreeBSD.org> <5665A68C.40007@ravexdata.com> From: Will Senn 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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