A new and improved form of compression when using btrfs has made it into the btrfs-tools called "zstd".
Note: GRUB cannot read this form of compression as of yet so if your boot folder is in a btrfs file system compressed with zstd you will not be able to boot.
I discovered this as I was moving my subvolumes - which includes my @grub subvolume - to my new drive. I had mounted it with ZSTD compression instead of my usual LZO. This rendered my new device unbootable immediately. Digging into the grub console and I discovered an error about "0x3" no readable and that turned out to mean the compression type I had used.
I was able to recover by booting to my older SSD that was still using LZO and mounting the new file system with LZO, then copying the files in @grub to a new subvolume and doing the same with the boot folder of @KDEneon. Right now I'm posting from my new drive and it's new btrfs filesystem.
Until this is addressed (the developers are aware), only use ZSTD on non-booting file systems.
That is all. As you were...
Note: GRUB cannot read this form of compression as of yet so if your boot folder is in a btrfs file system compressed with zstd you will not be able to boot.
I discovered this as I was moving my subvolumes - which includes my @grub subvolume - to my new drive. I had mounted it with ZSTD compression instead of my usual LZO. This rendered my new device unbootable immediately. Digging into the grub console and I discovered an error about "0x3" no readable and that turned out to mean the compression type I had used.
I was able to recover by booting to my older SSD that was still using LZO and mounting the new file system with LZO, then copying the files in @grub to a new subvolume and doing the same with the boot folder of @KDEneon. Right now I'm posting from my new drive and it's new btrfs filesystem.
Until this is addressed (the developers are aware), only use ZSTD on non-booting file systems.
That is all. As you were...
Comment