Linux NFS development
 help / color / mirror / Atom feed
From: "bfields@fieldses.org" <bfields@fieldses.org>
To: Trond Myklebust <trondmy@hammerspace.com>
Cc: "chuck.lever@oracle.com" <chuck.lever@oracle.com>,
	"jlayton@redhat.com" <jlayton@redhat.com>,
	"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
	"bfields@redhat.com" <bfields@redhat.com>,
	"jlayton@poochiereds.net" <jlayton@poochiereds.net>
Subject: Re: [PATCH 0/3] Handling NFSv3 I/O errors in knfsd
Date: Tue, 27 Aug 2019 10:59:12 -0400	[thread overview]
Message-ID: <20190827145912.GC9804@fieldses.org> (raw)
In-Reply-To: <20190827145819.GB9804@fieldses.org>

On Tue, Aug 27, 2019 at 10:58:19AM -0400, bfields@fieldses.org wrote:
> On Tue, Aug 27, 2019 at 02:53:01PM +0000, Trond Myklebust wrote:
> > The one problem is that the looping forever client can cause other
> > clients to loop forever on their otherwise successful writes on other
> > files.
> 
> Yeah, that's the case I was wondering about.
> 
> > That's bad, but again, that's due to client behaviour that is
> > toxic even today.
> 
> So my worry was that if write errors are rare and the consequences of
> the single client looping forever are relatively mild, then there might
> be deployed clients that get away with that behavior.
> 
> But maybe the behavior's a lot more "toxic" than I imagined, hence
> unlikely to be very common.

(And, to be clear, I like the idea, just making sure I'm not overlooking
any problems....)

--b.

  reply	other threads:[~2019-08-27 14:59 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-26 16:50 [PATCH 0/3] Handling NFSv3 I/O errors in knfsd Trond Myklebust
2019-08-26 16:50 ` [PATCH 1/3] nfsd: nfsd_file cache entries should be per net namespace Trond Myklebust
2019-08-26 16:50   ` [PATCH 2/3] nfsd: Support the server resetting the boot verifier Trond Myklebust
2019-08-26 16:50     ` [PATCH 3/3] nfsd: Don't garbage collect files that might contain write errors Trond Myklebust
2019-08-27  7:58     ` [PATCH 2/3] nfsd: Support the server resetting the boot verifier kbuild test robot
2019-08-26 20:51 ` [PATCH 0/3] Handling NFSv3 I/O errors in knfsd J. Bruce Fields
2019-08-26 21:02   ` Trond Myklebust
2019-08-27  0:48     ` bfields
2019-08-27  0:56       ` Trond Myklebust
2019-08-27  1:13         ` bfields
2019-08-27  1:28           ` Trond Myklebust
2019-08-27 13:59     ` Chuck Lever
2019-08-27 14:53       ` Trond Myklebust
2019-08-27 14:58         ` bfields
2019-08-27 14:59           ` bfields [this message]
2019-08-27 15:15             ` Trond Myklebust
2019-08-27 15:20               ` Chuck Lever
2019-08-28 13:48               ` bfields
2019-08-28 13:51                 ` Jeff Layton
2019-08-28 13:57                   ` Chuck Lever
2019-08-28 14:00                     ` J. Bruce Fields
2019-08-28 14:03                       ` Chuck Lever
2019-08-28 14:16                         ` Jeff Layton
2019-08-28 14:21                           ` Chuck Lever
2019-08-28 14:40                           ` J. Bruce Fields
2019-08-28 14:48                             ` Bruce Fields
2019-08-28 14:50                               ` Chuck Lever
2019-08-28 17:07                                 ` Bruce Fields
2019-08-28 15:09                             ` Jeff Layton
2019-08-28 15:12                             ` Rick Macklem
2019-08-28 15:37                               ` Trond Myklebust
2019-08-28 15:46                               ` Bruce Fields
2019-08-27 14:54       ` Bruce Fields
2019-08-27 14:59         ` Trond Myklebust
2019-08-27 15:00           ` bfields
2019-08-27 15:17       ` Jeff Layton

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=20190827145912.GC9804@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=bfields@redhat.com \
    --cc=chuck.lever@oracle.com \
    --cc=jlayton@poochiereds.net \
    --cc=jlayton@redhat.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trondmy@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