Received-SPF: pass (google.com: best guess record for domain of linux-nfs-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Subject: Re: NFS issues about aio and dio test
From:   Su Yanjun <suyj.fnst@cn.fujitsu.com>
To:     <linux-nfs@vger.kernel.org>
CC:     <cuiyue-fnst@cn.fujitsu.com>
References: <975395cc-62f2-843f-cc71-82339b2869cd@cn.fujitsu.com>
Message-ID: <65ea4ea2-548f-1546-059a-af901bba2e87@cn.fujitsu.com>
Date:   Mon, 26 Aug 2019 08:37:41 +0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101
 Thunderbird/60.7.0
MIME-Version: 1.0
In-Reply-To: <975395cc-62f2-843f-cc71-82339b2869cd@cn.fujitsu.com>
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 8bit
Sender: linux-nfs-owner@vger.kernel.org
Precedence: bulk

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.
>
>
>
>
>
>
>