public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: bfields@fieldses.org (J. Bruce Fields)
To: Su Yanjun <suyj.fnst@cn.fujitsu.com>
Cc: linux-nfs@vger.kernel.org, cuiyue-fnst@cn.fujitsu.com
Subject: Re: NFS issues about aio and dio test
Date: Wed, 28 Aug 2019 13:28:49 -0400	[thread overview]
Message-ID: <20190828172849.GA29148@fieldses.org> (raw)
In-Reply-To: <65ea4ea2-548f-1546-059a-af901bba2e87@cn.fujitsu.com>

On Mon, Aug 26, 2019 at 08:37:41AM +0800, Su Yanjun wrote:
> Any ping?
> 
> 在 2019/8/6 14:08, Su Yanjun 写道:
> >Hi,
> >
> >When I tested xfstests generic/465 with NFS, there was something
> >unexpected.
> >
> >When memory of NFS server was 10G, test passed.
> >But when memory of NFS server was 4G, test failed.
> >
> >Fail message was as below.
> >    non-aio dio test
> >    encounter an error: block 4 offset 0, content 62
> >    aio-dio test
> >    encounter an error: block 1 offset 0, content 62
> >
> >All of the NFS versions(v3 v4.0 v4.1 v4.2) have  this problem.
> >Maybe something is wrong about NFS's I/O operation.
> >
> >Thanks in advance.

Off the top of my head it doesn't look familiar.

What kernel version are you running on client and server?

Did this test previously pass on an older kernel (so, was this a recent
regression?)

Have you looked at generic/465 to see what exactly is happening here?

--b.

  reply	other threads:[~2019-08-28 17:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-06  6:08 NFS issues about aio and dio test Su Yanjun
2019-08-26  0:37 ` Su Yanjun
2019-08-28 17:28   ` J. Bruce Fields [this message]
2019-09-02  8:37     ` Su Yanjun

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=20190828172849.GA29148@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=cuiyue-fnst@cn.fujitsu.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=suyj.fnst@cn.fujitsu.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