greg-weber
commented
3 years ago I was very tired when looking at this. I didn't really say how much I appreciated the work. I really liked the polish. The fonts and the codecs made the office documents and multimedia instantly usable. I wanted to duplicate it and definitely studied you files things like how you setup the repos with priorities. The less recommended packages seem to make things quite slim and fit. Before you switched to btrfs as the default I had tried Gecko and took many ideas.
If my report turns out to be poo, at least I need to say thanks.
geckolinux
I may be mistaken in my research of this. I hope this is useful. It seems zstd is enabled and /boot was on btrfs without compression being turned off for /boot. System failed after updates where files needed in /boot were not available to grub due to zstd compression being used in new files.
GeckoLinux_ROLLING_Plasma.x86_64-999.210519.0.iso was installed in Virtual-box to test an openSUSE type install with less setup. Virtual machine was rebooted.
Checked the command to update tumbleweed/gecko rolling. zypper dup was completed. I restarted the GeckoLinux Rolling. The Grub configfile didn't load, although grub itself seemed to be in normal mode. Attempting to load the grub configfile wouldn't present grub in menu mode like normal. Attempting to cat the grub configfile revealed an error. Grub error typed out here manually with photo of /etc/fstab and grub error.
grub> cat (hd0,msdos1)/@/.snapshots/1/snapshot/boot/grub2/grub.cfg error: ../../grub-core/fs/btrfs.c:1667:compression type 0x3 not supported.
Searching for the error lead to type 0x3 seeming to refer to zstd compression not being supported by grub.
This is where I start to have doubts as while Gecko or perhaps tumbleweed seems to have an issue with this, I know that I'm running grub on btrfs with zstd. I have grub and boot on the btrfs / subvolume with zstd compression enabled. This is on my main laptop with Ubuntu 20.04 LTS having manually setup a partition with luks, btrfs, @ and @home subvolumes, and grub-btrfs-apt-timeshift snapshot integration. When setting it up I chose zstd compression for the workstation and it works no problem. I'm reporting this still as 6 days ago there was a poll for the default filesystem. There is even mention of zstd on btrfs and it seems there is some issue with it. I have my doubt as 1200 downloads later and I don't see a bug report so maybe it is just me ha.
Searched around a bit more and found openSUSE may have disabled zstd. I recall adjusting my partition table for extra space in case grub was a bit big and left some space after master boot record and didn't install to grub to partition.
openSUSE disabled zstd. https://build.opensuse.org/package/view_file/openSUSE:Factory/grub2/0001-btrfs-disable-zstd-support-for-i386-pc.patch?expand=1
I've left the virtual machine intact for now and am making a fresh virtual machine to further test.
Perhaps of note but I expect not to have contributed
(A functional install of openSUSE Leap 15.2 was on virtual hard disk and overwritten with the 3rd option of the 4 available - Phrasing was sort of on the lines of use the space from this prior installation. The subvolumes from Leap are no longer present as expected.)
(A snapshot was attempted from yast in fresh installation. Yast reported an error that there was no snapper config. snapper config was created for root. A snapshot was taken to confirm snapshots were working. I had not used snapper before. 4 more snapshots were created by the zypper dup)