From nobody Fri Aug 25 01:52:12 2023 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 4RX2yQ1nTPz4qdl1 for ; Fri, 25 Aug 2023 01:52:30 +0000 (UTC) (envelope-from rick.macklem@gmail.com) Received: from mail-pj1-x1030.google.com (mail-pj1-x1030.google.com [IPv6:2607:f8b0:4864:20::1030]) (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 4RX2yP4G5jz4Zyg for ; Fri, 25 Aug 2023 01:52:29 +0000 (UTC) (envelope-from rick.macklem@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20221208 header.b="hrjZuj/7"; spf=pass (mx1.freebsd.org: domain of rick.macklem@gmail.com designates 2607:f8b0:4864:20::1030 as permitted sender) smtp.mailfrom=rick.macklem@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-pj1-x1030.google.com with SMTP id 98e67ed59e1d1-269304c135aso270667a91.3 for ; Thu, 24 Aug 2023 18:52:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1692928348; x=1693533148; 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=80OdSLFa9m6xn/NuSTMX99LTKl5z0hkKRl7faKMn56I=; b=hrjZuj/7+B64eGXo78jOI+ClV6E69ZsQ1AbKaHX+fwDAssSlBcjJHSVFrQ9ycq1g2H mKMF5u/sqABI6jtfcz6hijix3vOoizNweVm8dQbgnBPfoNh4kGJXox1bMy/49FYHhKPU Prf1VwrFwKO90q6NMw5UqXGF0TqldW/FrrxtDDs6XBwHvdGDt0D4k/+K2rWzXWfvvLvO 1nxBGbIgoM9dTHVqq2Y2kk/tX0KarSlMt09e2j5eXXx7W+XkQIIIlQaCk6gYC34UFLxy rv8ZRSQR5ucB5I0fd9VjF4Qsl7mllx5qJLv9NDIhCM2RslthiLnPZ0/wcaDP6KWvlqH+ Wkow== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1692928348; x=1693533148; 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=80OdSLFa9m6xn/NuSTMX99LTKl5z0hkKRl7faKMn56I=; b=JAanXZsXRhGH6wJog9OiLOKy2opFf6z8PDF1OPfjR23IOOlY8xx0fr6ZF1y+wujohW TAb2ZWC4prkgXc3euB/LDO8kVDT/ILAO2zFPoejKBRrPd86xDDJeI8Ow8QUpqxnCxe7d yjVpntDVppEivmzhaUBhbzWrygoXVQCV84D1jJuZz3fT3oPZFRUkLtmgxDAZw9JYuMXX PEBmOfkqICF4IgVKrCmjBjw28WfJi4PFcysMdpd2aRntYkbYbHrBOmUTya1D0LaoCgJT QlOlg8R3swaClU+O3IrkW99qd8IC4obxJdveMOsffnOoBAUoJYSVUZOCgw48RY9cudg9 VtZg== X-Gm-Message-State: AOJu0YwXl2od/mhvCyHF+jp8HI10k9njKQ1fAzGMezgf5gL4ae9oBniL zuC6oDQnnk0tR+mrH/5fVioJDzWRRi/9JZeUmA== X-Google-Smtp-Source: AGHT+IEbpbgLJy0cprmfzbpwufWqeI1Gi9Z72WEexGSqQZlcDMpM89TfRgouXSlwkYzcz33HFLx1OYIyPhJ3StW15c0= X-Received: by 2002:a17:90b:1642:b0:26f:2998:fc56 with SMTP id il2-20020a17090b164200b0026f2998fc56mr16237714pjb.25.1692928347856; Thu, 24 Aug 2023 18:52:27 -0700 (PDT) List-Id: Filesystems List-Archive: https://lists.freebsd.org/archives/freebsd-fs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-fs@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Rick Macklem Date: Thu, 24 Aug 2023 18:52:12 -0700 Message-ID: Subject: Re: NFS client hang on 13.2-RELEASE-p2 on file locking / wrong interface selected To: J David Cc: FreeBSD FS Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spamd-Result: default: False [-3.93 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.93)[-0.932]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36:c]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20221208]; MIME_GOOD(-0.10)[text/plain]; FROM_HAS_DN(0.00)[]; TAGGED_RCPT(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; PREVIOUSLY_DELIVERED(0.00)[freebsd-fs@freebsd.org]; ARC_NA(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::1030:from]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; MLMMJ_DEST(0.00)[freebsd-fs@freebsd.org]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; TO_DN_ALL(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; TAGGED_FROM(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_TO(0.00)[gmail.com]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[] X-Spamd-Bar: --- X-Rspamd-Queue-Id: 4RX2yP4G5jz4Zyg On Thu, Aug 24, 2023 at 10:25=E2=80=AFAM J David = wrote: > > On Thu, Aug 24, 2023 at 10:02=E2=80=AFAM Rick Macklem wrote: > > Otherwise consider switching the mounts to NFSv4.1/4.2. > > Unfortunately, NFSv4 is worse. > > Under NFSv4.2, attempts to lock files that previously did not exist on > NFS servers work, but any attempt to lock an existing file, regardless > of permissions, inexplicably fails with "Permission denied." > > E.g.: > > $ lockf -k x sleep 3 && echo OK > OK > $ lockf -k x sleep 3 && echo OK > lockf: cannot open x: Permission denied Here's a snippet from "man lockf" -w Causes lockd to open file for writing rather than reading. This is necessary on filesystems (including NFSv4) where a file which has been opened read-only cannot be exclusively locked. I am pretty sure this is in 13.2, although I do not remember when it was added to "lockf". rick > $ rm x > $ lockf -k x sleep 3 && echo OK > OK > $ ktrace lockf -k x sleep 3 && echo OK > lockf: cannot open x: Permission denied > $ echo "what" >x > $ cat x > what > > From ktrace: > > 98614 lockf CALL > openat(AT_FDCWD,0x295c0979e8f1,0x224,0666) > 98614 lockf NAMI "x" > 98614 lockf RET openat -1 errno 13 Permission denied > > Thanks!