From owner-freebsd-scsi@FreeBSD.ORG Wed Feb 22 16:11:32 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 1C3F7106566B for ; Wed, 22 Feb 2012 16:11:32 +0000 (UTC) (envelope-from Kashyap.Desai@lsi.com) Received: from na3sys009aog112.obsmtp.com (na3sys009aog112.obsmtp.com [74.125.149.207]) by mx1.freebsd.org (Postfix) with ESMTP id 6ED258FC15 for ; Wed, 22 Feb 2012 16:11:31 +0000 (UTC) Received: from paledge01.lsi.com ([192.19.193.42]) (using TLSv1) by na3sys009aob112.postini.com ([74.125.148.12]) with SMTP ID DSNKT0UTsmGGOVGdNSLkoVKqlSkPYmYDyUMr@postini.com; Wed, 22 Feb 2012 08:11:31 PST Received: from PALHUB01.lsi.com (128.94.213.114) by PALEDGE01.lsi.com (192.19.193.42) with Microsoft SMTP Server (TLS) id 8.3.213.0; Wed, 22 Feb 2012 11:16:17 -0500 Received: from inbexch01.lsi.com (135.36.98.37) by PALHUB01.lsi.com (128.94.213.114) with Microsoft SMTP Server (TLS) id 8.3.213.0; Wed, 22 Feb 2012 11:11:29 -0500 Received: from inbmail01.lsi.com ([135.36.98.64]) by inbexch01.lsi.com ([135.36.98.37]) with mapi; Wed, 22 Feb 2012 21:41:26 +0530 From: "Desai, Kashyap" To: "dgilbert@interlog.com" Date: Wed, 22 Feb 2012 21:41:24 +0530 Thread-Topic: LSI2008 controller clobbers first disk with new LSI mps driver Thread-Index: AczxdbxHk8vJsdAURXuOqVBjaEt5EQABljag Message-ID: References: <4F450814.4020100@interlog.com> In-Reply-To: <4F450814.4020100@interlog.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 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: Wed, 22 Feb 2012 16:11:32 -0000 > -----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 >=20 > 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. > > > > EventDataLength: 5 > > AckRequired: 0 > > Event: SasEnclDeviceStatusChange (0x1d) > > EventContext: 0x0 > > EnclosureHandle: 0x2 > > ReasonCode: Added > > PhysicalPort: 0 > > NumSlots: 13 > > StartSlot: 0 > > 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. >=20 > 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_di= scover_list is failing for me) phy 0: inaccessible (phy vacant) phy 1: inaccessible (phy vacant) phy 2: inaccessible (phy vacant) phy 3: inaccessible (phy vacant) phy 4:S:attached:[500605b012345888:03 i(SSP+STP+SMP)] 6 Gbps phy 5:S:attached:[500605b012345888:02 i(SSP+STP+SMP)] 6 Gbps phy 6:S:attached:[500605b012345888:01 i(SSP+STP+SMP)] 6 Gbps phy 7:S:attached:[500605b012345888:00 i(SSP+STP+SMP)] 6 Gbps phy 12:D:attached:[5000c5003bc2c389:00 t(SSP)] 6 Gbps phy 13:D:attached:[500000e116ee91e2:00 t(SSP)] 6 Gbps phy 14:D:attached:[5000c5003bc308e5:00 t(SSP)] 6 Gbps phy 15:D:attached:[5000c5003bc2f0d1:00 t(SSP)] 6 Gbps phy 16:D:attached:[5000c5003bc2ff3d:00 t(SSP)] 6 Gbps phy 17:D:attached:[5000c5003bae5fdd:00 t(SSP)] 6 Gbps phy 18:D:attached:[5000c5003bae5eb1:00 t(SSP)] 6 Gbps phy 19:D:attached:[5000c5003bc2d135:00 t(SSP)] 6 Gbps phy 20:D:attached:[5000c5003baea36d:00 t(SSP)] 6 Gbps phy 21:D:attached:[5000c5003bc2a8c9:00 t(SSP)] 6 Gbps phy 22:D:attached:[5000c5003bc237a9:00 t(SSP)] 6 Gbps phy 23:D:attached:[5000c5003bc2cec1:00 t(SSP)] 6 Gbps phy 24:D:attached:[500000e01d92cb52:00 t(SSP)] 3 Gbps phy 25:D:attached:[500000e01d74cfb2:00 t(SSP)] 3 Gbps phy 26:D:attached:[500000e01d656052:00 t(SSP)] 3 Gbps phy 27:D:attached:[500000e01d7cad52:00 t(SSP)] 3 Gbps phy 28:D:attached:[500c04f2b64cdd1c:00 t(SATA)] 3 Gbps phy 29:D:attached:[500c04f2b64cdd1d:00 t(SATA)] 3 Gbps phy 30:D:attached:[500000e01d73c262:00 t(SSP)] 3 Gbps phy 31:D:attached:[500000e01d536b22:00 t(SSP)] 3 Gbps phy 32:D:attached:[500000e01d92cab2:00 t(SSP)] 3 Gbps phy 33:D:attached:[500000e01afd8792:00 t(SSP)] 3 Gbps phy 34:D:attached:[5000c5003bc30301:00 t(SSP)] 6 Gbps phy 35:D:attached:[5000c5003bb09a69:00 t(SSP)] 6 Gbps phy 36:D:attached:[500c04f2b64cdd3d:00 V i(SSP) t(SSP)] 6 Gbps <--- = This has virtual phy set. What I understood from your explanation is if we have virt_phy field set, w= e should not trust slot for that entry. You are suggesting to use phy index instead of slot. Just for info: But how= to see Slot details mapping with phy ? ~ Kashyap >=20 > Doug Gilbert