Date: Tue, 22 Jun 2021 01:58:20 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 254282] 13.0-RC2: NFS export from nullfs mount doesn't work as of 13.0 Message-ID: <bug-254282-3630-p0hNFct2ye@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-254282-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-254282-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=3D254282 Rick Macklem <rmacklem@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rmacklem@FreeBSD.org --- Comment #2 from Rick Macklem <rmacklem@FreeBSD.org> --- The problem is your specification of "late" on the nullfs mount lines. If you look in /etc/rc.d, you'll find "statd" requires "nfsd", which requires "mountd". However, it specifies BEFORE DAEMON. "mountlate" requires DAEMON. --> As such, mountd is executed before mountlate, which is what mounts the "late" file systems. To fix this, you could: - Drop "late" from the /etc/fstab lines, if you don't need to mount them "late". or - If you don't run rpc.statd and rpc.lockd, you could remove DAEMON from "statd" and "lockd" and then add "mountlate" to the REQUIRES line in "mountd". I don't know why this worked for FreeBSD-12, but I suspect that some DAEMON related dependency was added to the scripts (ie. they were broken). - Although rpc.statd and rpc.lockd are NFSv3 related protocols I avoid using, they need to be running before nfsd (for server side locking) and NFS mounts are done for client side locking, if you are using them. I can't think of a way to fix this so that mountd can start after "mountlate" and still work correctly, for those who are using rpc.statd, rpc.lockd. --=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-254282-3630-p0hNFct2ye>