From: Will Deacon <will.deacon@arm.com>
To: Weston Andros Adamson <dros@primarydata.com>
Cc: Peng Tao <tao.peng@primarydata.com>,
Trond Myklebust <trond.myklebust@primarydata.com>,
linux-nfs list <linux-nfs@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: WARNING at fs/nfs/write.c:743 nfs_inode_remove_request with -rc6
Date: Tue, 23 Sep 2014 15:53:56 +0100 [thread overview]
Message-ID: <20140923145356.GD28608@arm.com> (raw)
In-Reply-To: <20140923135938.GB28608@arm.com>
On Tue, Sep 23, 2014 at 02:59:38PM +0100, Will Deacon wrote:
> On Tue, Sep 23, 2014 at 02:33:06PM +0100, Weston Andros Adamson wrote:
> > Any more info on how to reproduce this would be really great. Unfortunately I don’t
> > have access to an arm64 system.
>
> I've not spotted a pattern other than using 64k pages, yet. If I manage to
> get a reproducer, I'll let you know.
>
> > If it’s possible, could we get a packet trace around when this happens? This is pure
> > speculation, but this might have something to do the resend path - a commit fails
> > and all the requests on the commit list have to be resent.
>
> Sure, once I can reproduce it reliably, then I'll try to do that.
Right, a bunch of DDing from /dev/zero over an ssh session triggers this
very quickly. I've put a binary tcpdump here:
http://www.willdeacon.ukfsn.org/bitbucket/oopsen/nfs/tcpdump.bin
You may want to filter out the ssh packets. The only `interesting' thing to
me is a retransmission about half way through, but I don't know what I'm
looking for.
The NFS server is 10.1.203.204 and the client is 10.1.203.24.
Will
next prev parent reply other threads:[~2014-09-23 14:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-23 13:03 WARNING at fs/nfs/write.c:743 nfs_inode_remove_request with -rc6 Will Deacon
2014-09-23 13:33 ` Weston Andros Adamson
2014-09-23 13:59 ` Will Deacon
2014-09-23 14:53 ` Will Deacon [this message]
2014-09-23 14:59 ` Weston Andros Adamson
2014-09-23 15:02 ` Weston Andros Adamson
2014-09-23 15:08 ` Weston Andros Adamson
2014-09-23 15:25 ` Will Deacon
2014-09-25 17:15 ` Will Deacon
2014-09-25 17:27 ` Weston Andros Adamson
2014-10-11 13:32 ` Weston Andros Adamson
2014-10-20 13:57 ` Will Deacon
2014-10-31 14:49 ` Weston Andros Adamson
2014-10-31 14:55 ` Will Deacon
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=20140923145356.GD28608@arm.com \
--to=will.deacon@arm.com \
--cc=dros@primarydata.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=tao.peng@primarydata.com \
--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.