There is a dozen of cases where you want to just compress some folders in your system, but you don't want to compress whole device, would you create a subvolume for each of them? On Sat, Mar 21, 2015 at 7:25 PM, Petr Bena <benapetr@xxxxxxxxx> wrote: > Ok, but what if I am just a non-root user who want to transparently > compress some of their data? What if I am a root user who does just > want to compress some large folder transparently and doesn't want to > mess up with subvolumes? > > I know that from sysadmin point of view, there is no need for this, > but from regular user point of view, who have btrfs on their laptop, > this could make life easier. > > On Sat, Mar 21, 2015 at 7:22 PM, Roman Mamedov <rm@xxxxxxxxxxx> wrote: >> On Sat, 21 Mar 2015 18:56:12 +0100 >> Petr Bena <benapetr@xxxxxxxxx> wrote: >> >>> unlike NTFS, compressing files in btrfs is not so simple >> >> There shouldn't be any need to micro-manage compression on Btrfs on a >> per-folder or per-file basis. Just mount the whole volume as compress=[method] >> (but not compress-force), there shouldn't be any downside, on the contrary, >> with the current ratio of CPU core count and their performance to disk I/O >> speed, you are likely to even see a speed-up. Also files which are detected to >> be incompressible are automatically skipped from compression (at least that's >> what it tries to do by design). >> >> If you want higher performance and less fragmentation on certain files/folders, >> you are supposed to set them NOCOW, at which point the compression is also >> automatically disabled. >> >> -- >> With respect, >> Roman -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
