Received-SPF: pass (google.com: domain of linux-kernel+bounces-40299-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3;
From: Dan Moulding <dan@danm.net>
To: carlos@fisica.ufpr.br
Cc: dan@danm.net,
	gregkh@linuxfoundation.org,
	junxiao.bi@oracle.com,
	linux-kernel@vger.kernel.org,
	linux-raid@vger.kernel.org,
	regressions@lists.linux.dev,
	song@kernel.org,
	stable@vger.kernel.org,
	yukuai1@huaweicloud.com
Subject: [REGRESSION] 6.7.1: md: raid5 hang and unresponsive system; successfully bisected
Date: Fri, 26 Jan 2024 08:46:10 -0700
Message-ID: <20240126154610.24755-1-dan@danm.net>
In-Reply-To: <ZbMnZnvyIyoWeIro@fisica.ufpr.br>
References: <ZbMnZnvyIyoWeIro@fisica.ufpr.br>
Precedence: bulk
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit

> It's known that ext4 has these symptoms with parity raid.

Interesting. I'm not aware of that problem. One of the systems that
hit this hang has been running with ext4 on an MD RAID-5 array with
every kernel since at least 5.1 and never had an issue until this
regression.

> To make sure it's a raid problem you should try another filesystem or
> remount it with stripe=0.

That's a good suggestion, so I switched it to use XFS. It can still
reproduce the hang. Sounds like this is probably a different problem
than the known ext4 one.

Thanks,

-- Dan