On Tue, Oct 28, 2025, at 2:00 AM, Samuel Sieb wrote:
> https://btrfs.readthedocs.io/en/latest/Compression.html#how-to-enable-compression > > Typically the compression can be enabled on the whole filesystem, > specified for the mount point. Note that the compression mount options > are shared among all mounts of the same filesystem, either bind mounts > or subvolume mounts. > > I don't know why they added the "typically", but it is clear that it > applies to all the mounted subvolumes. Typically might be a carve out for file attribute m and C? There is also `btrfs property` which is gnarly in that I don't know to what degree the properties are honored by the kernel. Like you could set one file to be compression none, another file to be compression lzo, another file would be zstd compression level 9, and so on. However, just because the property is set in metadata doesn't mean the btrfs kernel code will honor that property. Sure it *should* but does it? *shrug* It's possible some are and some aren't. -- Chris Murphy -- _______________________________________________ users mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
