Date: Wed, 22 Aug 2018 17:11:50 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 230752] panic: excl->share in newnfs_request Message-ID: <bug-230752-3630-Mrcm0gyawl@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-230752-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-230752-3630@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D230752 --- Comment #8 from Dimitry Andric <dim@FreeBSD.org> --- (In reply to Rick Macklem from comment #5) > Hmm. I notice you do have the "V4: / =E2=80=A6" line in your /etc/exports. > Do you know if there are clients doing an NFSv4 mount from "/"? > Something like: > mount -t nfs -o nfsv4 nfs-client:/ /mnt Yes, most clients use NFSv4, via /etc/fstab lines: nfssrv:/archive /archive nfs rw,intr,soft,nfsv4 0 0 nfssrv:/share /share nfs rw,intr,soft,nfsv4 0 0 I migrated most of them from NFSv3 a month or two ago. This panic started appearing relatively recently, for example when doing buildworlds from /sha= re (where freebsd sources are). > I think I will end up reverting the "use AF_LOCAL" socket patch, > since that is what is causing the soconnect() on the socket and > should definitely make the panic()s go away. > (It did fix a problem with using UDP when jails were enabled, but > that can be fixed less elegantly with a patch that adds a command > line argument for an alternate IP# instead of 127.0.0.1.) I'll check it out, thanks. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-230752-3630-Mrcm0gyawl>