All of lore.kernel.org
 help / color / mirror / Atom feed
From: AceLan Kao <acelan@gmail.com>
To: Yu Kuai <yukuai1@huaweicloud.com>
Cc: Bagas Sanjaya <bagasdotme@gmail.com>,
	Christoph Hellwig <hch@lst.de>, Song Liu <song@kernel.org>,
	 Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	 Linux Regressions <regressions@lists.linux.dev>,
	Linux RAID <linux-raid@vger.kernel.org>,
	 "yukuai (C)" <yukuai3@huawei.com>
Subject: Re: Fwd: Infiniate systemd loop when power off the machine with multiple MD RAIDs
Date: Tue, 22 Aug 2023 09:39:03 +0800	[thread overview]
Message-ID: <CAMz9Wg8kanG=2g6Y8TVcB7-=O8MgXrjgJ0YCewqa0cM51nXf=g@mail.gmail.com> (raw)
In-Reply-To: <433392a3-5ec4-cd63-fa5b-58e24deb56b9@huaweicloud.com>

Yu Kuai <yukuai1@huaweicloud.com> 於 2023年8月21日 週一 下午9:18寫道:
>
> Hi,
>
> 在 2023/08/16 17:37, Bagas Sanjaya 写道:
> > 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.
>
> Without the problem, did the log complain about this?
>
> Could not stop MD...Device or resource busy
>
> Thanks,
> Kuai
>
> >
> > 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
> >
>
Hi Yu,

Everything looks normal.
I can see the MD raids stop without any warning/error messages.

$ sudo journalctl -b -2 -k -o short-monotonic | egrep md[0-9]+
[   13.418154] u-Precision-7960-Tower kernel: md/raid10:md125: active
with 4 out of 4 devices
[   13.424050] u-Precision-7960-Tower kernel: md125: detected capacity
change from 0 to 1900396544
[   13.525198] u-Precision-7960-Tower kernel: md123: detected capacity
change from 0 to 1900396544
[   13.576770] u-Precision-7960-Tower kernel: md122: detected capacity
change from 0 to 1900417024
[   13.585705] u-Precision-7960-Tower kernel:  md122: p1 p2 p3
[   14.323717] u-Precision-7960-Tower kernel: EXT4-fs (md122p3):
mounted filesystem 6d53dc8e-3f45-4efa-bc0e-4af477fac217 ro with
ordered data mode. Quota mode: none.
[   14.814365] u-Precision-7960-Tower systemd-gpt-auto-generator[587]:
md122p3: Root device /dev/md122.
[   14.829064] u-Precision-7960-Tower kernel: block md122: the
capability attribute has been deprecated.
[   18.133316] u-Precision-7960-Tower systemd[1]:
unit_file_build_name_map: normal unit file:
/lib/systemd/system/casper-md5check.service
[   20.609948] u-Precision-7960-Tower kernel: EXT4-fs (md122p3):
re-mounted 6d53dc8e-3f45-4efa-bc0e-4af477fac217 r/w. Quota mode: none.
[   39.161554] u-Precision-7960-Tower kernel: md: requested-resync of
RAID array md125
[   77.344788] u-Precision-7960-Tower systemd[1]: Got message
type=signal sender=org.freedesktop.DBus
destination=org.freedesktop.systemd1 path=/org/freedesktop/DBus int
erface=org.freedesktop.systemd1.Activator member=ActivationRequest
cookie=89 reply_cookie=0 signature=s error-name=n/a error-message=n/a
[   77.736790] u-Precision-7960-Tower systemd[1]: Sent message
type=signal sender=n/a destination=n/a path=/org/freedesktop/systemd1
interface=org.freedesktop.systemd1.M
anager member=UnitNew cookie=716 reply_cookie=0 signature=so
error-name=n/a error-message=n/a
[   77.772791] u-Precision-7960-Tower systemd[1]: Sent message
type=signal sender=n/a destination=n/a path=/org/freedesktop/systemd1
interface=org.freedesktop.systemd1.M
anager member=UnitRemoved cookie=717 reply_cookie=0 signature=so
error-name=n/a error-message=n/a
[   77.808791] u-Precision-7960-Tower systemd[1]: Sent message
type=signal sender=n/a destination=n/a path=/org/freedesktop/systemd1
interface=org.freedesktop.systemd1.M
anager member=UnitNew cookie=718 reply_cookie=0 signature=so
error-name=n/a error-message=n/a
[   77.844795] u-Precision-7960-Tower systemd[1]: Sent message
type=signal sender=n/a destination=n/a path=/org/freedesktop/systemd1
interface=org.freedesktop.systemd1.M
anager member=UnitRemoved cookie=719 reply_cookie=0 signature=so
error-name=n/a error-message=n/a
[   77.880866] u-Precision-7960-Tower systemd[1]: Sent message
type=signal sender=n/a destination=n/a path=/org/freedesktop/systemd1
interface=org.freedesktop.systemd1.M
anager member=UnitNew cookie=720 reply_cookie=0 signature=so
error-name=n/a error-message=n/a
[   77.916817] u-Precision-7960-Tower systemd[1]: Sent message
type=signal sender=n/a destination=n/a path=/org/freedesktop/systemd1
interface=org.freedesktop.systemd1.M
anager member=JobNew cookie=721 reply_cookie=0 signature=uos
error-name=n/a error-message=n/a
[   79.072786] u-Precision-7960-Tower systemd[1]: Sent message
type=signal sender=n/a destination=n/a
path=/org/freedesktop/systemd1/unit/systemd_2dlocaled_2eservice int
erface=org.freedesktop.DBus.Properties member=PropertiesChanged
cookie=724 reply_cookie=0 signature=sa{sv}as error-name=n/a
error-message=n/a
[   79.112778] u-Precision-7960-Tower systemd[1]: Sent message
type=signal sender=n/a destination=n/a
path=/org/freedesktop/systemd1/unit/systemd_2dlocaled_2eservice int
erface=org.freedesktop.DBus.Properties member=PropertiesChanged
cookie=725 reply_cookie=0 signature=sa{sv}as error-name=n/a
error-message=n/a
[   79.188801] u-Precision-7960-Tower systemd[1]: Sent message
type=signal sender=n/a destination=n/a
path=/org/freedesktop/systemd1/unit/systemd_2dlocaled_2eservice int
erface=org.freedesktop.DBus.Properties member=PropertiesChanged
cookie=726 reply_cookie=0 signature=sa{sv}as error-name=n/a
error-message=n/a
[   79.228790] u-Precision-7960-Tower systemd[1]: Sent message
type=signal sender=n/a destination=n/a
path=/org/freedesktop/systemd1/unit/systemd_2dlocaled_2eservice int
erface=org.freedesktop.DBus.Properties member=PropertiesChanged
cookie=727 reply_cookie=0 signature=sa{sv}as error-name=n/a
error-message=n/a
[   79.268794] u-Precision-7960-Tower systemd[1]: Sent message
type=signal sender=n/a destination=n/a
path=/org/freedesktop/systemd1/job/1915 interface=org.freedesktop.D
Bus.Properties member=PropertiesChanged cookie=728 reply_cookie=0
signature=sa{sv}as error-name=n/a error-message=n/a
[   81.064804] u-Precision-7960-Tower systemd[1]: Got message
type=method_call sender=:1.67 destination=org.freedesktop.systemd1
path=/org/freedesktop/systemd1 interface
=org.freedesktop.DBus.Properties member=Get cookie=31 reply_cookie=0
signature=ss error-name=n/a error-message=n/a
[  286.066341] u-Precision-7960-Tower kernel: md123: detected capacity
change from 1900396544 to 0
[  286.073500] u-Precision-7960-Tower kernel: md: md123 stopped.
[  286.175794] u-Precision-7960-Tower kernel: md: md124 stopped.


