Kai Lüke
eefb46c83b
The indirect discard in mkfs.btrfs on the loop device mapped to the region on disk can hang and fail the first-boot creation of the rootfs. Since there already is a discard done we anyway don't need to do it twice. This might help for most cases to avoid the failure in mkfs.btrfs. Keep track if the direct discard worked and then skip the mkfs.btrfs discard if it did. This still leaves the case where mkfs.btrfs can hang when the direct discard couldn't succeed and mkfs.btrfs tries again but since the conditions are rather the same it might be that this case is not easy to trigger. If the problem still shows up and the kernel won't be fixed soon we can still disable the mkfs discard for at least btrfs.
System and Service Manager
Details
Most documentation is available on systemd's web site.
Assorted, older, general information about systemd can be found in the systemd Wiki.
Information about build requirements is provided in the README file.
Consult our NEWS file for information about what's new in the most recent systemd versions.
Please see the Code Map for information about this repository's layout and content.
Please see the Hacking guide for information on how to hack on systemd and test your modifications.
Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.
When preparing patches for systemd, please follow our Coding Style Guidelines.
If you are looking for support, please contact our mailing list, join our IRC channel #systemd on libera.chat or Matrix channel
Stable branches with backported patches are available in the stable repo.
We have a security bug bounty program sponsored by the Sovereign Tech Fund hosted on YesWeHack
Repositories with distribution packages built from git main are available on OBS, and also repositories with packages built from the latest stable release