From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 8E3A9C678DC for ; Fri, 18 Aug 2023 08:17:21 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1358498AbjHRIQv (ORCPT ); Fri, 18 Aug 2023 04:16:51 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45022 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1358543AbjHRIQo (ORCPT ); Fri, 18 Aug 2023 04:16:44 -0400 Received: from mgamail.intel.com (mgamail.intel.com [134.134.136.20]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 363182D7D; Fri, 18 Aug 2023 01:16:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1692346603; x=1723882603; h=date:from:to:cc:subject:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=dc06fUIqtwQAqNbNhGr+uIzCfrj4zxECY6jV06ommyo=; b=hnxLsBR33KUJbAMBLA57wAnRB1nGDZ6LvfkmdPPFcQxkJwj1juZ2ZnI2 P/r2S2OslCllygBWfCUvxPAqaqy4ZPWSrXVIdG5OkZ5rcNUaDBD4olGZA kCp17Hhez9dwAH6O9VlxOhzsFCKHctiiMbUIWvunW4TLlo3Ves+9E2Y8e p77pEDcnHbvcGewy0Eo3C3R6e/+0vp1AGA3krFzKvKVx4SWiK5dpv7Cs2 OJ+tFbAYGQsq1DPlDK7ghOtpwbIlUEghhtxOqMYVkOR9B+0mQJmav3K7y Bj/2MA/dtwynE+qycvpGcWzON7e12s33miC5/7hphg6q/tS8UPfrqvHVK Q==; X-IronPort-AV: E=McAfee;i="6600,9927,10805"; a="363205174" X-IronPort-AV: E=Sophos;i="6.01,182,1684825200"; d="scan'208";a="363205174" Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga101.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 18 Aug 2023 01:16:37 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10805"; a="735014632" X-IronPort-AV: E=Sophos;i="6.01,182,1684825200"; d="scan'208";a="735014632" Received: from mtkaczyk-mobl.ger.corp.intel.com (HELO localhost) ([10.249.139.215]) by orsmga002-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 18 Aug 2023 01:16:35 -0700 Date: Fri, 18 Aug 2023 10:16:30 +0200 From: Mariusz Tkaczyk To: Bagas Sanjaya Cc: Christoph Hellwig , Song Liu , AceLan Kao , Linux Kernel Mailing List , Linux Regressions , Linux RAID Subject: Re: Infiniate systemd loop when power off the machine with multiple MD RAIDs Message-ID: <20230818101630.000027f4@linux.intel.com> In-Reply-To: <028a21df-4397-80aa-c2a5-7c754560f595@gmail.com> References: <028a21df-4397-80aa-c2a5-7c754560f595@gmail.com> X-Mailer: Claws Mail 4.1.0 (GTK 3.24.33; x86_64-w64-mingw32) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-raid@vger.kernel.org On Wed, 16 Aug 2023 16:37:26 +0700 Bagas Sanjaya wrote: > Hi, > > I notice a regression report on Bugzilla [1]. Quoting from it: > > > It needs to build at least 2 different RAIDs(eg. RAID0 and RAID10, RAID5 > > and RAID10) and then you will see below error repeatly(need to use serial > > console to see it) > > > > [ 205.360738] systemd-shutdown[1]: Stopping MD devices. > > [ 205.366384] systemd-shutdown[1]: sd-device-enumerator: Scan all dirs > > [ 205.373327] systemd-shutdown[1]: sd-device-enumerator: Scanning /sys/bus > > [ 205.380427] systemd-shutdown[1]: sd-device-enumerator: Scanning /sys/class > > [ 205.388257] systemd-shutdown[1]: Stopping MD /dev/md127 (9:127). > > [ 205.394880] systemd-shutdown[1]: Failed to sync MD block device > > /dev/md127, ignoring: Input/output error [ 205.404975] md: md127 stopped. > > [ 205.470491] systemd-shutdown[1]: Stopping MD /dev/md126 (9:126). > > [ 205.770179] md: md126: resync interrupted. > > [ 205.776258] md126: detected capacity change from 1900396544 to 0 > > [ 205.783349] md: md126 stopped. > > [ 205.862258] systemd-shutdown[1]: Stopping MD /dev/md125 (9:125). > > [ 205.862435] md: md126 stopped. > > [ 205.868376] systemd-shutdown[1]: Failed to sync MD block device > > /dev/md125, ignoring: Input/output error [ 205.872845] block device > > autoloading is deprecated and will be removed. [ 205.880955] md: md125 > > stopped. [ 205.934349] systemd-shutdown[1]: Stopping MD /dev/md124p2 > > (259:7). [ 205.947707] systemd-shutdown[1]: Could not stop MD /dev/md124p2: > > Device or resource busy [ 205.957004] systemd-shutdown[1]: Stopping MD > > /dev/md124p1 (259:6). [ 205.964177] systemd-shutdown[1]: Could not stop MD > > /dev/md124p1: Device or resource busy [ 205.973155] systemd-shutdown[1]: > > Stopping MD /dev/md124 (9:124). [ 205.979789] systemd-shutdown[1]: Could > > not stop MD /dev/md124: Device or resource busy [ 205.988475] > > systemd-shutdown[1]: Not all MD devices stopped, 4 left. > > See Bugzilla for the full thread and attached full journalctl log. > > Anyway, I'm adding this regression to be tracked by regzbot: > > #regzbot introduced: 12a6caf273240a > https://bugzilla.kernel.org/show_bug.cgi?id=217798 #regzbot title: systemd > shutdown hang on machine with different RAID levels > > Thanks. > > [1]: https://bugzilla.kernel.org/show_bug.cgi?id=217798 > Hello, The issue is reproducible with IMSM metadata too, around 20% of reboot hangs. I will try to raise the priority in the bug because it is valid high- the base functionality of the system is affected. Christoph, could you take a look in short term? Thanks, Mariusz