Stale NFS handles depending on server-fs-type

Stale NFS handles depending on server-fs-type

[R.Oehler]

Hello, list

currently I got a problem with the userspace-nfs-packet
"nfs-server-2.2beta47".
I'm running the server in multiple-servers-mode (cmd-line
argument to make the server spawn 10 children).
When I export my selfmade filesystem, and do a client-side 
"cp -r /usr/include /net/<server>/export" then the nfs-client 
complains about "stale NFS handles" at about 90% of all files. 
These files appear on the destination-fs, but with  zero-length. 
(Created, but not written-to).

- Local copies to the selfmade filesystem work perfectly.
- When I run the server in single-serverprocess-mode (not 
  spawning children), then it works, too.
- When I use ext2 instead of my selfmade fs, it works, too.

So it appears that the selfmade filesystem does something 
that is OK for linux, but triggers some bug (?) in the 
multiple-server-section of the NFS-server.

Who is the "nfs-server-2.2beta47"-maintainer?
Or who can give me a hint of what could be wrong?

Regards,
        Ralf


 -----------------------------------------------------------------
|  Ralf Oehler
|  GDI - Gesellschaft fuer Digitale Informationstechnik mbH
|
|  E-Mail:      R.Oehler@GDImbH.com
|  Tel.:        +49 6182-9271-23 
|  Fax.:        +49 6182-25035           
|  Mail:        GDI, Bensbruchstraße 11, D-63533 Mainhausen
|  HTTP:        www.GDImbH.com
 -----------------------------------------------------------------

time is a funny concept