-- 
Chia-Lin Kao(AceLan)
http://blog.acelan.idv.tw/
E-Mail: acelan.kaoATcanonical.com (s/AT/@/)

  reply	other threads:[~2023-08-22  1:39 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-16  9:37 Fwd: Infiniate systemd loop when power off the machine with multiple MD RAIDs Bagas Sanjaya
2023-08-18  8:16 ` Mariusz Tkaczyk
2023-08-18  9:21   ` Hannes Reinecke
2023-08-21  3:23     ` AceLan Kao
2023-08-22  3:51   ` Guoqing Jiang
2023-08-22  6:17     ` Song Liu
2023-08-22  6:39       ` Mariusz Tkaczyk
2023-08-22  8:13         ` AceLan Kao
2023-08-22 12:41           ` Guoqing Jiang
2023-08-23  8:02             ` AceLan Kao
2023-08-23 13:25               ` Song Liu
2023-08-26  4:31                 ` AceLan Kao
2023-08-28  5:20                   ` Song Liu
2023-08-28 10:48                     ` AceLan Kao
2023-08-29  3:12                       ` AceLan Kao
2023-08-28 13:50                     ` Yu Kuai
2023-08-31  2:28                       ` Yu Kuai
2023-08-31  6:50                         ` Mariusz Tkaczyk
2023-09-06  6:26                           ` AceLan Kao
2023-09-06 10:27                             ` Mariusz Tkaczyk
2023-09-07  2:04                               ` Yu Kuai
2023-09-07 10:18                                 ` Mariusz Tkaczyk
2023-09-07 11:26                                   ` Yu Kuai
2023-09-07 12:14                                     ` Yu Kuai
2023-09-07 12:41                                       ` Mariusz Tkaczyk
2023-09-07 12:53                                         ` Yu Kuai
2023-09-07 15:09                                           ` Mariusz Tkaczyk
2023-09-08 20:25                                             ` Song Liu
2023-08-21 13:18 ` Fwd: " Yu Kuai
2023-08-22  1:39   ` AceLan Kao [this message]
2023-08-22 18:56 ` Song Liu
2023-08-22 19:13   ` Carlos Carvalho
2023-08-23  1:28     ` Yu Kuai
2023-08-23  6:04       ` Hannes Reinecke

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAMz9Wg8kanG=2g6Y8TVcB7-=O8MgXrjgJ0YCewqa0cM51nXf=g@mail.gmail.com' \
    --to=acelan@gmail.com \
    --cc=bagasdotme@gmail.com \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    --cc=song@kernel.org \
    --cc=yukuai1@huaweicloud.com \
    --cc=yukuai3@huawei.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.