From: "J. Bruce Fields" <bfields@fieldses.org>
To: xuhuan <xuhuan.fnst@cn.fujitsu.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: xfstest generci/465 failed under all versions of NFS
Date: Mon, 6 Aug 2018 15:27:43 -0400 [thread overview]
Message-ID: <20180806192743.GA9158@fieldses.org> (raw)
In-Reply-To: <ff080c90-e2e9-686f-9bcd-b6a4af8ac1a0@cn.fujitsu.com>
On Mon, Aug 06, 2018 at 05:29:33PM +0800, xuhuan wrote:
> I test NFS in xfstest generic/465 useing kernel v4.18-rc6.
> I tested it with all version of nfs ,and all got failed.
>
> This patch fixes a bug in the xfs filesystem.Prior to this patch,
> generic/465 is failed under the xfs file system.
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ee70daaba82d70766d0723b743d9fdeb3b06102a
>
> Now, under the xfs file system, generic/465 is passed, but when I use
> it to test NFS, while the server using the xfs file system, the test will still fail.
> I think it is a nfs's bug.I donnot know where is it.
generic/465 says "Test i_size is updated properly under dio read/write".
So I guess it's doing some direct IO that appends to a file and then a
stat to confirm that we get the new i_size?
If this isn't working when run on an NFS filesystem, then I think either
the client isn't asking the server for the new i_size, or maybe it's
asking but getting a bad response. The bad response might have the old
i_size. Or I wonder if the client would be confused if the server
failed to update the change attribute (i_version) for some reason?
Does this test fail when we export other filesystems? Is the failure
new, or has it always failed?
--b.
next prev parent reply other threads:[~2018-08-06 21:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-06 9:29 xfstest generci/465 failed under all versions of NFS xuhuan
2018-08-06 19:27 ` J. Bruce Fields [this message]
2018-08-15 4:57 ` xuhuan
2018-08-15 11:43 ` Trond Myklebust
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=20180806192743.GA9158@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=xuhuan.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