Date: Thu, 13 Nov 2025 16:51:20 -0800 From: Mark Millard <marklmi@yahoo.com> To: Ronald Klop <ronald@freebsd.org>, rick.macklem@gmail.com, freebsd-fs@freebsd.org Subject: Re: nfs hang Message-ID: <A3D0678A-F5AC-449A-BC71-13D61F2D4A04@yahoo.com>
index | next in thread | raw e-mail
Ronald Klop <ronald_at_FreeBSD.org> wrote on Date: Thu, 13 Nov 2025 17:17:48 UTC : > Op 13-11-2025 om 14:06 schreef Rick Macklem: > > On Thu, Nov 13, 2025 at 2:45 AM Ronald Klop <ronald@freebsd.org> wrote: > >> > >> Op 13-11-2025 om 11:41 schreef Ronald Klop: > >>> . . . > >>> > >>> > >> > >> > >> . . . > > Do you have more than one client mounting the file system? > > If you do, make sure they all have different /etc/hostid's. > > (Cloning a system disk without deleting /etc/hostid can > > result in multiple clients with the same /etc/hostid. That > > mean they are "the same client" to the NFSv4 server > > and that can cause the above.) > > > > If this is not the problem, I don't know why you'd see the > > above but I suspect the above explains the hang. > > > > rick > > > > > Two clients. Both have different /etc/hostid. > > I noticed that the procstat stacks start with "null_reclaim". And poudriere null-mounts the nfs mounts in the poudriere-jails. Do the poudriere jails on each host use the host's /etc/hostid (by content)? Any worries about needing poudriere jail /etc/hostid content uniqueness? > Could nfs+nullfs give some trouble? Or maybe it is just nullfs that hangs everything and the nfs stuff is just a result of it. > > At the same moment I had git hanging on a non-NFS mount. See attachment for the procstat which also includes nfs-calls. === Mark Millard marklmi at yahoo.comhelp
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A3D0678A-F5AC-449A-BC71-13D61F2D4A04>