From: Su Yanjun <suyj.fnst@cn.fujitsu.com>
To: <linux-nfs@vger.kernel.org>
Cc: <cuiyue-fnst@cn.fujitsu.com>
Subject: Re: NFS issues about aio and dio test
Date: Mon, 26 Aug 2019 08:37:41 +0800 [thread overview]
Message-ID: <65ea4ea2-548f-1546-059a-af901bba2e87@cn.fujitsu.com> (raw)
In-Reply-To: <975395cc-62f2-843f-cc71-82339b2869cd@cn.fujitsu.com>
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.
>
>
>
>
>
>
>
next prev parent reply other threads:[~2019-08-26 0:39 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 [this message]
2019-08-28 17:28 ` J. Bruce Fields
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=65ea4ea2-548f-1546-059a-af901bba2e87@cn.fujitsu.com \
--to=suyj.fnst@cn.fujitsu.com \
--cc=cuiyue-fnst@cn.fujitsu.com \
--cc=linux-nfs@vger.kernel.org \
/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