From owner-freebsd-current@freebsd.org Fri Sep 20 15:29:22 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 1D0D4FFC89 for ; Fri, 20 Sep 2019 15:29:22 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-lj1-x22e.google.com (mail-lj1-x22e.google.com [IPv6:2a00:1450:4864:20::22e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46Zd1F37zCz4K4k; Fri, 20 Sep 2019 15:29:21 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: by mail-lj1-x22e.google.com with SMTP id 7so7489675ljw.7; Fri, 20 Sep 2019 08:29:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=pXyqJiy2sixYawfIxl/xR7pki39rJY+5pD1DAkSeYbg=; b=QiHs9zJVKtweCaFQGIZkZGvP4me7fxEdiYj7Ada2792uF8uonmarDcVbU2tQ7R4Miy r9GGY8Ip8c5JkNkzTxuXzFp5cWGyeNnENB6TIw/fJ9vQPPU+MXUkS5mYlA5WImO8zipb vecDRdTJSDWlXeAWXRPs7h3cte1cFVp6L935ak9ia0PTUEPG7oYJu8n24VLD2mcvzzqE h2VkaoccoEk4TZaePiLASQo5RybR1pxs3JVFSQODfsm2ykIo2RI/wu7bS6vEDq4Hu1Mj i3iAOVVWpGeP8UmI5rlGnZ2WpBKaEhN9oDU2fLdJw+CGULwxR9PPahJKcHWI8SM3IB3i UjHA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=pXyqJiy2sixYawfIxl/xR7pki39rJY+5pD1DAkSeYbg=; b=HEmzb05ddUAR92F1TSDAURNOofvsCLAj3z7FSbgurgypvImjIIF+TTDfHoivPD+ZL6 tlporWooFDoXfXFQaBQUp0pZxX8rcasx59qboubj4zLPVkfpwdsPEVdayM5vYq0Q65c8 P9KPoiQU03lR5qlTchegVaQ+7v1Bvc4NeLvSnt+5n9cqUjpBprbvCGiDV6nmJysWh/T9 IQx3HhAVp0hpg+LObcOfjvy4a1muVxzq1oP7G47V+F4Toy/uCm4TaEL1F9VPEl/jz+Wz zetlbRzHzOBoWJqMrd4HE03bIRYG3w0YFLyVQPNvL5osH3YEp5zE2rxXoiciICWTOGje rHUA== X-Gm-Message-State: APjAAAWajac61WmZ8WpDvajmY0Sgj8RkOMzDRuFhwvz1OMehEZmCOlNh 91VsbWYvbTp2wLjrBfblUjGR6D0Fs+mWWSosw/tdqQ== X-Google-Smtp-Source: APXvYqzRfgBXxiwjJ97HaXuW0T2eLc87ZnKzA0VAguNQutIHS5jgUXVOPDNBqVXGaiFwXCIdx10OY2cK5EGn8a6hjjg= X-Received: by 2002:a2e:9ac1:: with SMTP id p1mr3308424ljj.179.1568993359556; Fri, 20 Sep 2019 08:29:19 -0700 (PDT) MIME-Version: 1.0 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> In-Reply-To: <20190920143531.GB38096@zxy.spb.ru> From: Freddie Cash Date: Fri, 20 Sep 2019 08:29:08 -0700 Message-ID: Subject: Re: Lockdown adaX numbers to allow booting ? To: Slawa Olhovchenkov Cc: Michael Gmelin , Kurt Jaeger , Toomas Soome , FreeBSD-Current X-Rspamd-Queue-Id: 46Zd1F37zCz4K4k X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=QiHs9zJV; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of fjwcash@gmail.com designates 2a00:1450:4864:20::22e as permitted sender) smtp.mailfrom=fjwcash@gmail.com X-Spamd-Result: default: False [-2.00 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; IP_SCORE_FREEMAIL(0.00)[]; RCPT_COUNT_FIVE(0.00)[5]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; RCVD_IN_DNSWL_NONE(0.00)[e.2.2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; IP_SCORE(0.00)[ip: (-9.38), ipnet: 2a00:1450::/32(-2.92), asn: 15169(-2.20), country: US(-0.05)]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0] Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 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:29:22 -0000 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=E2=80=99re independent of device numbering. The boot load= er should > only be installed on drives that contain the boot pool (maybe you have ol= d > 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 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. :) --=20 Freddie Cash fjwcash@gmail.com