Date: Sun, 8 Oct 2023 22:34:27 -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: <CAM5tNy5HfLFAaUK361VTE7-Q=dFRABj8Qhz4r9apHeqkdn-VkQ@mail.gmail.com> In-Reply-To: <CABXB=RSDyMPGotpjrN-rUnRwQqRVz6%2B%2BFb_XSREuwmRRj3g31w@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>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Oct 8, 2023 at 8:32=E2=80=AFPM J David <j.david.lists@gmail.com> wr= ote: > > On Sat, Oct 7, 2023 at 3:08=E2=80=AFPM Rick Macklem <rick.macklem@gmail.c= om> wrote: > > One thing you could try is running the nfscbd(8) daemon. > > [...] > > Maybe this server will be happier with the callback path working? > > Unfortunately, this avenue of inquiry proved unfruitful. Due to the > warning on the man page, I removed oneopenown before enabling nfscbd. > Over the course of the next few hours, that drove system load and CPU > usage through the roof, with LocalOwn and LocalOpen continually > increasing into the tens of millions. That must be the nfscbd version > of the OpenOwner problem. LocalOwn and LocalOpens indicate that the server did start issuing delegations. I guess you do need to not run the nfscbd(8). It is odd that the number of opens would increase dramatically. All I can think of is that you have an environment where the same file(s) get open'd by multiple processes. A NFSv4 close cannot occur until a file has no open references. --> No process has the file open. The "oneopenown" option at least ensures that there is a single open owner (without it, each process is a separate open owner). rick > > Thanks!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAM5tNy5HfLFAaUK361VTE7-Q=dFRABj8Qhz4r9apHeqkdn-VkQ>