From owner-freebsd-current@freebsd.org Thu Sep 19 21:46:18 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 1602C12F555 for ; Thu, 19 Sep 2019 21:46:18 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-lf1-x12d.google.com (mail-lf1-x12d.google.com [IPv6:2a00:1450:4864:20::12d]) (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 46Z9Qd2TN2z4KWv; Thu, 19 Sep 2019 21:46:17 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: by mail-lf1-x12d.google.com with SMTP id c195so3456396lfg.9; Thu, 19 Sep 2019 14:46:17 -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=DZL3Qs0S9R13Zp5T+/yJ73RGQmXLvq85Q3a87kVegis=; b=qSlz6aS1UXlsJa32bQwP7wqFaj0rXUJSA2W5ojlZxa97/n7bWlnyJjJSqGwX8TNyaW HZEewoBR039VVO+N8TvJWsIPxsMO0c8IKRXULX5H/s2sSSqdtmrRYnR4xqUDKG3ZC/nV Hy7ND8Za0IZaRadEhvRoXlHLqWcDCitDdrtRN1T4v/x/n85YcLIPCq/zChv0PKd9+n3+ p05vOleGhvCYorwXMSHtyf6DdYyxdE+ifNhiDmTWu+cVlf0D/8WxxccPMnCJfow37la0 AgNZhya61LumC87VjgbhNdGHcI4C0PVX6w0T5JsTtpSjYhILQb9kVIziddGNEVRv/Oui BtBg== 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=DZL3Qs0S9R13Zp5T+/yJ73RGQmXLvq85Q3a87kVegis=; b=ck4674Ubs8TBE8yrUexMTYCwsqrepXSrc67Cg+LxZlPxGCTixSO8210qAmZ1QBY7vo v6tTqZ1N7juLvVTH62X0me/wNmQXRFaY7bgxgGZvTyzkT0h/dNnkuA/QyRjMQCTzF1ns mw75MA5lB40IXlQ+tO/bmO4bZwBFQ/8RWeQLwF8huglB9llWcB9qxHwLGcQA/8zIMpDN iIjqcHIq6tRQEooJEb/FTyw4bWnaOwoYdpRFUENY5cNuqQMuVd5GCcqyzCJ65Tr0Gqar 5dp4pInWL86P6lfetsisKUMSez0bd6wZCrnfoTzeCn9McWQn3VD/5xYV1Z2yd2LEXvoU Em0A== X-Gm-Message-State: APjAAAUa1cde621yqzyKQBdSVFU0eQBvRgO7NPuI3m2NfI9rn73Q/+By MyPwb2QUdZtbA8Mo9kUxQPtqOHlAfGk8n+sh7nqU3Q== X-Google-Smtp-Source: APXvYqw4TvIiZA3verm7loEeRmucJakzVpBCZCyGLgiBiUgQ9B81FbMCqTgBDa80lO108+5UjwGS0v0dSwEYetA/JyU= X-Received: by 2002:ac2:4149:: with SMTP id c9mr6252695lfi.128.1568929574535; Thu, 19 Sep 2019 14:46:14 -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> <20190919171529.GH2863@home.opsec.eu> In-Reply-To: From: Freddie Cash Date: Thu, 19 Sep 2019 14:46:02 -0700 Message-ID: Subject: Re: Lockdown adaX numbers to allow booting ? To: Andreas Nilsson Cc: Michael Gmelin , Kurt Jaeger , Current FreeBSD X-Rspamd-Queue-Id: 46Z9Qd2TN2z4KWv X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=qSlz6aS1; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of fjwcash@gmail.com designates 2a00:1450:4864:20::12d 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)[]; RCPT_COUNT_THREE(0.00)[4]; FREEMAIL_FROM(0.00)[gmail.com]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; 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)[]; 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)[d.2.1.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: (-8.89), ipnet: 2a00:1450::/32(-2.93), asn: 15169(-2.22), country: US(-0.05)]; FREEMAIL_TO(0.00)[gmail.com]; 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" 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: Thu, 19 Sep 2019 21:46:18 -0000 On Thu, Sep 19, 2019 at 12:01 PM Andreas Nilsson wrote: > Seems like more of a bios enumeration issue. You should be able to set a > boot order better suited for your setup there. And if that does not work, > just move the sata cables around seems like the most straight forward > solution. > > Although I think I've heard it is bad practice to use raw devices for zfs, > especially if need to replace a drive, which day happens to be a different > revision, with a few fewer blocks available. Then you will not be able to > do the replace. > > Back in the good ol' days of ZFS versions where everyone was compatible with Solaris, this was an issue. However, the ondisk format (or ZFS label setup?) was changed to leave 1 MB of free space at the end of the drive to allow for this. With ZFSv6, for example, if you used a raw device for the vdev, and that disk died, and the replacement was 1 sector smaller, the replace would fail. Today, with OpenZFS, the replace would succeed. There's also 1 MB or so of reserved space in the pool such that if you fill the pool "100%", you can still do a "zfs destroy" of a dataset to free up space. Previously, this would fail, as you need space in the pool to write the metadata for the destroy before doing the destroy. ZFS of today is much more resilient to these kinds of niggles that bit us all, back in the day. :D -- Freddie Cash fjwcash@gmail.com