Date: Mon, 9 Oct 2023 09:03:13 -0700 From: Rick Macklem <rick.macklem@gmail.com> To: J David <j.david.lists@gmail.com> Cc: FreeBSD FS <freebsd-fs@freebsd.org> Subject: Re: FreeBSD 13.2 NFS client mount hangs Message-ID: <CAM5tNy5ef=2ApMAhHGhXf8f6jg99gcOLcPubas%2B8PaPJqpAc4Q@mail.gmail.com> In-Reply-To: <CABXB=RRa-0N7y2zX3jam2BVgOip0Zc3vubov7CRWmJwn=2SgWg@mail.gmail.com> References: <CABXB=RRSHMhZQFL28eHKjhAYmU87qjpQ=B1=8VRSZoXat9=r5A@mail.gmail.com> <CAM5tNy4sqc18UCZF0vgL%2BXP6vF0wgt_3Yi07yY4wqeuzs6haMA@mail.gmail.com> <CABXB=RSUJ3mpYF5puAm0hSxeavozxyf7Ruab8mPrtBOu6bxM-w@mail.gmail.com> <CAM5tNy52x2s=9Os%2BPAa=-iz7F_o_4_9XxJbRAR28V1v9A4nN6A@mail.gmail.com> <CABXB=RT14gofYHkMMr8cj%2BTy2QRUgn6zunho4T2Kq2NxAWmuAQ@mail.gmail.com> <CAM5tNy7AK7Hq%2Bnnxftg=s5wk=YHw27F7EBydLX=D_z1KvFuD_Q@mail.gmail.com> <CABXB=RS466mdJvPLBZw0MfL%2BgzPjSr8kiHoRiCcdAveNxnGUgg@mail.gmail.com> <CAM5tNy5H%2B7wZVfVupW2MMt61CQ_tOW--rGrYKn_Ob7u=D1MEXA@mail.gmail.com> <CABXB=RSDyMPGotpjrN-rUnRwQqRVz6%2B%2BFb_XSREuwmRRj3g31w@mail.gmail.com> <CAM5tNy5HfLFAaUK361VTE7-Q=dFRABj8Qhz4r9apHeqkdn-VkQ@mail.gmail.com> <CABXB=RRa-0N7y2zX3jam2BVgOip0Zc3vubov7CRWmJwn=2SgWg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Oct 9, 2023 at 2:37=E2=80=AFAM J David <j.david.lists@gmail.com> wr= ote: > > On Mon, Oct 9, 2023 at 1:34=E2=80=AFAM Rick Macklem <rick.macklem@gmail.c= om> wrote: > > LocalOwn and LocalOpens indicate that the server did start issuing > > delegations. > > Yes, with that enabled, the Delegs value from "nfsstat -Ec" climbs > into the low thousands. Performance does seem (gut feeling, not > tested) to be improved until the LocalOwns/LocalOpens pile up. > > > All I can think of is that you have an environment where the > > same file(s) get open'd by multiple processes. > > Yes. > > > The "oneopenown" option at least ensures that there is a single > > open owner (without it, each process is a separate open owner). > > I don't know what issue the "It may not work correctly when > Delegations are being issued by a server" warning about oneopenown > refers to. > > Would that potential problem still be a concern if the only filesystem > mounted with oneopenown were also mounted readonly and with nolockd? > (Specifically: ro,nfsv4,minorversion=3D2,tcp,nosuid,noatime,nolockd,oneop= enown) Yes. With "oneopenown" all NFSv4 Opens (not the same as a POSIX open, they are a Windows like open lock) are tied to the same open_owner string. Howev= er, local opens are tied to open_owner strings that are created from the proces= s. --> As such, delegations and "oneopenown" do not mix well. rick > > Thanks!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAM5tNy5ef=2ApMAhHGhXf8f6jg99gcOLcPubas%2B8PaPJqpAc4Q>