From owner-freebsd-current@freebsd.org Fri Sep 20 15:53:10 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 35BEA121537 for ; Fri, 20 Sep 2019 15:53:10 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 46ZdXj17Ktz4LXC; Fri, 20 Sep 2019 15:53:08 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1iBLDU-0002cV-9C; Fri, 20 Sep 2019 18:53:04 +0300 Date: Fri, 20 Sep 2019 18:53:04 +0300 From: Slawa Olhovchenkov To: Freddie Cash Cc: Michael Gmelin , Kurt Jaeger , Toomas Soome , FreeBSD-Current Subject: Re: Lockdown adaX numbers to allow booting ? Message-ID: <20190920155304.GN3953@zxy.spb.ru> References: <20190919140219.GE2863@home.opsec.eu> <7E0AE025-596C-457E-BC40-41217857A3CD@me.com> <20190919155713.GG2863@home.opsec.eu> <3C855A39-BF79-4430-98CB-CB9174768E11@freebsd.org> <20190920143531.GB38096@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-Rspamd-Queue-Id: 46ZdXj17Ktz4LXC X-Spamd-Bar: ++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of slw@zxy.spb.ru has no SPF policy when checking 195.70.199.98) smtp.mailfrom=slw@zxy.spb.ru X-Spamd-Result: default: False [2.84 / 15.00]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; IP_SCORE(0.00)[country: RU(0.01)]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; DMARC_NA(0.00)[zxy.spb.ru]; AUTH_NA(1.00)[]; RCPT_COUNT_FIVE(0.00)[5]; NEURAL_SPAM_MEDIUM(0.50)[0.500,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; NEURAL_SPAM_LONG(0.43)[0.434,0]; R_SPF_NA(0.00)[]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:5495, ipnet:195.70.192.0/19, country:RU]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Sep 2019 15:53:10 -0000 On Fri, Sep 20, 2019 at 08:29:08AM -0700, Freddie Cash wrote: > On Fri, Sep 20, 2019 at 7:35 AM Slawa Olhovchenkov wrote: > > > On Thu, Sep 19, 2019 at 06:04:54PM +0200, Michael Gmelin wrote: > > > What about gpart output of the pool drives? > > > > > > In general you would create zpools using gptids or gpt labels, not the > > devices, so you’re independent of device numbering. The boot loader should > > only be installed on drives that contain the boot pool (maybe you have old > > boot loaders on data drives?). > > > > ZFS work w/ ZFS labels, not w/ device names/gptids/gpt labels. > > You don't worry about changed device names aroud reboots. > > > > Very true, from ZFS' point of view. It writes a ZFS label to whichever > GEOM provider you hand it (file, iSCSI device, raw device, MBR partition, > GPT partition, etc), and it will find it's pool members based on those > labels. ZFS doesn't care where the device is physically connected in the > system, just that it is connected. > > But the ZFS labels aren't what it will display in "zpool list -v" or "zpool > status" output. That will show the GEOM provider you gave it (and, > depending on the order that GEOM tastes the devices, and what's > enabled/disabled in loader.conf, that output can change). That's where > it's useful to have human-readable, descriptive labels (like GPT partition > labels), and to disable all the GEOM ID systems you won't be using via > loader.conf. So that when things go sideways, and a disk dies, you can > find it quickly and easily. Much easier to replace "gpt/jbod3-a6" in a > multi-chassis storage system with 100+ drives than to figure out which bay > corresponds to "ada73" after a couple of reboots that may or may not have > changed the PCI bus enumeration direction, or after replacing an HBA that Location of device in multi-chassis storage system is different story. I am don't know how to field engineer insert disks in chassis. For me simple is find in /var/run/dmesg.boot S/N <=> daXY mapping and turn ON led by sas2ircu. > enumerates drives a different way (da vs ada), or after a BIOS/EFI upgrade > that renumbers things, or any other number of situations. (We've run into > most of these, and have come to rely on GPT partition labels for just this > reason; and we stick the drive serial number on the outside of the bay, > just in case). > It's not a ZFS requirement. It just makes things easier for the admin down > the road. Especially if the admin team changes or inherits systems. :) This is need many manual work at setup and build time. DC field engineer make servers for me and don't do this work for me.