From: Guoqing Jiang <guoqing.jiang@linux.dev>
To: Logan Gunthorpe <logang@deltatee.com>,
linux-raid@vger.kernel.org, Jes Sorensen <jsorensen@fb.com>
Cc: Song Liu <song@kernel.org>, Christoph Hellwig <hch@infradead.org>,
Donald Buczek <buczek@molgen.mpg.de>, Xiao Ni <xni@redhat.com>,
Himanshu Madhani <himanshu.madhani@oracle.com>,
Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>,
Coly Li <colyli@suse.de>, Bruce Dubbs <bruce.dubbs@gmail.com>,
Stephen Bates <sbates@raithlin.com>,
Martin Oliveira <Martin.Oliveira@eideticom.com>,
David Sloan <David.Sloan@eideticom.com>
Subject: Re: [PATCH mdadm v1 14/14] tests: Add broken files for all broken tests
Date: Fri, 10 Jun 2022 17:49:09 +0800 [thread overview]
Message-ID: <3b32656b-6d87-39df-625e-93bed6871022@linux.dev> (raw)
In-Reply-To: <20220609211130.5108-15-logang@deltatee.com>
On 6/10/22 5:11 AM, Logan Gunthorpe wrote:
> Each broken file contains the rough frequency of brokeness as well
> as a brief explanation of what happens when it breaks. Estimates
> of failure rates are not statistically significant and can vary
> run to run.
>
> This is really just a view from my window. Tests were done on a
> small VM with the default loop devices, not real hardware. We've
> seen different kernel configurations can cause bugs to appear as well
> (ie. different block schedulers). It may also be that different race
> conditions will be seen on machines with different performance
> characteristics.
>
> These annotations were done with the kernel currently in md/md-next:
>
> facef3b96c5b ("md: Notify sysfs sync_completed in md_reap_sync_thread()")
>
> Signed-off-by: Logan Gunthorpe <logang@deltatee.com>
> ---
> tests/01r5integ.broken | 7 ++++
> tests/01raid6integ.broken | 7 ++++
> tests/04r5swap.broken | 7 ++++
> tests/07autoassemble.broken | 8 ++++
> tests/07autodetect.broken | 5 +++
> tests/07changelevelintr.broken | 9 +++++
> tests/07changelevels.broken | 9 +++++
> tests/07reshape5intr.broken | 45 ++++++++++++++++++++++
> tests/07revert-grow.broken | 31 +++++++++++++++
> tests/07revert-shrink.broken | 9 +++++
> tests/07testreshape5.broken | 12 ++++++
> tests/09imsm-assemble.broken | 6 +++
> tests/09imsm-create-fail-rebuild.broken | 5 +++
> tests/09imsm-overlap.broken | 7 ++++
> tests/10ddf-assemble-missing.broken | 6 +++
> tests/10ddf-fail-create-race.broken | 7 ++++
> tests/10ddf-fail-two-spares.broken | 5 +++
> tests/10ddf-incremental-wrong-order.broken | 9 +++++
> tests/14imsm-r1_2d-grow-r1_3d.broken | 5 +++
> tests/14imsm-r1_2d-takeover-r0_2d.broken | 6 +++
> tests/18imsm-r10_4d-takeover-r0_2d.broken | 5 +++
> tests/18imsm-r1_2d-takeover-r0_1d.broken | 6 +++
> tests/19raid6auto-repair.broken | 5 +++
> tests/19raid6repair.broken | 5 +++
> 24 files changed, 226 insertions(+)
> create mode 100644 tests/01r5integ.broken
> create mode 100644 tests/01raid6integ.broken
> create mode 100644 tests/04r5swap.broken
> create mode 100644 tests/07autoassemble.broken
> create mode 100644 tests/07autodetect.broken
> create mode 100644 tests/07changelevelintr.broken
> create mode 100644 tests/07changelevels.broken
> create mode 100644 tests/07reshape5intr.broken
> create mode 100644 tests/07revert-grow.broken
> create mode 100644 tests/07revert-shrink.broken
> create mode 100644 tests/07testreshape5.broken
> create mode 100644 tests/09imsm-assemble.broken
> create mode 100644 tests/09imsm-create-fail-rebuild.broken
> create mode 100644 tests/09imsm-overlap.broken
> create mode 100644 tests/10ddf-assemble-missing.broken
> create mode 100644 tests/10ddf-fail-create-race.broken
> create mode 100644 tests/10ddf-fail-two-spares.broken
> create mode 100644 tests/10ddf-incremental-wrong-order.broken
> create mode 100644 tests/14imsm-r1_2d-grow-r1_3d.broken
> create mode 100644 tests/14imsm-r1_2d-takeover-r0_2d.broken
> create mode 100644 tests/18imsm-r10_4d-takeover-r0_2d.broken
> create mode 100644 tests/18imsm-r1_2d-takeover-r0_1d.broken
> create mode 100644 tests/19raid6auto-repair.broken
> create mode 100644 tests/19raid6repair.broken
Just to share some results from my side, with 5.19-rc1 (revert my
problematic patch of course), below tests failed.
/root/mdadm/tests/00raid0...
/root/mdadm/tests/00readonly...
/root/mdadm/tests/02lineargrow...
/root/mdadm/tests/03r0assem...
/root/mdadm/tests/03r5assem-failed...
/root/mdadm/tests/04r0update...
/root/mdadm/tests/04r5swap...
/root/mdadm/tests/04update-metadata...
/root/mdadm/tests/04update-uuid...
/root/mdadm/tests/05r1-bitmapfile...
/root/mdadm/tests/05r1-grow-external...
/root/mdadm/tests/05r1-n3-bitmapfile...
/root/mdadm/tests/05r1-re-add...
/root/mdadm/tests/05r1-re-add-nosuper...
/root/mdadm/tests/05r5-bitmapfile...
/root/mdadm/tests/05r6-bitmapfile...
/root/mdadm/tests/06wrmostly...
/root/mdadm/tests/07autoassemble...
/root/mdadm/tests/07changelevelintr...
/root/mdadm/tests/07changelevels...
/root/mdadm/tests/07layouts...
/root/mdadm/tests/07revert-grow...
/root/mdadm/tests/07revert-shrink...
/root/mdadm/tests/07testreshape5...
/root/mdadm/tests/09imsm-create-fail-rebuild...
/root/mdadm/tests/09imsm-overlap...
/root/mdadm/tests/10ddf-assemble-missing...
/root/mdadm/tests/10ddf-create...
/root/mdadm/tests/10ddf-fail-readd...
/root/mdadm/tests/10ddf-fail-spare...
/root/mdadm/tests/10ddf-fail-stop-readd...
/root/mdadm/tests/10ddf-fail-twice...
/root/mdadm/tests/10ddf-fail-two-spares...
/root/mdadm/tests/10ddf-incremental-wrong-order...
/root/mdadm/tests/19raid6auto-repair...
/root/mdadm/tests/19raid6repair...
05r1-bitmapfile failed which is probably because external bitmaps are only
work on ext2 and ext3, I guess other 05*-bitmapfile failed due to the same
reason.
01r5integ /01raid6integ can't finish due to some reason.
BTW, thank you for the effort to make md/mdadm better!
Thanks,
Guoqing
next prev parent reply other threads:[~2022-06-10 9:49 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 21:11 [PATCH mdadm v1 00/14] Bug fixes and testing improvments Logan Gunthorpe
2022-06-09 21:11 ` [PATCH mdadm v1 01/14] Makefile: Don't build static build with everything Logan Gunthorpe
2022-06-20 14:08 ` Mariusz Tkaczyk
2022-06-22 16:39 ` Logan Gunthorpe
2022-06-09 21:11 ` [PATCH mdadm v1 02/14] DDF: Cleanup validate_geometry_ddf_container() Logan Gunthorpe
2022-06-20 14:14 ` Mariusz Tkaczyk
2022-06-09 21:11 ` [PATCH mdadm v1 03/14] DDF: Fix NULL pointer dereference in validate_geometry_ddf() Logan Gunthorpe
2022-06-20 14:13 ` Mariusz Tkaczyk
2022-06-09 21:11 ` [PATCH mdadm v1 04/14] mdadm/Grow: Fix use after close bug by closing after fork Logan Gunthorpe
2022-06-20 14:27 ` Mariusz Tkaczyk
2022-06-09 21:11 ` [PATCH mdadm v1 05/14] monitor: Avoid segfault when calling NULL get_bad_blocks Logan Gunthorpe
2022-06-20 14:29 ` Mariusz Tkaczyk
2022-06-09 21:11 ` [PATCH mdadm v1 06/14] mdadm: Fix mdadm -r remove option regresision Logan Gunthorpe
2022-06-20 14:35 ` Mariusz Tkaczyk
2022-06-20 15:26 ` Paul Menzel
2022-06-09 21:11 ` [PATCH mdadm v1 07/14] mdadm: Fix optional --write-behind parameter Logan Gunthorpe
2022-06-20 14:37 ` Mariusz Tkaczyk
2022-06-09 21:11 ` [PATCH mdadm v1 08/14] tests/00raid0: add a test that validates raid0 with layout fails for 0.9 Logan Gunthorpe
2022-06-09 21:11 ` [PATCH mdadm v1 09/14] tests: fix raid0 tests for 0.90 metadata Logan Gunthorpe
2022-06-09 21:11 ` [PATCH mdadm v1 10/14] tests/04update-metadata: avoid passing chunk size to raid1 Logan Gunthorpe
2022-06-09 21:11 ` [PATCH mdadm v1 11/14] tests/02lineargrow: clear the superblock at every iteration Logan Gunthorpe
2022-06-09 21:11 ` [PATCH mdadm v1 12/14] mdadm/test: Add a mode to repeat specified tests Logan Gunthorpe
2022-06-09 21:11 ` [PATCH mdadm v1 13/14] mdadm/test: Mark and ignore broken test failures Logan Gunthorpe
2022-06-09 21:11 ` [PATCH mdadm v1 14/14] tests: Add broken files for all broken tests Logan Gunthorpe
2022-06-10 9:49 ` Guoqing Jiang [this message]
2022-06-10 15:17 ` Logan Gunthorpe
2022-06-10 16:16 ` Donald Buczek
2022-06-10 10:14 ` [PATCH mdadm v1 00/14] Bug fixes and testing improvments Paul Menzel
2022-06-10 15:27 ` Logan Gunthorpe
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=3b32656b-6d87-39df-625e-93bed6871022@linux.dev \
--to=guoqing.jiang@linux.dev \
--cc=David.Sloan@eideticom.com \
--cc=Martin.Oliveira@eideticom.com \
--cc=bruce.dubbs@gmail.com \
--cc=buczek@molgen.mpg.de \
--cc=colyli@suse.de \
--cc=hch@infradead.org \
--cc=himanshu.madhani@oracle.com \
--cc=jsorensen@fb.com \
--cc=linux-raid@vger.kernel.org \
--cc=logang@deltatee.com \
--cc=mariusz.tkaczyk@linux.intel.com \
--cc=sbates@raithlin.com \
--cc=song@kernel.org \
--cc=xni@redhat.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.