Do I need to install lzo package to use lzo compression on a btrfs partition? Can I somehow check if compression is working?
Last edited by miro279 (2013-01-13 09:57:17)
This is done in the kernel, so you don't need to install any package. Last I tried to test the compression there was no simple way (but you could try to deduce it from total space usage etc.)
The funny thing is, that df gives me weird output after changing to btrfs with lzo:
/dev/sda4 133169152 84898324 5433128 94% /home
If I recalculate that should be a reading of about 64% usage, not 94%. And I think 64% was about the value I had before chaning to btrfs (from ext4) so I was kind of doubtful about the compression..
kde behaves the same way, if I click home propertys it tells me I have 136,4GB for the partition, 88,0GB are used and 5,6GB are free with is a usage of 96%.. Is the btrfs metadate that big?
Don't use df on btrfs partitions, use 'btrfs filesystem df' instead. I think this is covered on our wiki, but if not, it's on the official btrfs wiki (along with information on how to understand it's output).
The amount of space your metadata takes up is unique, if you have lots of tiny files, you'll have more metadata than, say, if you had half a dozen huge files.
Mobo: ASUS P8Z77-V PRO // Processor: Intel Core i7-3770K 3.4GHz // GFX: nVidia GeForce GTX 970 Ti // RAM: 32GB (4x 8GB) Corsair DDR3 (@ 2133MHz) // Storage: 1x 3TB Seagate SATAII 5x 1TB Samsung SATAII, 2x 120GB Corsair SSD
Making lemonade from lemons since 2015.
it's not on the arch wiki, but I found it here: https://btrfs.wiki.kernel.org/index.php … licated.3F
I'm running btrfs filesystem balance /home/ at the moment..
thanks for your help. after all it seems that btrfs has some way to cover before it feels realy ready for normal use (also the fsck problem).
just for info: df reading after balance:
/dev/sda4 133169152 84865124 45292344 66% /home