From: Chuck Lever III <chuck.lever@oracle.com>
To: Bruce Fields <bfields@fieldses.org>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: sporadic hangs on generic/186
Date: Wed, 6 Apr 2022 19:58:12 +0000 [thread overview]
Message-ID: <9831571B-E597-48FE-9D48-06F971DCD860@oracle.com> (raw)
In-Reply-To: <20220406195424.GA1242@fieldses.org>
> On Apr 6, 2022, at 3:54 PM, J. Bruce Fields <bfields@fieldses.org> wrote:
>
> In the last couple days I've started getting hangs on xfstests
> generic/186 on upstream. I also notice the test completes after 10+
> hours (usually it takes about 5 minutes). Sometimes this is accompanied
> by "nfs: RPC call returned error 12" on the client.
>
> Test description is:
>
> # Ensuring that copy on write in buffered mode works when free space
> # is heavily fragmented.
> # - Create two files
> # - Reflink the odd blocks of the first file into a third file.
> # - Reflink the even blocks of the second file into the third file.
> # - Try to fragment the free space by allocating a huge file and
> # punching out every other block.
> # - CoW across the halfway mark.
> # - Check that the files are now different where we say they're
> # different.
>
> so maybe it's really some xfs change, I don't know. Or maybe it's a
> problem with my particular test filesystem (which doesn't get recreated
> for each test run).
>
> The problem doesn't reproduce easily enough to bisect.
>
> I may just turn off that test for now.
Thanks for the report.
I don't have a SCRATCH_DEV so generic/186 isn't run on my systems.
--
Chuck Lever
next prev parent reply other threads:[~2022-04-06 21:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-06 19:54 sporadic hangs on generic/186 J. Bruce Fields
2022-04-06 19:58 ` Chuck Lever III [this message]
2022-04-07 0:14 ` Dave Chinner
2022-04-07 0:27 ` NeilBrown
2022-04-07 1:19 ` NeilBrown
2022-04-07 1:49 ` J. Bruce Fields
2022-04-07 4:23 ` NeilBrown
2022-04-07 1:54 ` Trond Myklebust
2022-04-07 4:11 ` NeilBrown
2022-04-07 13:01 ` Trond Myklebust
2022-04-08 2:46 ` NeilBrown
2022-04-08 5:03 ` Dave Chinner
2022-04-08 5:32 ` NeilBrown
2022-04-10 23:34 ` Dave Chinner
2022-04-12 3:13 ` NeilBrown
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=9831571B-E597-48FE-9D48-06F971DCD860@oracle.com \
--to=chuck.lever@oracle.com \
--cc=bfields@fieldses.org \
--cc=linux-fsdevel@vger.kernel.org \
--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 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.