You are not logged in.
Does systemd-boot support booting from a compressed root subvolume? On the wiki page the following is stated:
If booting a btrfs subvolume as root, amend the options line with rootflags=subvol=<root subvolume>. In the example below, root has been mounted as a btrfs subvolume called 'ROOT'
$esp/loader/entries/arch-btrfs-subvol.conf title Arch Linux linux /vmlinuz-linux initrd /initramfs-linux.img options root=PARTUUID=14420948-2cea-4de7-b042-40f67c618660 rw rootflags=subvol=ROOT
However, no information on whether this works in case of compression is provided.
Consider the following installation procedure:
mkfs.btrfs /dev/sdaX
mount /dev/sdaX /mnt
btrfs subvolume create /mnt/root
umount /mnt
mount -o relatime,ssd,compress=lzo,space_cache,subvol=root /dev/sdaX /mnt
btrfs subvolume create /mnt/home
btrfs subvolume create /mnt/usr
btrfs subvolume create /mnt/var
mkdir /mnt/boot
mount $esp /mnt/boot
...
move on, pacstrap, genfstab, e.t.c.
...
bootctl install
...
Append "rootflags=subvol=root" to "options" in "$esp/loader/entries/arch-entry.conf"
...
finish up, networking, passwd, e.t.c.Would this work?
Last edited by robg (2016-03-03 18:02:02)
Offline
Confirmation: It works according to the outline in the initial post.
Offline
Follow-Up Remark: I'd like to add my findings to the wiki but before doing so: Is this piece of information actually worth adding or is there any obvious reason it should work that I missed in the first place?
Offline
When I installed, it didn't even cross my mind that there might be a problem.
What I worried about was to make sure that the files of the base packages put onto the volume are also compressed, not just the later packages you install after restarting into the system that has the flags in /etc/fstab.
Offline
You can, of course, mention it on the wiki page. You can also discuss this on the wiki first, every page has a discussion page.
Offline