[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPhsuW6nVUCYNtW-2a7q+T5zhyw=NhgcfP7jMeV9e_FJ5TfvXg@mail.gmail.com>
Date: Thu, 25 Jan 2024 11:40:36 -0800
From: Song Liu <song@...nel.org>
To: junxiao.bi@...cle.com
Cc: Dan Moulding <dan@...m.net>, gregkh@...uxfoundation.org, linux-kernel@...r.kernel.org,
linux-raid@...r.kernel.org, regressions@...ts.linux.dev,
stable@...r.kernel.org, yukuai1@...weicloud.com
Subject: Re: [REGRESSION] 6.7.1: md: raid5 hang and unresponsive system;
successfully bisected
On Thu, Jan 25, 2024 at 8:44 AM <junxiao.bi@...cle.com> wrote:
>
> Hi Dan,
>
> Thanks for the report.
>
> Can you define the hung? No hung task or other error from dmesg, any
> process in D status and what is the call trace if there is? From the
> perf result, looks like the raid thread is doing some real job, it may
> be issuing io since ops_run_io() took around 20% cpu, please share
> "iostat -xz 1" while the workload is running, i am wondering is this
> some performance issue with the workload?
I am hoping to get a repro on my side. From the information shared
by Dan, the md thread is busy looping on some stripes. The issue
probably only triggers with raid5 journal.
Thanks,
Song
Powered by blists - more mailing lists