[Bug 230752] panic: excl->share in newnfs_request
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Wed Aug 22 10:56:19 UTC 2018
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230752
--- Comment #4 from Dimitry Andric <dim at 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=nfsnobody:nfsnobody -network 192.168.0.1/24
/share -maproot=nfsnobody:nfsnobody -network 192.168.0.1/24
/usr/obj /usr/src -maproot=nfsnobody: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="NO" # This host is an NFS client (or NO).
nfs_server_enable="YES" # This host is an NFS server (or NO).
nfsv4_server_enable="YES" # Enable support for NFSv4
nfscbd_enable="NO" # NFSv4 client side callback daemon
nfsuserd_enable="YES" # NFSv4 user/group name mapping daemon
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-fs
mailing list