From: Askar Safin <safinaskar@gmail.com>
To: lists@colorremedies.com
Cc: linux-btrfs@vger.kernel.org
Subject: Re: 6.17rc5: btrfs scrub, Freezing user space processes failed
Date: Sun, 12 Oct 2025 11:52:56 +0300 [thread overview]
Message-ID: <20251012085256.8628-1-safinaskar@gmail.com> (raw)
In-Reply-To: <d93b2a2d-6ad9-4c49-809f-11d769a6f30a@app.fastmail.com>
"Chris Murphy" <lists@colorremedies.com>:
> Scrub initiated, walked away, and when I come back it appears hung with a black screen unresponsive
I suspect here is interplay between two issues.
First is btrfs kernel bug Qu Wenruo is talking about.
Second is systemd issue, which amplifies this kernel bug.
Systemd bug turns simple "suspend doesn't work, but system continues to
operate normally" to "reboot is needed".
I wrote about this here: https://github.com/systemd/systemd/issues/38337 .
The bug is fixed in mainline and stable versions of systemd.
So you should just upgrade your systemd. The fix is backported to stable
systemd versions, so it should come to all stable Linux distros on its own.
Suspend still will not work if
scrub is running, but at least your system will be operational after
failed suspend attempt.
If this still doesn't help, then, please, tell me your full systemd version
and distro version.
--
Askar Safin
next prev parent reply other threads:[~2025-10-12 8:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-13 21:57 6.17rc5: btrfs scrub, Freezing user space processes failed Chris Murphy
2025-09-15 23:16 ` Chris Murphy
2025-09-15 23:37 ` Qu Wenruo
2025-09-15 23:51 ` Chris Murphy
2025-10-12 8:52 ` Askar Safin [this message]
2025-10-12 22:10 ` Chris Murphy
2025-10-16 22:15 ` Chris Murphy
2025-10-17 11:01 ` Askar Safin
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=20251012085256.8628-1-safinaskar@gmail.com \
--to=safinaskar@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox