Re: nfs stale filehandle issues with 2.6.10-rc1 in-kernel server

[Jakob Oestergaard <jakob@unthought.net>]

On Tue, Nov 02, 2004 at 08:37:04AM -0800, Trond Myklebust wrote:
> ty den 02.11.2004 Klokka 16:02 (+0400) skreiv Brad Campbell:
> 
> > /raid 192.168.2.81(rw,async,no_root_squash)
> > /raid 192.168.3.80(rw,async,no_root_squash)
> > /raid0 192.168.2.81(rw,async,no_root_squash)
> > /raid0/tmp 192.168.2.81(rw,async,no_root_squash)
> > /raid2 192.168.2.81(rw,async,no_root_squash)
> > /raid2 192.168.3.80(rw,async,no_root_squash)
> > /nfsroot 192.168.2.81(rw,async,no_root_squash)
> 
> You should only have 1 line per directory.

But exportfs won't complain about this.

Additionally, it seems to be allowed to use NIS netgroups in the exports
file, except, well, it "sort of doesn't quite entirely always work".
The best part of course being the errors you get: None on the server -
but mounts might misbehave randomly at some point in the future on some
client machines.

I just edited an exports file (according to your recommendations -
because my server occationally gave stale file handles on some client
machines), and found that the netmask 255.255.254.0 doesn't work either
- you need to specify two nets with 255.255.255.0 instead.   My point
being, that even though I administer a network that I would describe as
"small", even I run into major problems with the lack of proper parsing
and error reporting of /etc/exports.

Generally, it seems exportfs would accept virtually any input, export it
one way or another to the kernel, with unpredictable results and
spurious errors at random times in the future.

What I would like was for exportfs to either say "No! Fix your file
stupid" or "Good! This setup will work reliably for all eternity then".

Is anyone considering fixing this?   And; is the problem mainly in
exportfs, in the kernel, or both?  (relevant for me to know if I want to
go fix it myself)    Thanks!

-- 

 / jakob