From owner-freebsd-scsi@freebsd.org Tue Feb 16 11:46:06 2016 Return-Path: Delivered-To: freebsd-scsi@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 7C17CAA91EA for ; Tue, 16 Feb 2016 11:46:06 +0000 (UTC) (envelope-from david.ford@ouce.ox.ac.uk) Received: from fallback2.mail.ox.ac.uk (fallback2.mail.ox.ac.uk [129.67.1.167]) by mx1.freebsd.org (Postfix) with ESMTP id 4B1781A8C for ; Tue, 16 Feb 2016 11:46:05 +0000 (UTC) (envelope-from david.ford@ouce.ox.ac.uk) Received: from relay12.mail.ox.ac.uk ([129.67.1.163]) by fallback2.mail.ox.ac.uk with esmtp (Exim 4.80) (envelope-from ) id 1aVe4t-0002cc-88 for freebsd-scsi@freebsd.org; Tue, 16 Feb 2016 11:45:59 +0000 Received: from hub06.nexus.ox.ac.uk ([163.1.154.240] helo=HUB06.ad.oak.ox.ac.uk) by relay12.mail.ox.ac.uk with esmtp (Exim 4.80) (envelope-from ) id 1aVe4h-00087g-fN for freebsd-scsi@freebsd.org; Tue, 16 Feb 2016 11:45:47 +0000 Received: from MBX01.ad.oak.ox.ac.uk ([169.254.1.95]) by HUB06.ad.oak.ox.ac.uk ([169.254.15.20]) with mapi id 14.03.0248.002; Tue, 16 Feb 2016 11:45:47 +0000 From: David Ford To: "'freebsd-scsi@freebsd.org'" Subject: camcontrol sata affiliations Thread-Topic: camcontrol sata affiliations Thread-Index: AdForTYiiodPtgJoTRCpk4BC+u40Tg== Date: Tue, 16 Feb 2016 11:45:47 +0000 Message-ID: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.16.150.237] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Feb 2016 11:46:06 -0000 Hello, I have a number of dual homed SAS disk chasses, with a mixture of SAS and S= ATA drives. As expected, the SAS drives appear to both hosts, and the SATA = drives appear on a single host, which gets the SAS affiliation. >From the host with the SATA drive visible: [root@backup-san1 ~]# camcontrol smpphylist /dev/ses0 26 PHYs: PHY Attached SAS Address 0 0x0000000000000000 1 0x0000000000000000 2 0x50080e53c2b8f002 (da33,pass36) 3 0x5000cca01ab1a139 (pass0,da0) 4 0x0000000000000000 5 0x0000000000000000 6 0x0000000000000000 7 0x5000c50041affc01 (pass2,da2) 8 0x0000000000000000 9 0x0000000000000000 10 0x5000cca03ea41585 (pass1,da1) 11 0x0000000000000000 12 0x500605b004f24f20 13 0x500605b004f24f20 14 0x500605b004f24f20 15 0x500605b004f24f20 16 0x0000000000000000 17 0x0000000000000000 18 0x0000000000000000 19 0x0000000000000000 20 0x0000000000000000 21 0x0000000000000000 22 0x0000000000000000 23 0x0000000000000000 24 0x50080e53c2b8f03d 25 0x000000000000003e >From the other host: root@backup-san-02:~ # camcontrol smpphylist /dev/ses0 26 PHYs: PHY Attached SAS Address 0 0x0000000000000000 1 0x0000000000000000 2 0x0000000000000000 3 0x5000cca01ab1a13a (pass2,da1) 4 0x0000000000000000 5 0x0000000000000000 6 0x0000000000000000 7 0x5000c50041affc02 (pass1,da0) 8 0x0000000000000000 9 0x0000000000000000 10 0x5000cca03ea41586 (pass3,da2) 11 0x0000000000000000 12 0x500605b004f27920 13 0x500605b004f27920 14 0x500605b004f27920 15 0x500605b004f27920 16 0x0000000000000000 17 0x0000000000000000 18 0x0000000000000000 19 0x0000000000000000 20 0x0000000000000000 21 0x0000000000000000 22 0x0000000000000000 23 0x0000000000000000 24 0x50080e53c1e1803d 25 0x000000000000003e I can successfully clear the affiliation: [root@backup-san1 ~]# camcontrol smppc /dev/ses0 -p 2 -o clearaffiliation [root@backup-san1 ~]# smp_rep_phy_sata --phy=3D2 /dev/ses0 Report phy SATA response: expander change count: 74 phy identifier: 2 STP I_T nexus loss occurred: 0 affiliations supported: 1 affiliation valid: 0 STP SAS address: 0x50080e53c2b8f002 register device to host FIS: 34 00 50 01 01 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 affiliated STP initiator SAS address: 0x0 STP I_T nexus loss SAS address: 0x0 affiliation context: 0 current affiliation contexts: 0 maximum affiliation contexts: 1 However from the other host: root@backup-san-02:~ # camcontrol smppc /dev/ses0 -p 2 -o sataportsel appears to do nothing - the output of camcontrol smpphylist /dev/ses0 and i= t does not appear on a rescan, or if I attempt to hard reset it. root@backup-san-02:~ # smp_rep_phy_sata --phy=3D2 /dev/ses0 Report phy SATA result: Phy does not support SATA The systems are running Freebsd 10.2, and I have tested with both the mps a= nd the mpr driver on different systems, the behaviour is identical. Either I'm missing a crucial step in this process, or it's a bug. Does anyo= ne have any suggestions. Thanks David --=20 David Ford IT Manager, School of Geography and the Environment For general IT Support queries please contact itsupport@ouce.ox.ac.uk Telephone: +44 1865 285089