From nobody Sun Apr 14 19:20:36 2024 X-Original-To: freebsd-fs@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 4VHgBT54Hzz5GvVc for ; Sun, 14 Apr 2024 19:20:49 +0000 (UTC) (envelope-from rick.macklem@gmail.com) Received: from mail-pf1-x42a.google.com (mail-pf1-x42a.google.com [IPv6:2607:f8b0:4864:20::42a]) (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 4VHgBT3RbVz4gsW for ; Sun, 14 Apr 2024 19:20:49 +0000 (UTC) (envelope-from rick.macklem@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-pf1-x42a.google.com with SMTP id d2e1a72fcca58-6ed32341906so2114519b3a.1 for ; Sun, 14 Apr 2024 12:20:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1713122447; x=1713727247; 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=aBod3/UtHg9at//fe7tusWFRVJb5Xpg/VV2hvzH6Tk0=; b=ir1C6uxoASAbs4NT9+Ypp3DgGA7NCXDl+KyhsAk1v6tMLLiUQKRkhbeKRpVD47D3QO apXCWFvh0U4e0Kt6PeN7VVio4eFMGBwb6Yd3p4WK14evqogLZwjatocxMltCiGeGKRyu wTYMA94N5Ha159sCmsMPx5tY9M+oqjg34QqZurBSxyGxHIFBDAjn2lr5MqkEIQ93PXPt 5t+dr4jU3q8rb5DvdvbAeaTix9qCEw1vCdrZIc9X6BmLttGOn5AXM1Mw+qf2KHqVWyPG MouEokMtDFHDh58dGjrneUepyZW83WqnFYfG5U6jr4IX1Q+4Couqdel5/K0n1TXKV+Cs 9mdg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1713122447; x=1713727247; 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=aBod3/UtHg9at//fe7tusWFRVJb5Xpg/VV2hvzH6Tk0=; b=sK6bH32wWBPQrJJ4Cl8tjwhS3NblrsqOThVuw2d5OSdajMTtx05QbAx9F/Dpv87I54 0rCpp2AGT1ZX7YYZUfZ78h+nk2sAbctcvEu+Izuqnvv30DfRVy0cCYNX6JzsEIHOZV4B 1Z9YKaSG/k/tE/OoRQG1iMcHh23Uvjz+k81Tz0aK+Nzy3sWCrDAHGn46QiqHuMEcQ/5B JX67feW5KOGEOPUg3d003DYQqrX3zO+Y7sV1X1lEEuZEqXRlnqlJRsFoDlMbSwG9aiwI jJ3X0ys31hAecFvg/dtCL8HBjEVlC5rFSMpF4wM9mm0MGiASCYOgIXN4BSf6YmLpZNGF 5zFQ== X-Gm-Message-State: AOJu0YzVTZQmHHjL+PztKmtdlBbmTxlLvUi7JzXCpLlGacBgN7p19iXP j2TwlN6hztySBNDp67nd/lm/igoh1rPLA2PIP61EgTEXc51v4zr4tlqx35ZduOvM7EzPUKBBE20 fCRsjOQYPqxVkDUQkMzpqWumYvA== X-Google-Smtp-Source: AGHT+IHYExZ/ufRmF35eO3UCH2K5NuNfTk5AbC7UTbUZnpo3+6NzsSlBKGua9+DVes5d5cOofL+PWF9cfo2lPYWc/nc= X-Received: by 2002:a05:6a20:daa7:b0:1a7:3b7c:3126 with SMTP id iy39-20020a056a20daa700b001a73b7c3126mr7497277pzb.5.1713122447280; Sun, 14 Apr 2024 12:20:47 -0700 (PDT) List-Id: Filesystems List-Archive: https://lists.freebsd.org/archives/freebsd-fs List-Help: List-Post: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 References: In-Reply-To: From: Rick Macklem Date: Sun, 14 Apr 2024 12:20:36 -0700 Message-ID: Subject: Re: Automount + NFS hang issues (follow-up to FreeBSD 12.3/13.1 NFS client hang thread) To: Andreas Kempe Cc: "freebsd-fs@freebsd.org" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spamd-Bar: ---- 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:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4VHgBT3RbVz4gsW On Sun, Apr 14, 2024 at 8:48=E2=80=AFAM Andreas Kempe wrote: > > Hello, > > I'm doing a follow-up on the thread FreeBSD 12.3/13.1 NFS client hang, > message ID YpEwxdGCouUUFHiE@shipon.lysator.liu.se. > > After having had recurring issues ever since that thread and not > managing a good tcpdump of a hang, I decided to simply get rid of > automount and instead mount the NFS shares via the fstab. With the > mounts being done via the fstab instead of automount, the NFS server > restarting causes processes using the mount to hang, but when the > server comes back things recover. > > When using automount as the NFS server becomes unresponsive, the > system log is filled with lines like > > 7 Apr 10 13:00:14 shipon kernel: WARNING: autofs_trigger_one: request = for /home/ completed with error 60, pid 68836 (fish) > 8 Apr 10 13:00:14 shipon kernel: WARNING: autofs_trigger_one: request = for /home/ completed with error 60, pid 69248 (sshd) > 9 Apr 10 13:00:14 shipon kernel: WARNING: autofs_trigger_one: request = for /home/ completed with error 60, pid 2221 (weechat) > > and it seems like automount is repeatedly trying to perform mounts > until the system eventually hangs. When the system has hung, all > automount processes are stuck in the kernel in uninterruptable sleep > in the NFS code. You can find some stack traces in the old thread. > Sometimes a umount -N on all the mounts would solve the issue, but > often a system reboot was the only way to recover. I might take another look, but I have never been involved in the automount = code and never use the automounter, so I doubt I'll figure out how to fix it. rick > > Best regards, > Andreas Kempe >