From nobody Mon May 29 15:52:18 2023 X-Original-To: freebsd-stable@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 4QVKmG509gz4XyZs for ; Mon, 29 May 2023 15:52:30 +0000 (UTC) (envelope-from rick.macklem@gmail.com) Received: from mail-pg1-x52e.google.com (mail-pg1-x52e.google.com [IPv6:2607:f8b0:4864:20::52e]) (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 4QVKmG2bZwz3rky for ; Mon, 29 May 2023 15:52:30 +0000 (UTC) (envelope-from rick.macklem@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-pg1-x52e.google.com with SMTP id 41be03b00d2f7-5304d0d1eddso1644231a12.2 for ; Mon, 29 May 2023 08:52:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1685375549; x=1687967549; 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=8buNjQ08DMZ0U0cA5NUxxJwyab3K1LoGkjf00fh5Xf4=; b=VGAoF2mjqyCU2C195Ujph8CtS57CEgVW646eRge7fZ1ehkTZVsKEm5Xr8HheSDmGHM 0key4rLzTfgE8fRD3R+8iWsl+ygIUajrjf5TnhUnjoFGMVIOs3utW0CeUkY65F+TU27K nbiiiQSkPmu1lW+mOd0zfwx+5QtuVn0MBoX2ee3GHaGpNNWr9WmlN0YXXCJFHXlqupUQ hBEGSyTdotQwtYALbo/Xv+BB0ypDdqdQb+Rd6ad4jZMBJt0/laY59MmWoUIgJ52097ZZ ZQ3oLm86CgsKs4N4u140i6zPNm8UehjhrhDdKEB+1Ikqbm/XSXeHRi84O2eISOQnb9B9 FwOg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1685375549; x=1687967549; 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=8buNjQ08DMZ0U0cA5NUxxJwyab3K1LoGkjf00fh5Xf4=; b=g2gz6y54R7U24QLWDqdPo2U8XmTJDAIiFUWLK6QIV9du9xAe/BIRBdnlWtEQ+k/Cu+ FoMMn+u5seoypQaPw+fGwe7K6iMSFQTYNGp4nRQLhorDUK9h6xcpVPdxD7C3G29XdWvs mWCAEWy7j/AiDB3wHGBSyVl4U3XePMGVhx9ezAZVad3r7dWLmi74v+fsBdYKJgIDorXB cDR5y0U7XpwJzM/19gp2b1Smg+wokJTJg0AZW1P8qDVQFaX0MUlVrBdK7mrgk5O1R6WB dY9J2oj7CJZb4wY18+OHFBN595H5UJKd9xN/g3dZ1EBhIPpmS6iMUsRlZVhq0KspE2Ds TRGg== X-Gm-Message-State: AC+VfDylgfBbArQJ/yKs2YTplVz6ii7VX12HjhnaYkxmef+9TKk16J/g wff9gglh3n/iwXqLY/UAihRKrIdEzvLJE1GSL42jAyep5//3 X-Google-Smtp-Source: ACHHUZ6EWduHs8wIlmityEh3PM4vOsUIp/iCjgmE1wR9YHrWz8iP6Tequw8snUR2Txc3FcYQ6qFLSZCCjyKeP8iXEjM= X-Received: by 2002:a17:903:2342:b0:1ac:7b13:de71 with SMTP id c2-20020a170903234200b001ac7b13de71mr16320587plh.37.1685375548999; Mon, 29 May 2023 08:52:28 -0700 (PDT) List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 References: <4943d4e5b65716a7a72cc11f1db251e2@glaver.org> In-Reply-To: <4943d4e5b65716a7a72cc11f1db251e2@glaver.org> From: Rick Macklem Date: Mon, 29 May 2023 08:52:18 -0700 Message-ID: Subject: Re: Sorry to mail you directly with a NFS question... To: Terry Kennedy Cc: freebsd-stable@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4QVKmG2bZwz3rky X-Spamd-Bar: ---- 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-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N Since the reply ended up at the end of the long email, I'll post it here as well. On Sun, May 28, 2023 at 5:55=E2=80=AFPM Terry Kennedy wrote: > > [This is the first time I'm trying to use the new FreeBSD > list serer, and it is behaving really bizarrely - it stripped > out the attachment in my first message, and when I sent the > attachment in a subsequent email, it REPLACED my prior email > which has vanished. I'm trying to reconstruct what I said. > Fortunately I still have the hung terminal windows open so > I have that data.] > > I can easily reproduce this bug by editing a file on the > NFS filesystem, making a trivial change and doing "save and > exit" - instant hang. > > I gathered the data Rick requested which is in my previous > post. > I'm afraid that nothing here indicates what the problem is, from what I can see at a quick glance. The only thing I can think of is that your "save and exit" might use byte range locking and rpc.lockd is flakey at best. If file locking does not need to be seen by other clients, you can use the "nolockd" mount option to do the file locking locally within the client. If other clients do need to see the locks (files being concurrently accessed from multiple clients), then NFSv4 does a much better job of file locking. (Since your server is quite old, I am not sure if switching to NFSv4 would be feasible for you.) Maybe others have some other ideas, rick > In another terminal window on the 13.2 system (165h) with > the hang, both filesystems show up, even after the hang: > > (0:19) 165h:/tmp# df -h > Filesystem Size Used Avail Capacity Mounted on > ... > gate:/usr/local/src 7.7G 3.3G 3.8G 46% /usr/local/src > gate:/sysprog 62G 22G 35G 39% /sysprog > ... > > In that other terminal window, I can create a file with > 'touch' (and it is indeed created, looking at the directory > from other clients running 12.4). But any attempt to list > the directory results in a hang: > > (0:22) 165h:/tmp# touch /usr/local/src/envir/foo > (0:23) 165h:/tmp# ls /usr/local/src/envir > load: 0.00 cmd: ls 97107 [nfs] 25.89r 0.00u 0.00s 0% 2864k > load: 0.00 cmd: ls 97107 [nfs] 52.44r 0.00u 0.00s 0% 2864k > load: 0.00 cmd: ls 97107 [nfs] 175.41r 0.00u 0.00s 0% 2864k > > In yet another terminal window, a create + write (as opposed > to just a "touch") hangs: > (0:2) 165h:/sysprog/terry# echo "Testing 123" > /usr/local/src/envir/bar > load: 0.00 cmd: tcsh 97128 [nfs] 61.17r 0.02u 0.00s 0% 4248k > load: 0.01 cmd: tcsh 97128 [nfs] 2736.92r 0.02u 0.00s 0% 4248k > > From another 12.4 client that has the same filesystem mounted, > things continue to work normally: > > (0:634) new-gate:~terry# echo "Testing 123" > /usr/local/src/envir/baz > (0:635) new-gate:~terry# cat /usr/local/src/envir/baz > Testing 123 > > Based on this, I think it is a client-side problem on the > 13.2 system. >