http://bugzilla.suse.com/show_bug.cgi?id=1137373 Alynx Zhou changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alynx.zhou@suse.com Assignee|bnc-team-screening@forge.pr |systemd-maintainers@suse.de |ovo.novell.com | -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1137373 http://bugzilla.suse.com/show_bug.cgi?id=1137373#c3 Daniele Tombolini changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |systemd-maintainers@suse.de Flags| |needinfo?(systemd-maintaine | |rs@suse.de) --- Comment #3 from Daniele Tombolini --- Created attachment 809053 --> http://bugzilla.suse.com/attachment.cgi?id=809053&action=edit journalctl -b -o short-monotonic log -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1137373 http://bugzilla.suse.com/show_bug.cgi?id=1137373#c4 --- Comment #4 from Franck Bui ---

From your logs:

[ 27.937471] fyrfos systemd[1]: dev-disk-by\x2duuid-44dccc07\x2d9527\x2d4ea7\x2d8e15\x2d5dc63486a9cd.device: Changed plugged -> dead [ 27.937545] fyrfos systemd[1]: local.mount: Trying to enqueue job local.mount/stop/replace [ 27.937617] fyrfos systemd[1]: Added job local.mount/stop to transaction.

It seems that the device for /local was unplugged during the boot process but it would be great if you could provide the debug logs for udev as well. In order to do so, please resend the journal content but with the following kernel command line options: "debug printk.devkmsg=on". Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1137373 Daniele Tombolini changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(systemd-maintaine | |rs@suse.de) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1137373 Franck Bui changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(systemd-maintaine | |rs@suse.de) | -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1137373 http://bugzilla.suse.com/show_bug.cgi?id=1137373#c8 --- Comment #8 from Franck Bui --- I reported this issue to upstream so it hopefully get fixed soon: https://github.com/systemd/systemd/issues/12953 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1137373 http://bugzilla.suse.com/show_bug.cgi?id=1137373#c10 Daniele Tombolini changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(kailed@kailed.net | |) | --- Comment #10 from Daniele Tombolini --- (In reply to Franck Bui from comment #9)

Daniele, would it be possible to give the following test project a try ?

https://download.opensuse.org/repositories/home:/fbui:/systemd:/next:/ openSUSE-Factory/openSUSE_Tumbleweed/

Thanks.

Done ! Now Systemd and udev are at version 239 and, after a reboot, everything is working as expected ! Let me now if you need more info... Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1137373 http://bugzilla.suse.com/show_bug.cgi?id=1137373#c12 Franck Bui changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(kailed@kailed.net | |) --- Comment #12 from Franck Bui --- (In reply to Daniele Tombolini from comment #10)

Now Systemd and udev are at version 239

That's not the right version as you were supposed to test v242 + some patches... I re-triggered a build of the test project and now the repository contains the correct version of systemd. Can you retry your testing please ? Sorry for the inconvenience. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1137373 http://bugzilla.suse.com/show_bug.cgi?id=1137373#c14 --- Comment #14 from Franck Bui --- Could you give it a few more tries so we can be confident that your issue is fixed ? Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1137373 Daniele Tombolini changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(systemd-maintaine | |rs@suse.de) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1137373 Fabian Vogt changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fvogt@suse.com -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1137373 http://bugzilla.suse.com/show_bug.cgi?id=1137373#c31 Franck Bui changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |axel.braun@gmx.de --- Comment #31 from Franck Bui --- *** Bug 1165943 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1137373 http://bugzilla.suse.com/show_bug.cgi?id=1137373#c32 --- Comment #32 from Franck Bui --- *** Bug 1165946 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1137373 https://bugzilla.suse.com/show_bug.cgi?id=1137373#c34 --- Comment #34 from владимир путин <1000Hz.radiowave@gmail.com> --- Can this btrfsmaintenance just be removed by default? It seem to cause more troubles than good. Besides, balancing of btrfs nowadays is not recommended, according to btrfs kernel wiki. And balancing with -susage=... is plain dangerous. Modern btrfs tools wont even allow to do it anymore unless you force it. And scrap won't help if you don't have redundant copy in some sort of raid. So this package basically does a lot of troubles all around the system without any real benefit. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1137373 https://bugzilla.suse.com/show_bug.cgi?id=1137373#c36 --- Comment #36 from Michael Hirmke --- (In reply to Franck Bui from comment #35)

(In reply to владимир путин from comment #34)

...

Can this btrfsmaintenance just be removed by default? It seem to cause more

For btrfsmaintenance complaints can you please use bug #1165780 instead ?

This bug deals specifically with the race that might happen when PID1 is reloading.

Thanks

In the meantime I found a workaround. Whenever an update triggered a reload of PID 1, run "init 3" before running "init 6". Since then, I never had this problem any longer. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1137373 Hans-Peter Jansen changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hpj@urpla.net -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1137373 Franck Bui changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://github.com/systemd/ | |systemd/issues/12953 -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1137373 https://bugzilla.suse.com/show_bug.cgi?id=1137373#c42 --- Comment #42 from Michael Hirmke --- (In reply to Franck Bui from comment #41)

This problem was fixed on TW (still need to be fixed on Leap :-/) and that's the reason why the race is unlikely to happen on this distro since now.

While waiting for the workaround, Leap users can follow the procedure described in comment #25.

But I still habe the problem on *Tumbleweed* (latest snapshot)! -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1137373 https://bugzilla.suse.com/show_bug.cgi?id=1137373#c44 --- Comment #44 from Michael Hirmke --- (In reply to Franck Bui from comment #43)

(In reply to Michael Hirmke from comment #42)

...

But I still habe the problem on *Tumbleweed* (latest snapshot)!

Then you need to figure out what's triggering PID1 reloads during early boot.

So how can I do that? As mentioned, it only happens after having run a zypper dup before reboot. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1137373 https://bugzilla.suse.com/show_bug.cgi?id=1137373#c46 --- Comment #46 from Michael Hirmke --- (In reply to Franck Bui from comment #45)

(In reply to Michael Hirmke from comment #44)

...

So how can I do that? As mentioned, it only happens after having run a zypper dup before reboot.

Then it's probably a different issue.

Can you please open a new bug report with a description of the steps you did to trigger the issue ?

Also please attach the debug logs (the output of 'journactl -b -oshort-monotonic') when the problem occurs. You can run 'systemctl log-level debug' just before running zypper, no need for the complete debug logs since it doesn't happen during the boot process.

There already was a but report last year: https://bugzilla.suse.com/show_bug.cgi?id=1155170 Nothing has changed since then. But of course I can provide the logs, after it has happened again. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1137373 https://bugzilla.suse.com/show_bug.cgi?id=1137373#c53 Franck Bui changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #53 from Franck Bui --- This bug should be fixed by the release of systemd v251.2 eventually. Hence closing. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1137373 https://bugzilla.suse.com/show_bug.cgi?id=1137373#c58 --- Comment #58 from Swamp Workflow Management --- SUSE-RU-2022:2470-2: An update that has 8 recommended fixes can now be installed. Category: recommended (important) Bug References: 1137373,1181658,1194708,1195157,1197570,1198507,1198732,1200170 CVE References: JIRA References: Sources used: openSUSE Leap Micro 5.2 (src): systemd-246.16-150300.7.48.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.