Hi James, James Abernathy <jfabernathy@gmail.com> writes: > I reran an install but this time when I remounted the @ and @home > subvolumes I only used the default, compress=zstd, and subvol= options. > Thank you. > This time it worked. After booting successfully, I edited fstab to add in > noatime and it still worked. At this point. it still could be the discard > or ssd options. > noatime is safe, and recommended, as noted in our wiki. compress=zstd is considered to be safe by many people--including Fedora. They're using "compress=zstd:1", and with different mount option than you're using. If "widely-tested" is an objective, then it may be worth keeping an eye on what config they use, and not introducing additional options that trigger corner cases. "ssd" see the Debian btrfs wiki on this topic (tldr: it's not necessary). > I'd look at what has changed in this area since Debian 11. Since Debian 11 (bullseye), space_cache v2 became the new btrfs-progs default, activated when a device is formatted, so it should be obvious why attempting to force space_cache v1 is wrong. At the same time, when upgrading from bullseye to bookworm, a volume made with space_cache v1 will still work (ie upgrades won't break), even with that mount option, because conversion to v2 does not yet happen automatically. discard=async isn't ready to use yet imho. Here is some upstream reading material on the topic: One year ago: https://www.spinics.net/lists/linux-btrfs/msg126838.html Last month: https://www.spinics.net/lists/linux-btrfs/msg133128.html Maybe it will be ready for linux-6.3? I don't know if the future fixes will be backported to 6.1, so I'm inclined to continue to advise against the use of discard=async for bullseye. Regards, Nicholas
Attachment:
signature.asc
Description: PGP signature