From nobody Mon Sep 15 15:37:35 2025 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 4cQTgl2hVLz67WK2 for ; Mon, 15 Sep 2025 15:37:55 +0000 (UTC) (envelope-from rick.macklem@gmail.com) Received: from mail-ed1-x531.google.com (mail-ed1-x531.google.com [IPv6:2a00:1450:4864:20::531]) (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 "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4cQTgl0NDpz3WPm for ; Mon, 15 Sep 2025 15:37:55 +0000 (UTC) (envelope-from rick.macklem@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ed1-x531.google.com with SMTP id 4fb4d7f45d1cf-62ee43b5e5bso5580155a12.1 for ; Mon, 15 Sep 2025 08:37:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1757950668; x=1758555468; darn=freebsd.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=731bw1LDG4YP9qf26x1fxMiHGJx3092OvAROed0Xq3o=; b=U/mdcZ+biTxsCHu/QLrIRY5nBN1siATjqxUqLOr4R9pcNGZgtKWIkM52gsaACZcuxs n5TgmNri6SDgQCs27XQ9a8AvBiXFvDqmmTHmrg1QGLyLdiTIU0BSobVL9tvNSViDUd2j 1wMRw3yrECnu/9cPHfwaNnxE+0p8qOWabjJrlyfkWP6pAX7QyrxO7Y1OKrqgt90viCWV lvJ5lKRkLqv0BvPaeoCjLiNVn9deDW0Q8ihA7qWkO3tFFp/Dw/JX7oWcEpjr/wxeDTNr 7Oi+7DMbQtxgJyDmWdUGPlCeJvqFNQ4zd6RiPYjSs4xcqbeRvUlGCVRcDT5J1GEnR6YE Uenw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1757950668; x=1758555468; h=content-transfer-encoding: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=731bw1LDG4YP9qf26x1fxMiHGJx3092OvAROed0Xq3o=; b=M2nwdMFIGMZwVzSW31GqbY2o6H6HWpgjcipGIpNHGtCycEBEYuQUTb1jwDm5InNAzN P4E6MHFNyv5LxaNzQrrg5Tc1A45TMSz9WP0NiILBJ8lZbY0tBuzEjdY+l8jHSElGqcZy nLHXUr+6J6R2Q9gdlQY8NMOptsgInR2hW6ebuFjo8HnJh2BIytRku4hs90xc+my4hAcB 7XteNP8ewscBht7HRv4AJHr0t14FvbOI7rGB6SZmCyInbCa4irZDVey44NCfW+SUKTS5 kv+qWXRUmdEsxT+wSAcUcJGmMqupGVsMD9WhSEVI9+jufuS4ETcsJtIr0d0Cc+iq2NxP vPAw== X-Gm-Message-State: AOJu0YwmtgUrKfB9gG6IZX8SFqagqvQ5/ZvpmRf7jpzru9Te0Y2PqFy8 Q5j+h7NbFAQplAJGcpYtqlm9mShs5mT36ilc9wQxFmdgDI449oZ7sAJDpoFvP1PTaw41RyIeilj nLyLWUCLfME4vc4jPWV85Z/agCiJnHyPR X-Gm-Gg: ASbGncu8hIzVd2rQk2D1ypqNqLn+aYbaLOHuXRR9/A8VIZtNJh6voBg+efO4P8a8+yF 8O0YWb4HBcLaR7oPkG2KrANjzCth9ZWT1F1dD/M9Sa4mylbT96FU4zKXtTGchVMr19UFScQJT8e OxXdOTNUEi0GYJ+Un6daXhrzoHI/PuKtpEGZDtrNTjhp9Sn45jZiKam9zWPxvXP/VONmx4Z03/t XrFuGNhhvoykAvAwhbKN2W+EGRWFH3mtw+QJfg= X-Google-Smtp-Source: AGHT+IH0FEEzbr3aux+9oMybroq1SVf6CcEWgb6Ofq7MPqWRchIXUgy58+xbCfA3mh6yNmNl0ih3SA1fSVjc0qDmTdw= X-Received: by 2002:a05:6402:2381:b0:627:2ad9:ce24 with SMTP id 4fb4d7f45d1cf-62ed830880amr11352577a12.31.1757950668055; Mon, 15 Sep 2025 08:37:48 -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: Rick Macklem Date: Mon, 15 Sep 2025 08:37:35 -0700 X-Gm-Features: AS18NWBEa4AooLrgn8QDtqtoXSFK-phtRm6s70nb0ckx16aVGNjJf9E6BFKt2qU Message-ID: Subject: Re: Changes in NFS mounts from 14.3 to -CURRENT (almost 15)? To: Zaphod Beeblebrox Cc: freebsd-current , freebsd-fs Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; TAGGED_FROM(0.00)[] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Rspamd-Queue-Id: 4cQTgl0NDpz3WPm On Sun, Sep 14, 2025 at 9:15=E2=80=AFPM Zaphod Beeblebrox wrote: > > OK. Thanks. rpcbind used to be running it wasn't. Ran rpcbind -d manua= lly and then ran (same machine) rpcinfo localhost. rpcbind coredumps. GDB= says: > > (gdb) bt > #0 ?? () at /usr/src/lib/libc/amd64/string/strlen.S:95 from /lib/libc.so= .7 > #1 0x00001d9c3c5273a8 in xdr_string (xdrs=3Dxdrs@entry=3D0x3ba5fb06f808,= cpp=3Dcpp@entry=3D0x3ba5fb047460, maxsize=3Dmaxsize@entry=3D9000) > at /usr/src/lib/libc/xdr/xdr.c:701 > #2 0x00001d9c3c51b841 in xdr_rpcb (xdrs=3D0x3ba5fb06f808, objp=3D0x3ba5f= b047450) at /usr/src/lib/libc/rpc/rpcb_prot.c:63 > #3 0x00001d9c3c528df2 in xdr_reference (xdrs=3Dxdrs@entry=3D0x3ba5fb06f8= 08, pp=3Dpp@entry=3D0x1d9418ba7140 , > size=3Dsize@entry=3D40, proc=3Dproc@entry=3D0x1d9c3c51b7f0 = ) at /usr/src/lib/libc/xdr/xdr_reference.c:92 > #4 0x00001d9c3c51b943 in xdr_rpcblist_ptr (xdrs=3D0x3ba5fb06f808, rp=3D0= x1d9418ba7140 ) > at /usr/src/lib/libc/rpc/rpcb_prot.c:124 > #5 0x00001d9c3c5205e4 in svc_vc_reply (xprt=3D0x3ba5fb0208c0, msg=3D0x1d= 9c39a3d618) at /usr/src/lib/libc/rpc/svc_vc.c:646 > #6 0x00001d9c3c51c7ee in svc_sendreply (xprt=3D0x0, xprt@entry=3D0x3ba5f= b0208c0, > xdr_results=3Dxdr_results@entry=3D0x1d9c3c51b870 , = xdr_location=3D0x2328) at /usr/src/lib/libc/rpc/svc.c:368 > #7 0x00001d9418ba0f52 in rpcb_service_3 (rqstp=3D0x1d9c39a3d740, transp= =3D0x3ba5fb0208c0) > at /usr/src/usr.sbin/rpcbind/rpcb_svc.c:175 > #8 0x00001d9c3c51d08d in svc_getreq_common (fd=3D) at /us= r/src/lib/libc/rpc/svc.c:664 > #9 0x00001d9c3c51d118 in svc_getreq_poll (pfdp=3Dpfdp@entry=3D0x1d9c39a3= dcf0, pollretval=3D1) at /usr/src/lib/libc/rpc/svc.c:732 > #10 0x00001d9418ba3069 in my_svc_run () at /usr/src/usr.sbin/rpcbind/rpcb= _svc_com.c:1167 > #11 0x00001d9418b9f835 in main (argc=3D, argv=3D0x1d9c39a4= 0000) at /usr/src/usr.sbin/rpcbind/rpcbind.c:286 Yea, its busted alright. I reproduced the crash. It appears that the r_addr field has not been set to a string. (My current guess is that commit d50fc4b broke it for the netlink case.) I'll poke away at it and post if/when I have a patch for testing. If you just want to work around it, you could try a NFSv4 mount, which doesn't use rpcbind. rick > > > On Sun, Sep 14, 2025 at 8:51=E2=80=AFPM Rick Macklem wrote: >> >> On Fri, Sep 12, 2025 at 7:55=E2=80=AFPM Zaphod Beeblebrox wrote: >> > >> > My overall goal is to have a FreeBSD workstation before Windows 10 die= s. That's coming up pretty quickly, so I've been testing. Because FreeBSD= 's proton support is very much dependant on 15-CURRENT, I upgraded both the= new workstation and my poudriere box to the 15-current about 2 weeks ago. >> > >> > Now... normally, when the workstation boots, half a dozen NFS mounts t= o the poudriere server (also fileserver) occur. This has been the config s= ince ... well... since back to FreeBSD 4 or so. >> > >> > My workstation's fstab has lines of the form: >> > >> > vr:/vr1/tmp /d/vr/tmp nfs rw,-3,-T,-l,-i,-b 0 0 >> > >> > 'vr' being the hostname and so on. On vr, >> > [2:31:331]root@vr:~> zfs get sharenfs vr1/tmp >> > NAME PROPERTY VALUE SOURCE >> > vr1/tmp sharenfs -maproot=3Dnobody ump run local >> > >> > Now... for some number of upgrades, this spits out lines like "-i depr= ecated, use -o intr" ... which it still does --- but then it hangs ... for = one NFS time out and it moves onto the next share. No errors on either the= client or the server. What's changed here? Both machines were working be= fore the upgrade from 14.3 to 15-c. >> >> Those options are from the Jurassic period, but they should still work, = afaik. >> >> I suspect your mount problem is something related to networking >> (firewall or ipv4 vs ipv6 or ???). Note that NFSv3 does need rpcbind >> to be working. >> >> rick