From nobody Thu Jun 22 06:07:51 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 4Qmqfx1n3Dz4gHGd for ; Thu, 22 Jun 2023 06:08:09 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-yb1-xb31.google.com (mail-yb1-xb31.google.com [IPv6:2607:f8b0:4864:20::b31]) (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 4Qmqfx08ngz423G for ; Thu, 22 Jun 2023 06:08:09 +0000 (UTC) (envelope-from kob6558@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-yb1-xb31.google.com with SMTP id 3f1490d57ef6-bfee66a5db6so1401888276.0 for ; Wed, 21 Jun 2023 23:08:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1687414087; x=1690006087; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=qP32e6l9nj3FqUOICk+tdDxv9bGju06d3lGeHKF/Gm4=; b=YLE/r90jdcfiqsvDbO0mo7YhcuHm4LcqWGQN9tuox8xCVWwUgmtHGiVYPZlfb+wYs/ JB301ulhxyyqw2WZtu9WCUIPWYKw2nHXPCybDLuHN2V5VX7Xylxml+vUP2TPJ/CxUz4U 5VLhNSOUGRdfu3i0NW1hPMU7YGfW5r3hAjF7Rn1YjWNC7JzHPgJujqn9jN7RdGCdZGCU +OhHmLfT64G7M7Zb5lEAPrX6h4e7pSdOzM9pJY9EIakYUwQlRWleVSmOi1uUdXJ7QJE5 11kr71J+DB5aASiEKoh7yukQu+eLR/NrSw0S20mPBRGHdU0ggz42WihnZew/UMZHG4aO xa7g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1687414088; x=1690006088; 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=qP32e6l9nj3FqUOICk+tdDxv9bGju06d3lGeHKF/Gm4=; b=JcTBlEKVdN6Yq/FFY2AnF1U/bP/hpvSZBtVTTKwe7IHYOFyB+Qnook/pdCrKgHj/Ol /hAD+kWBlwvtuIARhIXh1RQTFwrvxjwIHtKIiFAn1GTXonm3FEFGdcdR7PGA8b1v4kte 2IT0nUoMqarNREVR//9Ubn8Xuo/SNJVlbRBAOeqwW+1BprIYx+BTiwvJFnvUl5wq13HP +jd0sLW0xyIO//6N5alIgn8tba2Y3NHhGlKy3iFoTvhSI7PwTK9iNa4pevhNoAe3WAov 9ME9eJeGBPqBA0aNmWgnFarvfOGItoIpMs3PIrVdvIffRbiPwMTUvMDDArSObBPIY4wc P8dg== X-Gm-Message-State: AC+VfDz9M9HdbawvIvRdNw9EQOYgYVXktkhSXV5KuL9KcbWTolO7KP98 TIX1UruaphdEyUXDfZYQzoNq2LZeNP6k8HvCJU4sPkav X-Google-Smtp-Source: ACHHUZ7690nEWPam3koHTc2agJAPEEuyUr179xYdTpQfUr5VROS+CaNCQ8BtmcQTtJoYlH3Fl5wMoj2Hqefrqann6xQ= X-Received: by 2002:a25:6982:0:b0:ba8:1c9e:c77f with SMTP id e124-20020a256982000000b00ba81c9ec77fmr8124083ybc.22.1687414087685; Wed, 21 Jun 2023 23:08:07 -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 23:07:51 -0700 Message-ID: Subject: Re: Where did the nvd devices go? To: Warner Losh Cc: FreeBSD Current Content-Type: multipart/alternative; boundary="000000000000491aaa05feb1b5fc" X-Rspamd-Queue-Id: 4Qmqfx08ngz423G 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 --000000000000491aaa05feb1b5fc Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Just found another breakage due to nvd becoming a symlimk. I use gkrellm as my system monitor and, after the update, my SSD showed no activity. Easy fix to edit the configuration to disable nvd0 and enable nda0, but another case of a tool not following the symlink. If I get a little time tomorrow. I'll try finding the code in gkrellm and see if I can figure out whether the breakage is a roble in the port or a system issue, but no promises. On Wed, Jun 21, 2023 at 8:43=E2=80=AFPM Warner Losh wrote: > > > On Wed, Jun 21, 2023 at 8:47=E2=80=AFPM Kevin Oberman wrote: > >> >> 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*. >> > > Ah. I see the problem. libgeom doesn't parse the nodes, nor does > it use them when searching for a geom by name... > > I need to carefully think about how to fix it, though, since it may be an > ABI change and we're getting trickily close > to 14 to be mucking with this... > > Warner > --=20 Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 --000000000000491aaa05feb1b5fc Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Just found another breakage due to nvd becoming = a symlimk. I use gkrellm as my system monitor and, after the update, my SSD= showed no activity. Easy fix to edit the configuration to disable nvd0 and= enable nda0, but another case of a tool not following the symlink.

If I get a little time tomorrow. I'll try f= inding the code in gkrellm and see if I can figure out whether the breakage= is a roble in the port or a system issue, but no promises.
=
On Wed= , Jun 21, 2023 at 8:43=E2=80=AFPM Warner Losh <imp@bsdimp.com> wrote:


On Wed, Jun 21= , 2023 at 8:47=E2=80=AFPM Kevin Oberman <rkoberman@gmail.com> wrote:

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

Ah. I see the problem. libgeom doesn= 't parse the <alias> nodes, nor does it use them when searching f= or a geom by name...

I need to carefully think abo= ut how to fix it, though, since it may be an ABI change and we're getti= ng trickily close
to 14 to be mucking with this...
=
Warner


--