mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: fabian.frederick@prov-liege.be
Cc: linux-kernel@vger.kernel.org
Subject: Re: NFS export ... again
Date: Fri, 16 Apr 2004 09:18:59 -0700	[thread overview]
Message-ID: <1082132338.2581.42.camel@lade.trondhjem.org> (raw)
In-Reply-To: <S262454AbUDPHML/20040416071211Z+2733@vger.kernel.org>

On Fri, 2004-04-16 at 00:05, fabian.frederick@prov-liege.be wrote:
> Trond, Chris,
> 
>      AFAICS, nfsd/export code already does some nfs cache poll through RPC to generate /proc/nfs/exports .... But content appears broken to me as it relates progressive mounting points but never umounts.We only have to fix this in my opinion ... or maybe I'm lured by multi-versioning there ... 

/proc/nfs/exports is a server-side thing, and just reflects the kernel's
cache of currently exported filesystems. It is controlled by mountd by
means of a syscall...

I don't see what you are getting at here. There is no such thing as a
reliable way of ensuring that the server has a fully uptodate list of
all clients that are currently mounting a filesystem: Clients can and do
crash. When they do, they will fail to send a "umount" call to the
server. When that happens, the reference count in /var/lib/nfs/rmtab
will be wrong, and so all these lists from /proc/fs/nfs/exports to
"showmount" will show clients that are no longer there.

Just don't rely on that information: it will never be completely
correct.

Cheers,
  Trond

      reply	other threads:[~2004-04-16 16:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-16  7:05 fabian.frederick
2004-04-16 16:18 ` Trond Myklebust [this message]

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=1082132338.2581.42.camel@lade.trondhjem.org \
    --to=trond.myklebust@fys.uio.no \
    --cc=fabian.frederick@prov-liege.be \
    --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®