Your message dated Wed, 22 Jun 2022 10:12:25 +0200
with message-id <[email protected]>
and subject line Re: Bug#1012787: systemd: Sometimes systemd mount check fails
has caused the Debian Bug report #1012787,
regarding systemd: Sometimes systemd mount check fails
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1012787: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012787
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 241-7~deb10u8
Severity: important
Tags: patch buster
Dear maintainer,
When booting with systemd, sometimes (about once every 10,000 times) system
mount check fails.
The mount is successful, but systemd's mount check fails.
```
...
May 25 19:24:33 local systemd[1]: Started Flush Journal to Persistent Storage.
-- Subject: A start job for unit systemd-journal-flush.service has finished
successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit systemd-journal-flush.service has finished successfully.
--
-- The job identifier is 37.
May 25 19:24:33 local systemd[1]: home.mount: Mount process finished, but there
is no mount.
May 25 19:24:33 local kernel: EXT4-fs (sda3): mounted filesystem with
journalled data mode. Opts: data=journal
May 25 19:24:33 local systemd[1]: home.mount: Failed with result 'protocol'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit home.mount has entered the 'failed' state with result 'protocol'.
May 25 19:24:33 local systemd[1]: Failed to mount /home.
-- Subject: A start job for unit home.mount has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit home.mount has finished with a failure.
--
....
```
This has already been reported[0] on Upstream and some fix suggestions have
been created.
I applied patches[1][2] included in upstream to 241-7~deb10u8 and tested it
about 200,000 times
but the problem no longer reappears. Would you consider applying them?
Best regards,
Nobuhiro
[0]: https://github.com/systemd/systemd/issues/10872
[1]: https://github.com/systemd/systemd/pull/13097
fcd8e119c2 mount: simplify /proc/self/mountinfo handler
350804867d mount: rescan /proc/self/mountinfo before processing waitid()
results
bcce581d65 swap: scan /proc/swaps before processing waitid() results
[2]: https://github.com/systemd/systemd/pull/14234
1d086a6e59 mount: mark an existing "mounting" unit from /proc/self/mountinfo
as "just_mounted"
0001-Fix-mount-units-fail-with-Mount-process-finished-but.patch
Description: 0001-Fix-mount-units-fail-with-Mount-process-finished-but.patch
--- End Message ---
--- Begin Message ---
Version: 245-1
Hi Nobuhiro!
Am 14.06.22 um 04:47 schrieb [email protected]:
When booting with systemd, sometimes (about once every 10,000 times) system
mount check fails.
The mount is successful, but systemd's mount check fails.
...
This has already been reported[0] on Upstream and some fix suggestions have
been created.
I applied patches[1][2] included in upstream to 241-7~deb10u8 and tested it
about 200,000 times
but the problem no longer reappears. Would you consider applying them?
Best regards,
Nobuhiro
[0]: https://github.com/systemd/systemd/issues/10872
[1]: https://github.com/systemd/systemd/pull/13097
fcd8e119c2 mount: simplify /proc/self/mountinfo handler
350804867d mount: rescan /proc/self/mountinfo before processing waitid()
results
bcce581d65 swap: scan /proc/swaps before processing waitid() results
Those patches were included in v243
[2]: https://github.com/systemd/systemd/pull/14234
1d086a6e59 mount: mark an existing "mounting" unit from /proc/self/mountinfo as
"just_mounted"
And those in v245, so marking as fixed for that version.
At this point, oldstable, i.e. buster, will only receive security
related uploads and this change doesn't really qualify as such I think.
I'm thus closing the issue.
My advice would be to upgrade to bullseye or use 247.3-6~bpo10+1 which
we provide via buster-backports.
Regards,
Michael
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
