From: "Chris Murphy" <lists@colorremedies.com>
To: "Askar Safin" <safinaskar@gmail.com>
Cc: "Btrfs BTRFS" <linux-btrfs@vger.kernel.org>
Subject: Re: 6.17rc5: btrfs scrub, Freezing user space processes failed
Date: Thu, 16 Oct 2025 18:15:32 -0400 [thread overview]
Message-ID: <30c367f1-f65d-4ba5-a4a3-776bb308a682@app.fastmail.com> (raw)
In-Reply-To: <19dd908b-12df-45ad-bde4-ab7281557608@app.fastmail.com>
On Sun, Oct 12, 2025, at 6:10 PM, Chris Murphy wrote:
> On Sun, Oct 12, 2025, at 4:52 AM, Askar Safin wrote:
>> "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.
>
> Thanks for the response.
>
> I've since moved to Fedora 43 (pre-release) which has
> systemd-258-1.fc43.x86_64.
>
> Fedora 42 still has systemd-257.9-2.fc42 which is what I was running at
> the time of the problem.
I'm told the fix is already in the systemd I had when Inran into the problem. Fix is in 257.8 and I had 257.9-2.
--
Chris Murphy
next prev parent reply other threads:[~2025-10-16 22:15 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
2025-10-12 22:10 ` Chris Murphy
2025-10-16 22:15 ` Chris Murphy [this message]
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=30c367f1-f65d-4ba5-a4a3-776bb308a682@app.fastmail.com \
--to=lists@colorremedies.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=safinaskar@gmail.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