Linux NFS development
 help / color / mirror / Atom feed
From: Steve Dickson <steved@redhat.com>
To: NeilBrown <neilb@suse.de>
Cc: linux-nfs@vger.kernel.org,
	Trond Myklebust <trond.myklebust@hammerspace.com>
Subject: Re: [PATCH 0/6 nfs-utils v2] fixes for error handling in nfsd_fh
Date: Wed, 25 Oct 2023 13:37:30 -0400	[thread overview]
Message-ID: <055f76be-226f-4b15-8e7b-13f78dba10c5@redhat.com> (raw)
In-Reply-To: <20231023021052.5258-1-neilb@suse.de>



On 10/22/23 9:58 PM, NeilBrown wrote:
> Hi,
>   this is a revised version of my previous series with the same name.
>   This first two patches are unchanged.
>   The third patch, which was an RFC, has been replaced with the last
>   patch which actually addresses the issue rather than skirting
>   around it.
> 
>   Patch 3 here is a revert of a change I noticed while exploring the
>   code.  cache_open() must be called BEFORE forking workers, as explained
>   in that patch.
>   Patches 4 and 5 factor our common code which makes the final patch
>   simpler.
> 
>   The core issue is that sometimes mountd (or exportd) cannot give a
>   definitey "yes" or "no" to a request to map an fsid to a path name.
>   In these cases the only safe option is to delay and try again.
> 
>   This only becomes relevant if a filesystem is mounted by a client, then
>   the server restarts (or the export cache is flushed) and the client
>   tries to use a filehandle that it already has, but that server cannot
>   find it and cannot be sure it doesn't exist.  This can happen when an
>   export is marked "mountpoint" or when a re-exported NFS filesystem
>   cannot contact the server and reports an ETIMEDOUT error.  In these
>   cases we want the client to continue waiting (which it does) and also
>   want mountd/exportd to periodically check if the target filesystem has
>   come back (which it currently does not).
>   With the current code, once this situation happens and the client is
>   waiting, the client will continue to wait indefintely even if the
>   target filesytem becomes available.  The client can only continue if
>   the NFS server is restarted or the export cache is flushed.  After the
>   ptsch, then within 2 minutes of the target filesystem becoming
>   available again, mountd will tell the kernel and when the client asks
>   again it will get be allowed to proceed.
> 
> NeilBrown
> 
> 
>   [PATCH 1/6] export: fix handling of error from match_fsid()
>   [PATCH 2/6] export: add EACCES to the list of known
>   [PATCH 3/6] export: move cache_open() before workers are forked.
>   [PATCH 4/6] Move fork_workers() and wait_for_workers() in cache.c
>   [PATCH 5/6] Share process_loop code between mountd and exportd.
>   [PATCH 6/6] cache: periodically retry requests that couldn't be
> 
Committed... (tag: nfs-utils-2-6-4-rc5)

steved.


      parent reply	other threads:[~2023-10-25 17:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-23  1:58 [PATCH 0/6 nfs-utils v2] fixes for error handling in nfsd_fh NeilBrown
2023-10-23  1:58 ` [PATCH 1/6] export: fix handling of error from match_fsid() NeilBrown
2023-10-23  1:58 ` [PATCH 2/6] export: add EACCES to the list of known path_lookup_error() errors NeilBrown
2023-10-23  1:58 ` [PATCH 3/6] export: move cache_open() before workers are forked NeilBrown
2023-10-23  1:58 ` [PATCH 4/6] Move fork_workers() and wait_for_workers() in cache.c NeilBrown
2023-10-23  1:58 ` [PATCH 5/6] Share process_loop code between mountd and exportd NeilBrown
2023-10-23  1:58 ` [PATCH 6/6] cache: periodically retry requests that couldn't be answered NeilBrown
2023-10-25 17:37 ` Steve Dickson [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=055f76be-226f-4b15-8e7b-13f78dba10c5@redhat.com \
    --to=steved@redhat.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=trond.myklebust@hammerspace.com \
    /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