From: Weston Andros Adamson <dros@primarydata.com>
To: Will Deacon <will.deacon@arm.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 11:02:26 -0400 [thread overview]
Message-ID: <FA11FBE3-42E7-46B9-B9DA-FAE368DCE96B@primarydata.com> (raw)
In-Reply-To: <5294BEB2-F20F-4E3E-BFB2-E41806A4F85A@primarydata.com>
On Sep 23, 2014, at 10:59 AM, Weston Andros Adamson <dros@primarydata.com> wrote:
> On Sep 23, 2014, at 10:53 AM, Will Deacon <will.deacon@arm.com> wrote:
>
>> 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.
>
> Thanks! You are using NFSv2, so there are no commits - that rules out my hunch.
Wait a second - the whole point of this extra reference (that the WARN_ON_ONCE is
related to) is to handle the pass off to commit lists.
Maybe I’m just doing the wrong thing here with NFSv2!
More soon.
-dros
next prev parent reply other threads:[~2014-09-23 15:02 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
2014-09-23 14:59 ` Weston Andros Adamson
2014-09-23 15:02 ` Weston Andros Adamson [this message]
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=FA11FBE3-42E7-46B9-B9DA-FAE368DCE96B@primarydata.com \
--to=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 \
--cc=will.deacon@arm.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