Date: Wed, 21 Jun 2023 18:52:15 -0600 From: Warner Losh <imp@bsdimp.com> To: Kevin Oberman <rkoberman@gmail.com> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: Where did the nvd devices go? Message-ID: <CANCZdfr6BN6S5TKcCuifq-RSNpnRfaf-Zf_Y%2BMXwxF96N3CcJQ@mail.gmail.com> In-Reply-To: <CAN6yY1s-8T4yoafCy6sPTgqw6ndMYv7hj%2BHU-fcO2QhnhUCRWQ@mail.gmail.com> References: <CAN6yY1s-8T4yoafCy6sPTgqw6ndMYv7hj%2BHU-fcO2QhnhUCRWQ@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Wed, Jun 21, 2023, 6:22 PM Kevin Oberman <rkoberman@gmail.com> wrote: > Well, they are still around, but not functional. They are symlinks to nda > devices, but the symlinks don't work well. > They work for filesystem access. I have no idea when the symlink of nvd to nda happened, but after updating > my system to main-n263630-ab3e6234ab6e, at least geom 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." geli responds (after > entering a passphrase) "geli: Provider not found: "/dev/nvd0p7"My previous > 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? 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. > All these questions are answered in the UPDATING entry from when I switched the default: 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=1 in your loader.conf or add `options NVME_USE_NVD=1` to your kernel config. To disable the nvd compatibility aliases, add kern.cam.nda.nvd_compat=0 to loader.conf. The default has been nda on all non-x86 platforms for some time now. If you need to fall back, please email imp@freebsd.org about why. -- > Kevin Oberman, Part time kid herder and retired Network Engineer > E-mail: rkoberman@gmail.com > PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 > [-- Attachment #2 --] <div dir="auto"><div><br><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jun 21, 2023, 6:22 PM Kevin Oberman <<a href="mailto:rkoberman@gmail.com" target="_blank" rel="noreferrer">rkoberman@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small">Well, they are still around, but not functional. They are symlinks to nda devices, but the symlinks don't work well.</div></div></blockquote></div></div><div dir="auto"><br></div><div dir="auto">They work for filesystem access.</div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small">I have no idea when the symlink of nvd to nda happened, but after updating my system to main-n263630-ab3e6234ab6e, at least geom 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." geli responds (after entering a passphrase) "geli: Provider not found: "/dev/nvd0p7"My previous system version was main-n262908-c16e08e5f324.</div></div></blockquote></div></div><div dir="auto"><br></div><div dir="auto">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).</div><div dir="auto"><br></div><div dir="auto">Was this just a failure of muscle memory, or was there persistent config that failed?</div><div dir="auto"><br></div><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small">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.<br></div></div></blockquote></div></div><div dir="auto"><br></div><div dir="auto">All these questions are answered in the UPDATING entry from when I switched the default:</div><div dir="auto"><br></div><div dir="auto"><pre style="padding:0px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0);font-size:13.3333px;background-color:rgb(255,255,255)"><code>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=1 in your loader.conf or add `options NVME_USE_NVD=1` to your kernel config. To disable the nvd compatibility aliases, add kern.cam.nda.nvd_compat=0 to loader.conf. The default has been nda on all non-x86 platforms for some time now. If you need to fall back, please email <a href="mailto:imp@freebsd.org">imp@freebsd.org</a> about why.</code></pre></div><div dir="auto"><br></div><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small"></div><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr">Kevin Oberman, Part time kid herder and retired Network Engineer<br>E-mail: <a href="mailto:rkoberman@gmail.com" rel="noreferrer noreferrer" target="_blank">rkoberman@gmail.com</a><br></div><div>PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683</div></div></div></div></div></div></div></div></div> </blockquote></div></div></div>help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfr6BN6S5TKcCuifq-RSNpnRfaf-Zf_Y%2BMXwxF96N3CcJQ>