From owner-freebsd-scsi@FreeBSD.ORG Wed Sep 19 20:07:56 2012 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 35C64106564A for ; Wed, 19 Sep 2012 20:07:56 +0000 (UTC) (envelope-from jas@cse.yorku.ca) Received: from bronze.cs.yorku.ca (bronze.cs.yorku.ca [130.63.95.34]) by mx1.freebsd.org (Postfix) with ESMTP id 021C08FC0A for ; Wed, 19 Sep 2012 20:07:55 +0000 (UTC) Received: from [130.63.97.125] (ident=jas) by bronze.cs.yorku.ca with esmtp (Exim 4.76) (envelope-from ) id 1TEQYm-00078l-Rl for freebsd-scsi@freebsd.org; Wed, 19 Sep 2012 16:07:48 -0400 Message-ID: <505A2614.2000709@cse.yorku.ca> Date: Wed, 19 Sep 2012 16:07:48 -0400 From: Jason Keltz User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:10.0.7) Gecko/20120824 Thunderbird/10.0.7 MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: -1.0 X-Spam-Level: - X-Spam-Report: Content preview: I have a Dell R720 and a 24 x 2.5" Dell MD1220 JBOD. I have added dual LSI 9205-8e, each connected to the same MD1220 array. Under FreeBSD 9.0, if I do a "camcontrol devlist" (with every other disk removed), I see: [...] Content analysis details: (-1.0 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 SHORTCIRCUIT Not all rules were run, due to a shortcircuited rule -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP Subject: mps target difference between FreeBSD 9 and 9.1 RC X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Sep 2012 20:07:56 -0000 I have a Dell R720 and a 24 x 2.5" Dell MD1220 JBOD. I have added dual LSI 9205-8e, each connected to the same MD1220 array. Under FreeBSD 9.0, if I do a "camcontrol devlist" (with every other disk removed), I see: at scbus0 target 0 lun 0 (pass0,da0) at scbus0 target 2 lun 0 (pass1,da1) at scbus0 target 4 lun 0 (pass2,da2) at scbus0 target 6 lun 0 (pass3,da3) at scbus0 target 8 lun 0 (pass4,da4) at scbus0 target 10 lun 0 (pass5,da5) at scbus0 target 36 lun 0 (pass6,ses0) at scbus1 target 12 lun 0 (pass7,da6) at scbus1 target 14 lun 0 (pass8,da7) at scbus1 target 16 lun 0 (pass9,da8) at scbus1 target 18 lun 0 (pass10,da9) at scbus1 target 21 lun 0 (pass11,da10) at scbus1 target 22 lun 0 (pass12,da11) at scbus1 target 36 lun 0 (pass13,ses1) at scbus6 target 0 lun 0 (pass14,cd0) ... which is what I would expect. If I do the same thing with any pre-release/RC version of 9.1, I see: at scbus0 target 34 lun 0 (pass0,da0) at scbus0 target 36 lun 0 (pass1,da1) at scbus0 target 38 lun 0 (pass2,da2) at scbus0 target 39 lun 0 (pass3,da3) at scbus0 target 41 lun 0 (pass4,da4) at scbus0 target 43 lun 0 (pass5,da5) at scbus0 target 45 lun 0 (ses0,pass6) at scbus1 target 21 lun 0 (pass7,da6) at scbus1 target 23 lun 0 (pass8,da7) at scbus1 target 24 lun 0 (pass9,da8) at scbus1 target 26 lun 0 (pass10,da9) at scbus1 target 29 lun 0 (pass11,da10) at scbus1 target 31 lun 0 (pass12,da11) at scbus1 target 32 lun 0 (ses1,pass13) at scbus6 target 0 lun 0 (pass14,cd0) In particular, note how the targets are starting at 34. I wonder if someone might explain why? I was considering using /boot/device.hints to hard-code the daX mapping to avoid the use of "labels" for my volumes, but I wouldn't expect the targets to change between the two releases. Thanks for any information that you can provide.. Jason.