From nobody Thu Jun 22 02:46:53 2023 X-Original-To: freebsd-current@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 4QmlC22Zmjz4gLH3 for ; Thu, 22 Jun 2023 02:47:10 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-yb1-xb2e.google.com (mail-yb1-xb2e.google.com [IPv6:2607:f8b0:4864:20::b2e]) (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 4QmlC20y42z4DPN for ; Thu, 22 Jun 2023 02:47:10 +0000 (UTC) (envelope-from kob6558@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-yb1-xb2e.google.com with SMTP id 3f1490d57ef6-bfe6ea01ff5so1533520276.3 for ; Wed, 21 Jun 2023 19:47:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1687402029; x=1689994029; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=H8p2rI2ZaAI561IsKD9lLHzPuWueIlN5hJxMz+eOrIs=; b=sca6xMsh8yVxkGQPaZJ7SJqsUJAXX+sWTQYO6pyHsoklyl+gOJ6fH/EtrYjUX8zArh CT3VcrdRXcJfisliGENSz3UPw2I5HMGh4OWZu56hGSarFUe3deTyD/UxndI5YVj8iaP0 sM6OF0U3fWrLortcChsN8SBnLUZX4ucG/C6GP7TnuJUhpeVJ7hBDfGkgltzv0zwmELCW Q9j2kSv9+qt5oQb153L9Yw66rotK3IK4KswVkSacp/TP3ABtWLr/zijnRc3jatYXoIIS u7Db42vMi8UfPPbCkT2sBNzwHvqfLKknBs0njkOtsW9vTRzzlENLNhDxjLje9Nta5cPl XeIQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1687402029; x=1689994029; 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=H8p2rI2ZaAI561IsKD9lLHzPuWueIlN5hJxMz+eOrIs=; b=PcFykuvobYbzO9ww6NGmwqSVm5vHPIDL9zkrebeQx2DBJJimshf+FR7KvG25oareVF /O5rXBUdjOWwV2nd0GUGnywn0kP9P6kfbAaF0XBsiL/igkinRANrOs8jdlvYFQvTHDR7 wISmC/vc2936s1S0uXWnnLYDiLdGUNwssPvnOJfxYQKGni+ie8MLiHc4EeyHbeGSnbJT iYy0klvNsmbdojblCIIIbExN6Huu8/3pxgnmwAi6ng6bDaO8Ix7lshHm/IhfPfC4DViz v26WO4FESG/oivHSCx9Nr5PsaSU1n89etv5FQPjfLqybxduFW/zGoUXla0VXV2wquDDR tkTw== X-Gm-Message-State: AC+VfDwlx96Jk7MURkVYrZG8dhpOkw37bkRBPWjENlGfdokpZYcriq9O G9N8aaLDab4FZWBh9RUkzPExS6gzOEsEkywtdrhQSkKG X-Google-Smtp-Source: ACHHUZ54Au58jn0Qxn9QIXuA9nGUl6K66u3K2SWCjDnU3+gTtQqYzH5UCjiO2owmxgTAL8LcRJ0xTmhteoJz1PZnFdE= X-Received: by 2002:a25:ae48:0:b0:bcf:ef73:1431 with SMTP id g8-20020a25ae48000000b00bcfef731431mr12601391ybe.26.1687402029086; Wed, 21 Jun 2023 19:47:09 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Kevin Oberman Date: Wed, 21 Jun 2023 19:46:53 -0700 Message-ID: Subject: Re: Where did the nvd devices go? To: Warner Losh Cc: FreeBSD Current Content-Type: multipart/alternative; boundary="000000000000897ab105feaee6ea" X-Rspamd-Queue-Id: 4QmlC20y42z4DPN X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --000000000000897ab105feaee6ea Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, Jun 21, 2023 at 5:52=E2=80=AFPM Warner Losh wrote: > > > On Wed, Jun 21, 2023, 6:22 PM Kevin Oberman wrote: > >> Well, they are still around, but not functional. They are symlinks to nd= a >> devices, but the symlinks don't work well. >> > > They work for filesystem access. > Not too surprised, but I didn't try it. Should have looked more closely before sending it. > > I have no idea when the symlink of nvd to nda happened, but after updatin= g >> my system to main-n263630-ab3e6234ab6e, at least geom related commands n= o >> longer function using nvd0p?. I hit this when trying to use gpart and ge= li. >> gpart claims "gpart: No such geom: /dev/nvd0." geli responds (after >> entering a passphrase) "geli: Provider not found: "/dev/nvd0p7"My previo= us >> system version was main-n262908-c16e08e5f324. >> > > These will work with nda. They should likely work with the nvd aliases, > but don't it seems (though you don't need the /dev/ for geom commands). > > Was this just a failure of muscle memory, or was there persistent config > that failed? > Yes, I had confirmed that nda worked and I know that /dev is not required for geom commands, but I've never bothered to test whether gpt/label worked and I tend to use labels. > > Was this intentional? If so, why was this change made? If not, could it >> be fixed? Since I usually use geli with the /dev/gpt devices, I didn't >> notice it right away, but it could certainly surprise many users. >> > Commands used were "gpart show nvd0" and "geli attach -d -k ************ /dev/nvd0p7". Also tried both with and without the "/dev" which fail for nvd* and succeed with nda*. All these questions are answered in the UPDATING entry from when I switched > the default: > I should have checked UPDATING. --=20 > Kevin Oberman, Part time kid herder and retired Network Engineer > E-mail: rkoberman@gmail.com > PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 > --=20 Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 --000000000000897ab105feaee6ea Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Wed, Jun 21, 2023 at 5:52=E2= =80=AFPM Warner Losh <imp@bsdimp.com> wrote:


On Wed, Jun 21, 2023, 6:22 = PM Kevin Oberman <rkoberman@gmail.com> wrote:
Well, they are still around, bu= t not functional. They are symlinks to nda devices, but the symlinks don= 9;t work well.

They work for filesystem access.

Not too surprised, but I didn't try it. Sh= ould have looked more closely before sending it.

=
I have no idea when the symlink of nvd to nda happen= ed, but after updating my system to main-n263630-ab3e6234ab6e, at least geo= m related commands no longer function using nvd0p?. I hit this when trying = to use gpart and geli. gpart claims "gpart: No such geom: /dev/nvd0.&q= uot; geli responds (after entering a passphrase) "geli: Provider not f= ound: "/dev/nvd0p7"My previous system version was main-n262908-c1= 6e08e5f324.

These will work with nda. They should likely work with t= he nvd aliases, but don't it seems (though you don't need the /dev/= for geom commands).

Was= this just a failure of muscle memory, or was there persistent config that = failed?

Yes, I had confirm= ed that nda worked and I know that /dev is not required for geom commands, = but I've never bothered to test whether gpt/label worked and I tend to = use labels.

=
Was this inten= tional? If so, why was this change made?=C2=A0 If not, could it be fixed? S= ince I usually use geli with the /dev/gpt devices, I didn't notice it r= ight away, but it could certainly=C2=A0 surprise many users.

Comma= nds used were "gpart show nvd0" and "geli attach -d -k *****= ******* /dev/nvd0p7". Also tried both with and without the "/dev&= quot; which fail for nvd*=C2=A0 and succeed with nda*.

<= /div>
All these questions are answered in the UPDATING entry from= when I switched the default:

I should have checked UPDATING.

--
<= div>
Kevin Oberman, Part time kid her= der and retired Network Engineer
E-mail: rkoberman@gmail.com=
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B05568= 3


--
Kevin= Oberman, Part time kid herder and retired Network Engineer
E-mail: rkoberman@gmail.com
--000000000000897ab105feaee6ea--