From owner-freebsd-scsi@FreeBSD.ORG Mon Feb 27 19:59:19 2012 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C403F1065679 for ; Mon, 27 Feb 2012 19:59:19 +0000 (UTC) (envelope-from nitroboost@gmail.com) Received: from mail-tul01m020-f182.google.com (mail-tul01m020-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 771F38FC12 for ; Mon, 27 Feb 2012 19:59:19 +0000 (UTC) Received: by obbwc7 with SMTP id wc7so917668obb.13 for ; Mon, 27 Feb 2012 11:59:18 -0800 (PST) Received-SPF: pass (google.com: domain of nitroboost@gmail.com designates 10.60.3.167 as permitted sender) client-ip=10.60.3.167; Authentication-Results: mr.google.com; spf=pass (google.com: domain of nitroboost@gmail.com designates 10.60.3.167 as permitted sender) smtp.mail=nitroboost@gmail.com; dkim=pass header.i=nitroboost@gmail.com Received: from mr.google.com ([10.60.3.167]) by 10.60.3.167 with SMTP id d7mr6570818oed.20.1330372758955 (num_hops = 1); Mon, 27 Feb 2012 11:59:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=Gc9/cylVcjzzQAnB+Ev0mRB2CoaS35+03Axx+mKVKLQ=; b=M00v3xdFUyWia1pvzo+Rq+NPgONMmE/SdIxvsOjK/T6Zz2aJBnEcx8g7MhdDtTeDF0 knsQedZyk7DvQUFpQkAtuGwmWhkRiwkFvAEIMHXiWgggZgk3yFXnwooElY3NUQxQhXZt 8rjOH1XKWcmbqTIfjIJsK2eC9U299q4P0FAH4= MIME-Version: 1.0 Received: by 10.60.3.167 with SMTP id d7mr5774590oed.20.1330372758879; Mon, 27 Feb 2012 11:59:18 -0800 (PST) Received: by 10.182.29.196 with HTTP; Mon, 27 Feb 2012 11:59:18 -0800 (PST) In-Reply-To: References: <4F450814.4020100@interlog.com> Date: Mon, 27 Feb 2012 12:59:18 -0700 Message-ID: From: Jason Wolfe To: "Desai, Kashyap" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: "freebsd-scsi@freebsd.org" , "McConnell, Stephen" Subject: Re: LSI2008 controller clobbers first disk with new LSI mps driver 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: Mon, 27 Feb 2012 19:59:19 -0000 On Wed, Feb 22, 2012 at 9:11 AM, Desai, Kashyap wro= te: > > >> -----Original Message----- >> From: Douglas Gilbert [mailto:dgilbert@interlog.com] >> Sent: Wednesday, February 22, 2012 8:52 PM >> To: Desai, Kashyap >> Cc: Jason Wolfe; freebsd-scsi@freebsd.org; McConnell, Stephen >> Subject: Re: LSI2008 controller clobbers first disk with new LSI mps >> driver >> >> On 12-02-22 03:39 AM, Desai, Kashyap wrote: >> > Here is a possible root cause of this issue. >> > >> > Enclosure which you are using in your setup (might be) not configured >> properly. >> > >> > You have Enclosure with 12 Slots + 1 SES Device. >> > See below detail from the log. >> > >> > =A0 =A0 EventDataLength: 5 >> > =A0 =A0 AckRequired: 0 >> > =A0 =A0 Event: SasEnclDeviceStatusChange (0x1d) >> > =A0 =A0 EventContext: 0x0 >> > =A0 =A0 EnclosureHandle: 0x2 >> > =A0 =A0 ReasonCode: Added >> > =A0 =A0 PhysicalPort: 0 >> > =A0 =A0 NumSlots: 13 >> > =A0 =A0 StartSlot: 0 >> > =A0 =A0 PhyBits: 0xff >> > >> > StartSlot is 0 in this case. >> > Correct behavior should be each device on your enclosure must have >> different slot number starting from 0 till 12. >> > I have doubt that SES device has not configured well and it is using >> slot-0 as default. This can create issue for actual device which is >> connected to slot-0. >> > So In your setup you will have slot-0 till slot-11 assigned for actual >> Phys of your enclosures and again slot-0 is assigned for SES device >> instead of Slot-12. >> >> No. SAS-2 expanders typically have an integral SES device on an >> expander _virtual_ phy (see SMP DISCOVER (LIST) response). Once >> you see that virtual phy flag the slot number is irrelevant. > > Doug, > > I need some more info so that I can understand your point better. > > I have one Enclosure setup on FreeBSD. Here is smp_discover output. (smp_= discover_list is failing for me) > > phy =A0 0: inaccessible (phy vacant) > =A0phy =A0 1: inaccessible (phy vacant) > =A0phy =A0 2: inaccessible (phy vacant) > =A0phy =A0 3: inaccessible (phy vacant) > =A0phy =A0 4:S:attached:[500605b012345888:03 =A0i(SSP+STP+SMP)] =A06 Gbps > =A0phy =A0 5:S:attached:[500605b012345888:02 =A0i(SSP+STP+SMP)] =A06 Gbps > =A0phy =A0 6:S:attached:[500605b012345888:01 =A0i(SSP+STP+SMP)] =A06 Gbps > =A0phy =A0 7:S:attached:[500605b012345888:00 =A0i(SSP+STP+SMP)] =A06 Gbps > =A0phy =A012:D:attached:[5000c5003bc2c389:00 =A0t(SSP)] =A06 Gbps > =A0phy =A013:D:attached:[500000e116ee91e2:00 =A0t(SSP)] =A06 Gbps > =A0phy =A014:D:attached:[5000c5003bc308e5:00 =A0t(SSP)] =A06 Gbps > =A0phy =A015:D:attached:[5000c5003bc2f0d1:00 =A0t(SSP)] =A06 Gbps > =A0phy =A016:D:attached:[5000c5003bc2ff3d:00 =A0t(SSP)] =A06 Gbps > =A0phy =A017:D:attached:[5000c5003bae5fdd:00 =A0t(SSP)] =A06 Gbps > =A0phy =A018:D:attached:[5000c5003bae5eb1:00 =A0t(SSP)] =A06 Gbps > =A0phy =A019:D:attached:[5000c5003bc2d135:00 =A0t(SSP)] =A06 Gbps > =A0phy =A020:D:attached:[5000c5003baea36d:00 =A0t(SSP)] =A06 Gbps > =A0phy =A021:D:attached:[5000c5003bc2a8c9:00 =A0t(SSP)] =A06 Gbps > =A0phy =A022:D:attached:[5000c5003bc237a9:00 =A0t(SSP)] =A06 Gbps > =A0phy =A023:D:attached:[5000c5003bc2cec1:00 =A0t(SSP)] =A06 Gbps > =A0phy =A024:D:attached:[500000e01d92cb52:00 =A0t(SSP)] =A03 Gbps > =A0phy =A025:D:attached:[500000e01d74cfb2:00 =A0t(SSP)] =A03 Gbps > =A0phy =A026:D:attached:[500000e01d656052:00 =A0t(SSP)] =A03 Gbps > =A0phy =A027:D:attached:[500000e01d7cad52:00 =A0t(SSP)] =A03 Gbps > =A0phy =A028:D:attached:[500c04f2b64cdd1c:00 =A0t(SATA)] =A03 Gbps > =A0phy =A029:D:attached:[500c04f2b64cdd1d:00 =A0t(SATA)] =A03 Gbps > =A0phy =A030:D:attached:[500000e01d73c262:00 =A0t(SSP)] =A03 Gbps > =A0phy =A031:D:attached:[500000e01d536b22:00 =A0t(SSP)] =A03 Gbps > =A0phy =A032:D:attached:[500000e01d92cab2:00 =A0t(SSP)] =A03 Gbps > =A0phy =A033:D:attached:[500000e01afd8792:00 =A0t(SSP)] =A03 Gbps > =A0phy =A034:D:attached:[5000c5003bc30301:00 =A0t(SSP)] =A06 Gbps > =A0phy =A035:D:attached:[5000c5003bb09a69:00 =A0t(SSP)] =A06 Gbps > =A0phy =A036:D:attached:[500c04f2b64cdd3d:00 =A0V i(SSP) t(SSP)] =A06 Gbp= s =A0 <--- This has virtual phy set. > > What I understood from your explanation is if we have virt_phy field set,= we should not trust slot for that entry. > You are suggesting to use phy index instead of slot. Just for info: But h= ow to see Slot details mapping with phy ? > > ~ Kashyap > >> >> Doug Gilbert Kashyap, Let me know if there are any changes agreed upon, I'm happy to test out patches as this is affecting a large number of our machines. I can only imagine the same for others as they start to upgrade, as this is standard SuperMicro hardware. Thanks, Jason