From owner-freebsd-fs@FreeBSD.ORG Mon Dec 8 13:55:14 2014 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 089C2593; Mon, 8 Dec 2014 13:55:14 +0000 (UTC) Received: from mx2.paymentallianceintl.com (mx2.paymentallianceintl.com [216.26.158.171]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mx2.paymentallianceintl.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AD9EF693; Mon, 8 Dec 2014 13:55:13 +0000 (UTC) Received: from PAIMAIL.pai.local (paimail.pai.local [10.10.0.153]) by mx2.paymentallianceintl.com (8.14.5/8.13.8) with ESMTP id sB8Dk22o099676 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 8 Dec 2014 08:46:02 -0500 (EST) (envelope-from mikej@paymentallianceintl.com) Received: from PAIMAIL.pai.local ([::1]) by PAIMAIL.pai.local ([::1]) with mapi; Mon, 8 Dec 2014 08:46:01 -0500 From: Michael Jung To: Will Andrews , Andriy Gapon Date: Mon, 8 Dec 2014 08:45:56 -0500 Subject: FreeBSD Enclosure Management - WAS: ZFS weird issue... Thread-Topic: FreeBSD Enclosure Management - WAS: ZFS weird issue... Thread-Index: AdAS7Q0yXe6cCl4IQ52pBOM8jKJQAw== Message-ID: <9C91F97841BC4347910F206618BAA3BB04E8583B27@PAIMAIL.pai.local> 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-fs@freebsd.org" X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Dec 2014 13:55:14 -0000 >There are patches to provide physical paths through SES/SAF-TE/SGPIO which >offer paths decidedly more physical than a device name. And to perform >automatic replacement by physical path based on these. Not sure to what >degree these have been integrated in the mainline. But this still requires >the system to have an enclosure service of some sort. All: At home, I have used gpart labels to identify drives (14 drives) which obvi= ously doesn't scale well. Do the patches get one to a point of identifying drives as lon= g as you have controllers and backplanes supporting say SGPIO e.g. LSI/Superm= icro? Can you expound on what the 'service' would provide in addition to the patc= hes? This link is informative but leave questions for the reader. https://people.freebsd.org/~mav/Enclosure_Management_en.pdf Where are your patches located? I would very much like to learn more as to how best to handle enclosure management under FreeBSD, or to know that in fact it is not generic enough and that it will always be hardware (backplane/expander/controller) dependent for any implementation requiring programing skills or vendor supplied tools. Kind regards, --mikej GoPai.com | Facebook.com/PaymentAlliance CONFIDENTIALITY NOTE: This message is intended only for the use of the individual or entity to whom it is addressed and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, please notify us by telephone at (502) 212-4001 or notify us at PAI , Dept. 99, 6060 Dutchmans Lane, Suite 320, Louisville, KY 40205