From: bfields@fieldses.org (J. Bruce Fields)
To: Chuck Lever <chuck.lever@oracle.com>
Cc: linux-nfs@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: sporadic hangs on generic/186
Date: Wed, 6 Apr 2022 15:54:24 -0400 [thread overview]
Message-ID: <20220406195424.GA1242@fieldses.org> (raw)
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.
--b.
next reply other threads:[~2022-04-06 21:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-06 19:54 J. Bruce Fields [this message]
2022-04-06 19:58 ` sporadic hangs on generic/186 Chuck Lever III
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=20220406195424.GA1242@fieldses.org \
--to=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).