From: Christoph Hellwig <hch@infradead.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Trond Myklebust <trond.myklebust@primarydata.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH, RFC] backchannel overflows
Date: Wed, 29 Apr 2015 08:14:04 -0700 [thread overview]
Message-ID: <20150429151404.GA12936@infradead.org> (raw)
In-Reply-To: <1C0C92C2-FBCF-49D8-BB31-3C23A520B075@oracle.com>
On Wed, Apr 29, 2015 at 10:55:10AM -0400, Chuck Lever wrote:
>
> On Apr 28, 2015, at 4:21 PM, Christoph Hellwig <hch@infradead.org> wrote:
>
> > Currently the client will just crap out if a CB_NULL comes in at the
> > same time as a slot controlled CB_COMPOUND that includes a CB_SEQUENCE.
>
> Under what circumstances does the server send a CB_NULL while a CB_COMPOUND
> is in flight?
When a client is under heavy loads from fsx or aio-stress, and we lose
the connection (nfsd4_conn_lost is called) while doing heavy recalls.
xfstests against a server offering pnfs layouts for which the client
can't reach the storage devices is an easy reproducer.
next prev parent reply other threads:[~2015-04-29 15:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-28 20:21 [PATCH, RFC] backchannel overflows Christoph Hellwig
2015-04-29 12:08 ` Kinglong Mee
2015-04-29 13:46 ` Christoph Hellwig
2015-04-29 14:55 ` Chuck Lever
2015-04-29 14:58 ` Trond Myklebust
2015-04-29 15:14 ` Christoph Hellwig [this message]
2015-04-29 15:24 ` Trond Myklebust
2015-04-29 17:34 ` J. Bruce Fields
2015-04-30 6:25 ` Christoph Hellwig
2015-04-30 14:34 ` Chuck Lever
2015-04-30 14:37 ` Christoph Hellwig
[not found] ` <CAHQdGtRgEVXidNNYtYf4c3uS0vc6fbm-SZ5AxrY=awXYynmACw@mail.gmail.com>
2015-04-30 15:02 ` Trond Myklebust
2015-04-30 15:11 ` Chuck Lever
2015-04-30 17:41 ` Chuck Lever
2015-05-01 17:23 ` Christoph Hellwig
2015-05-01 17:28 ` Trond Myklebust
2015-05-01 17:37 ` Christoph Hellwig
2015-05-01 17:47 ` Trond Myklebust
2015-05-01 17:31 ` Chuck Lever
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=20150429151404.GA12936@infradead.org \
--to=hch@infradead.org \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@primarydata.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.