From: Song Liu <song@kernel.org>
To: "Sung, KoWei" <winders@amazon.com>
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>,
"Bshara, Saeed" <saeedb@amazon.com>,
"Duan, HanShen" <hansduan@amazon.com>,
"Tokoyo, Hiroshi" <htokoyo@amazon.co.jp>,
"Fortin, Mike" <mfortin@amazon.com>
Subject: Re: RAID5 issue with UBUNTU 20.04.1 on my desktop
Date: Thu, 17 Sep 2020 00:03:22 -0700 [thread overview]
Message-ID: <CAPhsuW6q5bLgOUyuTH8MFTo6GSnGqRxne6sV+dsFHRy_qHtxRA@mail.gmail.com> (raw)
In-Reply-To: <6F1A48DB-CA95-433B-91F3-D0051453A8E1@amazon.com>
Hi Winder,
On Wed, Sep 16, 2020 at 2:53 AM Sung, KoWei <winders@amazon.com> wrote:
>
> Hi,
>
> I found RAID5 stability issue while doing disk expansion.
> I attached 4 disks (/dev/sda, /dev/sdb, /dev/sdc and /dev/sdd) and create partition by “create_partition.sh” scripts on my PC and run my test scripts “raid_reshape_12.sh” (as attached).
> Basically, the test will add partitions to RAID5 (/dev/md3) and write files to /dev/md3 (ext4) at the same time.
> Within 1 or 2 hours, kernel will get crashed (Oops) and reshape/resync cannot be finished forever (log as attached).
>
> The issue happens randomly, but it most likely happens at beginning of reshape process. When kernel crash happens, the reshape stops at about 3-10% complete only.
> Moreover, it is not related to any partition size, because I’ve tried different size, but issue still exists.
> I've also tried different kernel (4.1/4.2/4.9/4.19/5.4/5.8), and all kernel version can see this issue.
Thanks for the report. I just started some tests with the script. I
will update whether it repros the issue.
Song
next prev parent reply other threads:[~2020-09-17 7:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-16 9:53 RAID5 issue with UBUNTU 20.04.1 on my desktop Sung, KoWei
2020-09-17 7:03 ` Song Liu [this message]
2020-09-22 0:34 ` Sung, KoWei
2020-09-28 17:15 ` Song Liu
2020-10-05 7:40 ` Song Liu
2020-10-07 7:02 ` Sung, KoWei
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=CAPhsuW6q5bLgOUyuTH8MFTo6GSnGqRxne6sV+dsFHRy_qHtxRA@mail.gmail.com \
--to=song@kernel.org \
--cc=hansduan@amazon.com \
--cc=htokoyo@amazon.co.jp \
--cc=linux-raid@vger.kernel.org \
--cc=mfortin@amazon.com \
--cc=saeedb@amazon.com \
--cc=winders@amazon.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 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).