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 37460C41513 for ; Wed, 16 Aug 2023 09:38:10 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S243402AbjHPJhj (ORCPT ); Wed, 16 Aug 2023 05:37:39 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52710 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S243455AbjHPJhb (ORCPT ); Wed, 16 Aug 2023 05:37:31 -0400 Received: from mail-pl1-x62c.google.com (mail-pl1-x62c.google.com [IPv6:2607:f8b0:4864:20::62c]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7A4DF26A4; Wed, 16 Aug 2023 02:37:30 -0700 (PDT) Received: by mail-pl1-x62c.google.com with SMTP id d9443c01a7336-1bb84194bf3so39158015ad.3; Wed, 16 Aug 2023 02:37:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1692178650; x=1692783450; h=content-transfer-encoding:subject:from:cc:to:content-language :user-agent:mime-version:date:message-id:from:to:cc:subject:date :message-id:reply-to; bh=1lS1r+gat9gKV1Ap/cgPo1okEN4ipNq1TwCugcvDik0=; b=p9vcUD7SG77yUjMoY4NXQ+ZkQjjj7s7oNy2iUAz+wM9vTKo45qPNzO9dsjJ9YxWsXU 4bl4dOOmDm1KHlBvFoaXmYQimcShmpiHLhQuT7GJTZJyCjI/z6kH5I2/ahA4SeNagndD xl+loyaQVE0TpFvRzOEXw83qeBY67QOMj7DBFdU4nb5B/lU9ALwPIim9kOOdkYmW64MW /I/yHNlMMEI6aKsEROR/rt3OanyYe2ZrWSYwBf5XopMNsilqGL0OtDgGo1eoF3cSOaXm CYa/xDH73140/MZQQ4CW1815P2i31hfteCvGOFfLcZkdSn8vOHFvt4YMUY2CuL5vSIHk r+dw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1692178650; x=1692783450; h=content-transfer-encoding:subject:from:cc:to:content-language :user-agent:mime-version:date:message-id:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to; bh=1lS1r+gat9gKV1Ap/cgPo1okEN4ipNq1TwCugcvDik0=; b=NDwW335Uuas05v2KU+xRmDxJIbNsWjjw9/RgEHDVkxE4juKhItPbHeVrLVp8ro180j wfe1R0Dzz13G6NDclIeojlE+o+wjF+0d+kH4mjZEDWmYF+cNEoyYdPjFFvHvL2wSQsyG GQyFV5DR81UmXBv6AO0XmU/Q1BbxAIYK13VnGXphDuxgYHTv0dLC9G6KCH6Y+dLrK2WS 9TMKhgpHkiifd4z4Pk9QiPNhMaL2sMVBaXZFlmdWggZ2hhs+S5gOrQ+a468C1TZEpYbf 5kPd95/mpYUtqUbBAsy2CQYrdu6AMIpGocYfwoVWXe2tvAjcIHIUzyIEcTX95SPhBD9G 0vdA== X-Gm-Message-State: AOJu0YwZYyosBz1sYLmzlfEC4RWb5Gwl5MR39CL+oGblhmWRsy274nko Y68rrDANIen1riyhgURpWgk= X-Google-Smtp-Source: AGHT+IHGoKGbh8REsOj7FWUiAtyf3Z/SSp0bH7SDpB1ScBpX2GzKpd9GEewooAZU8xvsVHYNUiYs2g== X-Received: by 2002:a17:902:6b86:b0:1bc:56c3:ebb7 with SMTP id p6-20020a1709026b8600b001bc56c3ebb7mr949752plk.20.1692178649825; Wed, 16 Aug 2023 02:37:29 -0700 (PDT) Received: from [192.168.0.105] ([103.124.138.83]) by smtp.gmail.com with ESMTPSA id n4-20020a170902d2c400b001bb6c5ff4edsm12670642plc.173.2023.08.16.02.37.27 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 16 Aug 2023 02:37:29 -0700 (PDT) Message-ID: <028a21df-4397-80aa-c2a5-7c754560f595@gmail.com> Date: Wed, 16 Aug 2023 16:37:26 +0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.14.0 Content-Language: en-US To: Christoph Hellwig , Song Liu , AceLan Kao Cc: Linux Kernel Mailing List , Linux Regressions , Linux RAID From: Bagas Sanjaya Subject: Fwd: Infiniate systemd loop when power off the machine with multiple MD RAIDs Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-raid@vger.kernel.org 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 -- An old man doll... just what I always wanted! - Clara