Received-SPF: pass (google.com: domain of linux-kernel+bounces-74937-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) client-ip=139.178.88.99;
Message-ID: <2b5daa31-af66-4297-932b-d2fd341b63e6@linux.intel.com>
Date: Wed, 21 Feb 2024 15:50:26 +0100
Precedence: bulk
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [REGRESSION] 6.7.1: md: raid5 hang and unresponsive system;
 successfully bisected
To: junxiao.bi@oracle.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
References: <20240123005700.9302-1-dan@danm.net>
 <20240220230658.11069-1-dan@danm.net>
 <f32cd478-a905-4e98-a46c-0612bc10c38e@oracle.com>
Content-Language: pl
From: Mateusz Kusiak <mateusz.kusiak@linux.intel.com>
In-Reply-To: <f32cd478-a905-4e98-a46c-0612bc10c38e@oracle.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

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.

Thanks,
Mateusz