From: Chuck Lever III <chuck.lever@oracle.com>
To: Trond Myklebust <trondmy@hammerspace.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: recent intermittent fsx-related failures
Date: Mon, 23 Aug 2021 15:21:26 +0000 [thread overview]
Message-ID: <9D849792-600A-464F-8340-8F5C32ED2439@oracle.com> (raw)
In-Reply-To: <36417C84-FE59-484F-859D-3445F53CC0D7@oracle.com>
> On Jul 23, 2021, at 5:31 PM, Chuck Lever III <chuck.lever@oracle.com> wrote:
>
>> On Jul 23, 2021, at 4:24 PM, Trond Myklebust <trondmy@hammerspace.com> wrote:
>>
>> On Fri, 2021-07-23 at 20:12 +0000, Chuck Lever III wrote:
>>> Hi-
>>>
>>> I noticed recently that generic/075, generic/112, and generic/127
>>> were
>>> failing intermittently on NFSv3 mounts. All three of these tests are
>>> based on fsx.
>>>
>>> "git bisect" landed on this commit:
>>>
>>> 7b24dacf0840 ("NFS: Another inode revalidation improvement")
>>>
>>> After reverting 7b24dacf0840 on v5.14-rc1, I can no longer reproduce
>>> the test failures.
>>
>> So you are seeing file metadata updates that end up not changing the
>> ctime?
>
> I haven't drilled that deeply into it yet.
>
> Fwiw, the test runs against a tmpfs export.
Btw, I'm still seeing this failure on occasion. It had stopped
reproducing for a while, so I set it aside, but it has cropped
up again.
--
Chuck Lever
next prev parent reply other threads:[~2021-08-23 15:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-23 20:12 recent intermittent fsx-related failures Chuck Lever III
2021-07-23 20:24 ` Trond Myklebust
2021-07-23 21:31 ` Chuck Lever III
2021-08-23 15:21 ` Chuck Lever III [this message]
2021-09-19 23:03 ` Chuck Lever III
2021-09-19 23:19 ` Trond Myklebust
2021-09-20 20:05 ` Chuck Lever III
2021-09-21 19:00 ` Trond Myklebust
2021-09-24 15:30 ` Chuck Lever III
2021-09-24 22:09 ` Trond Myklebust
2021-09-25 17:26 ` Chuck Lever III
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=9D849792-600A-464F-8340-8F5C32ED2439@oracle.com \
--to=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trondmy@hammerspace.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.