From: Christoph Hellwig <hch@lst.de>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] gfs2 hang in xfstests generic/361 (v3)
Date: Tue, 27 Jul 2021 09:05:46 +0200 [thread overview]
Message-ID: <20210727070546.GA12839@lst.de> (raw)
In-Reply-To: <612d262a-e997-e887-ade9-1edc5efab758@redhat.com>
On Mon, Jul 26, 2021 at 01:50:11PM -0500, Bob Peterson wrote:
> FYI: I just pushed a replacement patch to linux-gfs2/for-next.next4.
> The patch I mentioned last time had problems, so this is a simplified
> middle-ground between that patch and the one I suggested earlier.
> Patch is a89a427e0afe.
With just that patch cherry picked the test still hangs.
The entire linux-gfs2/for-next.next4 completes a quick group xfstests
run, but with a lot of failures:
Failures: generic/079 generic/082 generic/092 generic/094 generic/103 generic/219 generic/230 generic/235 generic/244 generic/294 generic/306 generic/347 generic/379 generic/380 generic/382 generic/383 generic/384 generic/385 generic/386 generic/400 generic/441 generic/452 generic/488 generic/545 generic/566 generic/587 generic/594 generic/600 generic/601 generic/603
Failed 30 of 514 tests
next prev parent reply other threads:[~2021-07-27 7:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-26 14:00 [Cluster-devel] gfs2 hang in xfstests generic/361 Christoph Hellwig
2021-07-26 14:49 ` Bob Peterson
2021-07-26 17:11 ` Bob Peterson
2021-07-26 17:35 ` Bob Peterson
2021-07-26 18:50 ` [Cluster-devel] gfs2 hang in xfstests generic/361 (v3) Bob Peterson
2021-07-27 7:05 ` Christoph Hellwig [this message]
2021-07-27 14:05 ` Bob Peterson
2021-07-27 14:27 ` Andreas Gruenbacher
2021-07-27 16:41 ` Bob Peterson
2021-07-28 5:39 ` Christoph Hellwig
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=20210727070546.GA12839@lst.de \
--to=hch@lst.de \
/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).