From nobody Tue May 27 01:51:28 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 4b5wbf6jdTz5x8ht for ; Tue, 27 May 2025 01:51:42 +0000 (UTC) (envelope-from rick.macklem@gmail.com) Received: from mail-ed1-x529.google.com (mail-ed1-x529.google.com [IPv6:2a00:1450:4864:20::529]) (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 4b5wbf4dbnz3R1Y for ; Tue, 27 May 2025 01:51:42 +0000 (UTC) (envelope-from rick.macklem@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ed1-x529.google.com with SMTP id 4fb4d7f45d1cf-5efe8d9ebdfso5429761a12.3 for ; Mon, 26 May 2025 18:51:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1748310700; x=1748915500; 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=XiwbiD4ey+0ZOLwl5v0IsbDNEzkgU7Ex+dFDJfb6oNc=; b=S1tx2xiN1tLi8WHj7TAzCWbgAAxeVogjNNb2xud81qXlqjJg++jzS/ACx60epChrxV icC0kRvSPbQJ4Qv4I7YRNB7kvXrvDv2qD1QkNDdte90xCVGU4PMJeSYIq8wnQXoguj4y I91lD9IXaVJcRfJcgByP9tUdhDzkUjmMUB82bzpwBpWtHzzWG/B8PRkRicTH+cKBoDlT Z6ignBPWaIWTlFl38UHsq7Q4RbS6hd2TflkzsqXlEUtDIellzfhenIxo+4ITtqUVMffe i8WHWF9qAMCTFkFSZfT2+HmBjqGp82CK7ir5MzI58pUeWgX2jX9hfznSkuc3tTgIwRtV MZWQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1748310700; x=1748915500; 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=XiwbiD4ey+0ZOLwl5v0IsbDNEzkgU7Ex+dFDJfb6oNc=; b=hnmw4KBOUpId2fenx+bKG16pQCr56uU7aFdbwqoV9L5hh6M+5Dki/c9hGCXEfjJvTg cmBCAZB8Efm8LXUAMKnzUpbXHnhlik4f+htqPS+s5QcvMI9Lf7F78jTCN2sl61yjcegf 17IGVDu7BJY8NoQYsK4PAyf/tlhILc/Gcp0e6TEnTlDpTb0W37JS5wcjfHxhRVTRIluq Y2ULQNBdwpB8PLTFNS9vho5ZKcgtLJO4NJDheyM1tKoVm7Rwq/C0TrYg1UvXTP2ZT12e r1BZuSrMIE3DFcoJmEK9Hb2sZQ68qrePgjFON2MfazCvLQYlLnKcP2m+tOXiAl3zX5Io ObZA== X-Gm-Message-State: AOJu0YxVUMNy58nD1SEsTx/VN6uQWVnaFqVQzlHh63xxkXFnIf12/YTk DRYrie3j+YxR/qUHqMOjHLLu3eBL0/G9bQnpK71Qr5ljGkw43ZHP8OruimcRn+B8bP92Cu9bWx7 ezweL+cnhHeo8f5RSOWylGtpwdYblNw== X-Gm-Gg: ASbGnctUbdfdApcl4t6RBv21BdgTd9G74VF5LVR7SPZJMb3nFWuFIP2ABCPlE9/qgKz oqF9Q9uUkYbgNXjcTV9cG1jUwBC3Az+Fe3KKGQAE9vLjjYIUvlbAbL/o7Jyxgfut7AChiCfUZi/ acXw3SnrFkbAaf5Gq6q8/vnUb7nEFV1zIo X-Google-Smtp-Source: AGHT+IGfCF5o44M4rrxsA2/SF2rYAVOK0Z3C4BUiXazRO4nB/qs6C8w2rMGAzkMvVWOOA1U2ILyyAfLDij5JWDFfgBY= X-Received: by 2002:a05:6402:5242:b0:604:b953:f805 with SMTP id 4fb4d7f45d1cf-604b9545706mr5022884a12.3.1748310700404; Mon, 26 May 2025 18:51:40 -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: <20250526162557.97D6C318@slippy.cwsent.com> In-Reply-To: <20250526162557.97D6C318@slippy.cwsent.com> From: Rick Macklem Date: Mon, 26 May 2025 18:51:28 -0700 X-Gm-Features: AX0GCFsDXP1Osay69DHjU3-LcqwIkBTPviwvRvirNqfl4GERGBIa39JryYSBqqM Message-ID: Subject: Re: mountd(8) Hangs To: Cy Schubert Cc: freebsd-current@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4b5wbf4dbnz3R1Y X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; TAGGED_FROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Spamd-Bar: ---- On Mon, May 26, 2025 at 9:26=E2=80=AFAM Cy Schubert wrote: > > I've noticed over the past month or so mountd(8) hanging on an NFS server > here when the NFS server is running poudriere. This only occurs when > poudriere is building multiple little ports resulting in many mounts and > unmounts due to jails being constituted and torn down. After a while > mountd(8) ends up in a deadlocked state causing poudriere to seize. I cannot think why poudriere would care about mountd being hung? > The > workaround is to stop mountd before or immediately following initiation o= f > poudriere. Well, there is code in mountd.c that prevents it from reloading exports too often. RELOADDELAY is set to 0.25sec. However, this code has not changed in a long time, so unless clock_gettime() has somehow changed, I cannot see why it would have stopped working? The commits during the last month or so for mountd.c are pretty benign, but you could try reverting one or two of them. (One moves some of the code into libutil, but I cannot think why that might matter?) The only commit I did (on May 1) was 68daa78, which just adds one additiona= l check to the exports processing. You can easily revert this one to see if i= t makes any difference? Can you see where the mountd process is stuck with something like # ps axHl to see if it is hung in the kernel and, if so, what the wchan is? or try sending it a SIGHUP when it is hung to see if that brings it back to life? rick > > This used to be a problem without the -S flag but now suspend/resume of > nfsd threads doesn't mitigate the problem either. > > Something has changed but I cannot point to any individual commit or grou= p > of commits that caused this regression. > > > -- > Cheers, > Cy Schubert > FreeBSD UNIX: Web: https://FreeBSD.org > NTP: Web: https://nwtime.org > > e^(i*pi)+1=3D0 > > >