From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: David Woodhouse <dwmw2@infradead.org>
Cc: "Sven Köhler" <skoehler@upb.de>,
linux-kernel@vger.kernel.org, nfs@lists.sourceforge.net
Subject: Re: why do i get "Stale NFS file handle" for hours?
Date: Mon, 06 Sep 2004 11:59:17 -0400 [thread overview]
Message-ID: <1094486357.8342.12.camel@lade.trondhjem.org> (raw)
In-Reply-To: <1094464633.3986.36.camel@imladris.demon.co.uk>
På må , 06/09/2004 klokka 05:57, skreiv David Woodhouse:
> The fact that we require a persistent table of exports at all, and can't
> call back to mountd to authenticate 'new' clients instead of just
> telling them to sod off if the kernel doesn't already know about them,
> is considered by some to be a bug in knfsd.
That should have been fixed in 2.6.x. If you do mount /proc/fs/nfsd, and
use a recent enough version of mountd, then knfsd can and will work
without any extra help from exportfs.
The one problem I have found with this implementation is that it relies
very heavily on reverse-DNS lookups, so it may give unexpected results
if you have more than one name for your client. I can't see why that
shouldn't be fixable, though...
Cheers,
Trond
next prev parent reply other threads:[~2004-09-06 16:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-05 1:06 Sven Köhler
2004-09-05 1:39 ` Trond Myklebust
2004-09-05 1:51 ` Sven Köhler
2004-09-05 2:02 ` Trond Myklebust
2004-09-05 2:23 ` Sven Köhler
2004-09-05 3:01 ` Trond Myklebust
2004-09-05 8:17 ` Tim Connors
2004-09-05 8:59 ` Florian Weimer
2004-09-05 9:02 ` Tim Connors
2004-09-05 16:20 ` Mike Jagdis
2004-09-06 1:32 ` Tim Connors
2004-09-05 13:18 ` Sven Köhler
2004-09-05 20:10 ` Trond Myklebust
2004-09-06 7:47 ` Kalin KOZHUHAROV
2004-09-06 9:57 ` David Woodhouse
2004-09-06 15:59 ` Trond Myklebust [this message]
2004-09-07 0:55 ` [NFS] " Greg Banks
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=1094486357.8342.12.camel@lade.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
--cc=skoehler@upb.de \
/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®