Hi,
while 4.14 is still fresh, let me address some concerns I've seen on linux
forums already.
The newly added ZSTD support is a feature that has broader impact than
just the runtime compression. The btrfs-progs understand filesystem with
ZSTD since 4.13. The remaining key part is the bootloader.
Up to now, there are no bootloaders supporting ZSTD. This could lead to an
unmountable filesystem if the critical files under /boot get accidentally
or intentionally compressed by ZSTD.
There are several ways how to get around that:
- separate boot partition, no zstd there
- reset potential compression of /boot/* files to something supported, eg.
$ btrfs filesystem defrag -r -czlib /boot/*
or
$ btrfs filesystem defrag -r -clzo /boot/*
To see if there are zstd files:
$ find /boot -print -exec sudo btrfs prop get '{}' compression \; | grep -B1
zstd
There might be other workarounds but I want to keep the advice simple.
d.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
