Date: Wed, 22 Aug 2018 10:56:16 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 230752] panic: excl->share in newnfs_request Message-ID: <bug-230752-3630-ENlVGN3sh3@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 #4 from Dimitry Andric <dim@FreeBSD.org> --- (In reply to Rick Macklem from comment #3) > Sorry, to clarify...I was wondering if the machine that panic()'d > had its /var/run exported to NFS client(s) that would have it mounted via > NFS. > (If that was the case, it could be a case where the nfsd thread is doing > a Getattr on /var/run/nfsuserd.sock and then it tries to connect to > /var/run/nfsuserd.sock to do the upcall to the nfsuserd.) > --> I think I'll need to make it still use UDP sockets by default (since > this could happen when the socket is in the namespace). No, it's only exporting other directories. /etc/exports looks like this: /archive -maproot=3Dnfsnobody:nfsnobody -network 192.168.0.1/24 /share -maproot=3Dnfsnobody:nfsnobody -network 192.168.0.1/24 /usr/obj /usr/src -maproot=3Dnfsnobody:nfsnobody -network 192.168.0.1/24 V4: / -network 192.168.0.1/24 The following nfs related settings are in /etc/rc.conf: nfs_client_enable=3D"NO" # This host is an NFS client (or NO). nfs_server_enable=3D"YES" # This host is an NFS server (or NO). nfsv4_server_enable=3D"YES" # Enable support for NFSv4 nfscbd_enable=3D"NO" # NFSv4 client side callback daemon nfsuserd_enable=3D"YES" # NFSv4 user/group name mapping daemon --=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-ENlVGN3sh3>