|Summary:||knfsd can't export across mountpoints, user-space nfsd not available|
|Product:||[Retired] Red Hat Linux||Reporter:||jered|
|Component:||knfsd||Assignee:||Cristian Gafton <gafton>|
|Status:||CLOSED NOTABUG||QA Contact:|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2000-02-17 15:40:33 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
Description jered 1999-10-24 23:09:10 UTC
In RedHat 6.0, the user-space nfs server was replaced with knfsd. knfsd will not export across local mount points. The other mount points can be listed in /etc/exports, but they must be individually mounted by the client machines. This is different behaviour than earlier releases, and is not desireable. As there seems to be no easy way to fix this, I want to use the user-space NFS server. Even though the kernel-space NFS is still considered experimental, RedHat has made it the default and not even provided the user-space server as an option! Bring back the user-space server as an optional package until the kernel-space server has equivalent functionality!
Comment 1 Jeff Johnson 1999-11-05 13:14:59 UTC
*** Bug 6680 has been marked as a duplicate of this bug. *** i have / exported to another computer. Everything works fine , until I attempt to enter a directory which is mounted from a seperate partition , say , /dos , instead of /sbin. An empty directory is all that is brought up. I have Sun NFS server compiled into my kernel. I can't see why it isn't working. I'm running 2.2.13 , now. 2.2.12-20 didn't work either. I suspect this might be a bug in knfsd? ------- Additional Comments From firstname.lastname@example.org 11/03/99 11:08 ------- apologies, this is a repeat of bug #6317, which I should have checked for more carefully.
Comment 2 Alan Cox 2000-02-17 15:40:59 UTC
This is how all normal NFS daemons work. They expect you to export and mount each mount point you need. Without doing this you get potential clashing file handles - a problem unfsd has in such configurations that can cause bogus 'Stale NFS handle' and othr such messages.