From nobody Mon Jun 26 16:54:44 2023 X-Original-To: freebsd-fs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4QqYqS65sfz4k21L for ; Mon, 26 Jun 2023 16:55:00 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-lf1-x129.google.com (mail-lf1-x129.google.com [IPv6:2a00:1450:4864:20::129]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QqYqS2th3z4KtM for ; Mon, 26 Jun 2023 16:55:00 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-lf1-x129.google.com with SMTP id 2adb3069b0e04-4f865f0e16cso4603868e87.3 for ; Mon, 26 Jun 2023 09:55:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20221208.gappssmtp.com; s=20221208; t=1687798498; x=1690390498; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=T0K2s+I1hkzksxV/LBkqI5s+DpDzrp3L59f881U1IWo=; b=LUqyhpBgrefQgZnUijgdmoZk8dg4mZEQXZHYhD3MropDsiIkFLYqyQAMUcccFAeO3v U5oP8C2jgjQerSNJJo4limh0E9mbFqy0w0NLQ6d+4FMIMLme4CxpFSB0B8FcDRRaUqR+ l+Wa1W08Mv2vg1zsoxO7qmtFfSVp8euvgIALy53nLMXTZsZk+lBcM2hgJnvbcL6lL2Hg utmVszSV1V1faNsmKIUhJYA6wLHjIH+KYhguZc+jsJ1xbswDep5IW8YT+Csh8LRWLff+ UvYPIjhaxe7/grXS0oOphAJDQiZpOZoqlNVMl0DgCOr8DTrzr5+bQ8yiBxBIXBf3qUGx XKPQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1687798498; x=1690390498; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=T0K2s+I1hkzksxV/LBkqI5s+DpDzrp3L59f881U1IWo=; b=UIOWUKjvaBOQTRvNczfJc4YgGN8pCz6gBZ2i6zPvlrilczP+/zwQXRW10lYwM5mKCz F63lAZwCDzweTs82McO99J1BQn5BYvzzNzOboUKrQISfpI5JpvojGs3DfGXIto/rUW5O 8bacupOFQU6L59EXCrQcyfm1oSTGv/aVdx6YhVm60JkU3YeVgyaX3NIM/2Yn74Tmkz7c mYWwvlpdqhjW3ZeZvZ7cWOV4EA/okylRJsVYCSCHPQ1t0iaiCfbG8xkdBbu9GA+UiYaX o/MRYfS56ThY8rH1H+SqAnikOoKs3nQ1HVGknB6IXWaKFZOQFKXtnQV8++GeIDO609c+ gP5A== X-Gm-Message-State: AC+VfDxgBl9nKsgQpxLH6Huh3nW7vZKYHlVCgdgo9dxGCnO00hUZWBWC JLFkXPf1iXvVpg8KjQKaL9cWTV00oQPDlLIWBO+2jcFYJc79C60cjVc= X-Google-Smtp-Source: ACHHUZ7PMkD1Rxg02tNG4pkrZ7x4go87eKPyHAOcXDCDp/QXZxeauljAODwFJIMx9TNndxse3gMBpPR695hCR/C+I1U= X-Received: by 2002:a05:6512:3d19:b0:4f9:7a6e:fec1 with SMTP id d25-20020a0565123d1900b004f97a6efec1mr3979281lfv.10.1687798495581; Mon, 26 Jun 2023 09:54:55 -0700 (PDT) List-Id: Filesystems List-Archive: https://lists.freebsd.org/archives/freebsd-fs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-fs@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Warner Losh Date: Mon, 26 Jun 2023 10:54:44 -0600 Message-ID: Subject: Re: nvd -> nda change (breaks geli)? To: "Bjoern A. Zeeb" Cc: freebsd-fs@freebsd.org Content-Type: multipart/alternative; boundary="000000000000c95b2905ff0b35de" X-Rspamd-Queue-Id: 4QqYqS2th3z4KtM X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --000000000000c95b2905ff0b35de Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, Jun 26, 2023 at 10:01=E2=80=AFAM Bjoern A. Zeeb < bzeeb-lists@lists.zabbadoz.net> wrote: > Hi, > > some laptops had only /dev/nvd* nodes in the past. > These now show up as /dev/nda*. > Not sure when the symlinks are created for compat. > > I had to help rescue someone's geli setup manually as there were > no keys loaded for nda but only for nvd. At least loading the key > again for nda made things work. A bit painful remotely ... > > Should this at least be in UPDATING? > Well, we have this already: 20230612: Belatedly switch the default nvme block device on x86 from nvd to nda. nda created nvd compatibility links by default, so this should be a nop. If this causes problems for your application, set hw.nvme.use_nvd=3D1 in your loader.conf or add `options NVME_USE_NVD=3D1` to your kerne= l config. To disable the nvd compatibility aliases, add kern.cam.nda.nvd_compat=3D0 to loader.conf. The default has been n= da on all non-x86 platforms for some time now. If you need to fall back, please email imp@freebsd.org about why. Can you send me more details about what failed? It should be a no-op, but I am aware of one issue with libgeom that I need to fix. Warner --000000000000c95b2905ff0b35de Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Mon, Jun 26, 2023 at 10:01=E2=80= =AFAM Bjoern A. Zeeb <= bzeeb-lists@lists.zabbadoz.net> wrote:
Hi,

some laptops had only /dev/nvd* nodes in the past.
These now show up as /dev/nda*.
Not sure when the symlinks are created for compat.

I had to help rescue someone's geli setup manually as there were
no keys loaded for nda but only for nvd.=C2=A0 At least loading the key
again for nda made things work.=C2=A0 A bit painful remotely ...

Should this at least be in UPDATING?

We= ll, we have this already:

20230612:
=C2=A0 =C2=A0 = =C2=A0 =C2=A0 Belatedly switch the default nvme block device on x86 from nv= d to nda.
=C2=A0 =C2=A0 =C2=A0 =C2=A0 nda created nvd compatibility link= s by default, so this should be a
=C2=A0 =C2=A0 =C2=A0 =C2=A0 nop. If th= is causes problems for your application, set hw.nvme.use_nvd=3D1
=C2=A0 = =C2=A0 =C2=A0 =C2=A0 in your loader.conf or add `options NVME_USE_NVD=3D1` = to your kernel
=C2=A0 =C2=A0 =C2=A0 =C2=A0 config. To disable the nvd co= mpatibility aliases, add
=C2=A0 =C2=A0 =C2=A0 =C2=A0 kern.cam.nda.nvd_co= mpat=3D0 to loader.conf.=C2=A0 The default has been nda on
=C2=A0 =C2=A0= =C2=A0 =C2=A0 all non-x86 platforms for some time now. If you need to fall= back,
=C2=A0 =C2=A0 =C2=A0 =C2=A0 please email imp@freebsd.org about why.

Can you se= nd me more details about what failed? It should be a no-op, but I am
<= div>aware of one issue with libgeom that I need to fix.

Warner=C2=A0
--000000000000c95b2905ff0b35de--