Re: [REGRESSION] 6.7.1: md: raid5 hang and unresponsive system; successfully bisected

From: junxiao.bi@oracle.com
To: Mateusz Kusiak <mateusz.kusiak@linux.intel.com>,
	Dan Moulding <dan@danm.net>
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
	linux-raid@vger.kernel.org, regressions@lists.linux.dev,
	song@kernel.org, stable@vger.kernel.org
Subject: Re: [REGRESSION] 6.7.1: md: raid5 hang and unresponsive system; successfully bisected
Date: Wed, 21 Feb 2024 11:15:35 -0800	[thread overview]
Message-ID: <c9b3466c-7972-47c0-b590-9c1012b53a82@oracle.com> (raw)
In-Reply-To: <2b5daa31-af66-4297-932b-d2fd341b63e6@linux.intel.com>

On 2/21/24 6:50 AM, Mateusz Kusiak wrote:
> On 21.02.2024 00:15, junxiao.bi@oracle.com wrote:
>>
>> The thing is we can't reproduce this issue at all. If you can 
>> generate a vmcore when the hung happened, then we can review which 
>> processes are stuck.
>>
> Hi,
> don't know if that be any of help, but I run below scenario with SATA 
> and NVMe drives. For me, the issue is reproducible on NVMe drives only.
>
> Scenario:
> 1. Create R5D3 with native metadata
>     # mdadm -CR /dev/md/vol -l5 -n3 /dev/nvme[0-2]n1 --assume-clean
> 2. Create FS on the array
>     # mkfs.ext4 /dev/md/vol -F
> 3. Remove single member drive via "--incremental --fail"
>     # mdadm -If nvme0n1
>
> The result is almost instant.

This is not the same issue that Dan reported, it looks like another 
regression that Yu Kuai fixed , can you please try this patch?

https://lore.kernel.org/lkml/95f2e08e-2daf-e298-e696-42ebfa7b9bbf@huaweicloud.com/

Thanks,

Junxiao.

>
> Thanks,
> Mateusz