Received: by 2002:a05:7412:3290:b0:fa:6e18:a558 with SMTP id ev16csp716836rdb; Fri, 26 Jan 2024 08:33:36 -0800 (PST) X-Google-Smtp-Source: AGHT+IFqL4vdk9Ilv3bwY1JTbtYmitxmdmB688/K6DLdR1dYiJrisTPjofL0oydpcljCpqe+MKwn X-Received: by 2002:a05:6358:1807:b0:176:38e:7601 with SMTP id u7-20020a056358180700b00176038e7601mr1857105rwm.30.1706286816290; Fri, 26 Jan 2024 08:33:36 -0800 (PST) ARC-Seal: i=2; a=rsa-sha256; t=1706286816; cv=pass; d=google.com; s=arc-20160816; b=JX8+gDgSUgjXJMp4Sabc8Q6FnnzSqe2nUk4FAQEqE2Sn1z6JPpsbztjhqY0Gjfk1D8 SlXyYeF2i9RWitqPC1k1yHQXo5L0gLOlcdmMNXjjpuffYQTfvmEapr47qaxfhTMkKyVN Q3Y8M1Jv9EQVgJDn9feSRvMVDTzYeFtEQEhnsm2RaBFMSOvJGhbiISBnODEagHwv2tAL m/aT1tJ1wwC/ImS0XLnPgVjcKIcFoJdRsp6HvH4Kpxs3A2+5erYSurDzLm/+nNUEwp0f up/dKVNIAo6CoUSuRI+0lKHWEpcGyqqxZa62y3Puf/ieJpZkMufCeX6mtMdUk5lXUpa5 kZ1w== ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:mime-version:list-unsubscribe :list-subscribe:list-id:precedence:references:in-reply-to:message-id :subject:cc:to:from:date; bh=XVLAvcqId6sulJ1xRFThuWp88WWxQIxnU+uZJkiniNk=; fh=Pf4/gwbHahmHzxDzd9Jemsu7HVaXOegp+niHp0r206A=; b=UWcIpAw91WQRx/L0Q3w2O3poJNf9gv1nMjqNX0cIf4dBTjtwsPVpvsfsbq3M/sHy7f GZf+InZtq7AmXmXjyp4gsFqDqPh1m7dC/Wofb736BaAjRNK6jYMfd/nK7Epf/IQZSzPx NIUWUpgX9p+u2yswWBxw+xM7BUq8F+n0P3nJDAyi9vQLppf7VwafMfBLospngYX/rpW8 7Cgiv6ZJSXVJUcpkS7JoLgH5AljpBL+bsP0UILCNZaAtvogY0rYMauEORWhMdY30sGcB HCPATjLSfbJXThyP42o3DiOQ5uB5ZAhfDuSRP2QL+z/0OLEEOnFCE0ksCLdt9s0ARTf2 QC4w== ARC-Authentication-Results: i=2; mx.google.com; arc=pass (i=1 spf=pass spfdomain=romanrm.net); spf=pass (google.com: domain of linux-kernel+bounces-40338-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:40f1:3f00::1 as permitted sender) smtp.mailfrom="linux-kernel+bounces-40338-linux.lists.archive=gmail.com@vger.kernel.org" Return-Path: Received: from sy.mirrors.kernel.org (sy.mirrors.kernel.org. [2604:1380:40f1:3f00::1]) by mx.google.com with ESMTPS id s28-20020a63525c000000b00565e0624182si1347842pgl.404.2024.01.26.08.33.35 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 26 Jan 2024 08:33:36 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel+bounces-40338-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:40f1:3f00::1 as permitted sender) client-ip=2604:1380:40f1:3f00::1; Authentication-Results: mx.google.com; arc=pass (i=1 spf=pass spfdomain=romanrm.net); spf=pass (google.com: domain of linux-kernel+bounces-40338-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:40f1:3f00::1 as permitted sender) smtp.mailfrom="linux-kernel+bounces-40338-linux.lists.archive=gmail.com@vger.kernel.org" Received: from smtp.subspace.kernel.org (wormhole.subspace.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by sy.mirrors.kernel.org (Postfix) with ESMTPS id 58F5CB2361A for ; Fri, 26 Jan 2024 16:30:23 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id 922A31DDF5; Fri, 26 Jan 2024 16:30:12 +0000 (UTC) Received: from shin.romanrm.net (shin.romanrm.net [146.185.199.61]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id DC53D1D69B; Fri, 26 Jan 2024 16:30:08 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=146.185.199.61 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1706286612; cv=none; b=YcieeiZOtyp4Ygyx5qEDXaQxxvHgAm8C0XBj1EyZhptAnzCfKVg/e/w+7u6hAKtnngGWQW7Rzj3bE3B2t9iY3u88tL+daaUnpnCfnxaYvYoJTOPfZuFvJpkIwEqPpPB4ScbbzXuWlv0+obMSnxa4CG/kw9YD9aaVlwCE+LSqCE8= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1706286612; c=relaxed/simple; bh=juwBFU+dDgaSzOGfV33Nf3WE1fOrDnyv59tl7BpARXk=; h=Date:From:To:Cc:Subject:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=jepdFjIo0swIv1i74QHaeI/N8K7Ti2mIXVaZDcOXuynI5DoPET6ueVJwxisxiTxrmoBz27y91A0zaCjqY6YuYZZvCqqMVqOg6pCTmrH8YWufsb4LMocAwuvcexdsgy6CNofasNFYGWfqhrIbkEei2MGvwwB60qI/oiMS4RMXXg0= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=romanrm.net; spf=pass smtp.mailfrom=romanrm.net; arc=none smtp.client-ip=146.185.199.61 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=romanrm.net Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=romanrm.net Received: from nvm (unknown [IPv6:fd39::4a:3cff:fe57:d6b5]) by shin.romanrm.net (Postfix) with SMTP id 92F0040BAA; Fri, 26 Jan 2024 16:21:55 +0000 (UTC) Date: Fri, 26 Jan 2024 21:21:50 +0500 From: Roman Mamedov To: Carlos Carvalho Cc: Dan Moulding , junxiao.bi@oracle.com, gregkh@linuxfoundation.org, 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: Re: [REGRESSION] 6.7.1: md: raid5 hang and unresponsive system; successfully bisected Message-ID: <20240126212150.4b56ae05@nvm> In-Reply-To: References: <2ef7d741-3df8-402a-967f-53ec77c73e2c@oracle.com> <20240125203130.28187-1-dan@danm.net> X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.31; x86_64-pc-linux-gnu) Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Fri, 26 Jan 2024 00:30:46 -0300 Carlos Carvalho wrote: > Dan Moulding (dan@danm.net) wrote on Thu, Jan 25, 2024 at 05:31:30PM -03: > > I then created an ext4 file system on the "data" volume, mounted it, and used > > "dd" to copy 1MiB blocks from /dev/urandom to a file on the "data" file > > system, and just let it run. Eventually "dd" hangs and top shows that > > md0_raid5 is using 100% CPU. > > It's known that ext4 has these symptoms with parity raid. To make sure it's a > raid problem you should try another filesystem or remount it with stripe=0. If Ext4 wouldn't work properly on parity RAID, then it is a bug that should be tracked down and fixed, not worked around by using a different FS. I am in disbelief you are seriously suggesting that, and to be honest really doubt there is any such high-profile "known" issue that stays unfixed and is just commonly worked around. -- With respect, Roman