Chris Murphy

OK doing only `--force --repair` on a new but empty btrfs on /dev/loop0, it didn't actually make changes so it didn't corrupt the file system. But adding `--init-extent-tree` did: ```...

> Why would dracut and a 300s delay be necessary? Same reason as for mdadm raid. To be certain the device isn't merely slow to appear. Degraded operation is obviously...

Even if we don't remove the entries: This: https://src.fedoraproject.org/rpms/grub2/c/3e40727f723213b92defb8df7396e6c579480483?branch=rawhide plus this: https://github.com/rhinstaller/anaconda/blob/master/pyanaconda/modules/storage/bootloader/utils.py#L248 means that an installation will replace the unique information in the existing BLS snippets, breaking them anyway. https://bugzilla.redhat.com/show_bug.cgi?id=2120845

The problem in [1874724](https://bugzilla.redhat.com/show_bug.cgi?id=1874724) doesn't happen with Server, all the BLS snippets are present. (However I do hit bug [2120845](https://bugzilla.redhat.com/show_bug.cgi?id=2120845) thus the pre-existing are broken.) I did a side-by-side installation...

[18 days ago](https://github.com/systemd/systemd/issues/24247#issuecomment-1208387110) We said "$BOOT/loader/ is the directory containing all files needed for Type https://github.com/keszybz/systemd/pull/1 entries" which is blatantly wrong. >I really don't follow here? why do you say...

[Downstream bug and debugging on Fedora 36](https://bugzilla.redhat.com/show_bug.cgi?id=2082022#c18) >[22920.230910] systemd-homework[265152]: Ready to resize image size 885.3G → 175.1G, partition size 885.3G → 175.1G, file system size 885.3G → 175.0G. And as...

See also: https://lore.kernel.org/linux-btrfs/[email protected]/ The systemd-devel list was cc'd but most of the responses for the thread are in the btrfs list. The one above goes into some of the complexities...

See also: systemd/pull/18386 A shrink request 885G->175G suggests up to 175G of extent migration. A best performing consumer NVMe means up to 90s for the shrink operation, and for HDDs...

Oh I just saw this, I think it will at least support the plain squashfs + overlayfs case, and has been there since 2018, with commit 9d764847. https://github.com/livecd-tools/livecd-tools/blob/fb8aa0be327d38dee49884df9af9d85df1433423/tools/livecd-iso-to-disk.sh#L1232 So I...

Missed this comment from ~2 years ago > Also, they can be individually mounted via the "subvol=" mount option, and directories can't, right? Behind the scenes this is a bind...