Re: Bugs in knfsd -- Problem re-exporting an NFS share

[Jorge L. deLyra]

> Date: Wed, 3 Jan 2001 11:52:36 +0100
> From: Andi Kleen <[e-mail]>
> To: "Jorge L. deLyra" <[e-mail]>
> Cc: Neil Brown <[e-mail]>,
>     Andrzej Krzysztofowicz <[e-mail]>,
>     [e-mail], kernel list <[e-mail]>
> Subject: Re: Bugs in knfsd -- Problem re-exporting an NFS share
> 
> On Wed, Jan 03, 2001 at 08:37:08AM -0200, Jorge L. deLyra wrote:
> > It would be nice if a way was found to implement this feature on knfsd.
> 
> There is: just run unfsd too, bound to an own IP address to not conflict. 

Hum, interesting, I didn't know you could run both servers at the same
time. The problem is that the old server is not being developed any more,
as dully advised on the 2.2.18 kernel help messages. In fact, we have been
having some problems with it for some time, I/O errors and mounts hanging,
mostly. In fact, upgrading to 2.2.18 broke old NFS exports in some cases
around here, until we migrated to knfsd: gave us sure-fire I/O errors and
hangs. So this might be a stopgap measure for some time, but no permanent
solution. In any case, knfsd seems so much more solid, we want to use it!

> More efficient would probably be a proxy though that just forwards packets.
> I see no reason in core NFS why multiple clients could not share a single 
> multiplexed mount. It could need some lockd support though. 

I'm afraid you lost me here... If this would have to be some kind of new
daemon or kernel module that filters out NFS packets and forwards them,
wouldn't this be equivalent to making knfsd do the same thing? Humm, on
second thoughts, maybe not, because this beast would not have to interpret
the mount as a filesystem on the front end. Am I following you correctly?

----------------------------------------------------------------
        Jorge L. deLyra,  Associate Professor of Physics
            The University of Sao Paulo,  IFUSP-DFMA
       For more information: finger [e-mail]
----------------------------------------------------------------