mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: R.Oehler@GDImbH.com
To: linux-kernel@vger.kernel.org
Subject: Stale NFS handles depending on server-fs-type
Date: Wed, 09 Jan 2002 10:19:37 +0100 (MET)	[thread overview]
Message-ID: <XFMail.20020109101937.R.Oehler@GDImbH.com> (raw)

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


                 reply	other threads:[~2002-01-09  9:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=XFMail.20020109101937.R.Oehler@GDImbH.com \
    --to=r.oehler@gdimbh.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®