On Mon, Sep 18, 2017 at 1:56 PM, Timofey Titovets <nefelim4ag@xxxxxxxxx> wrote: > 2017-09-18 10:36 GMT+03:00 shally verma <shallyvermacavium@xxxxxxxxx>: >> Hi >> >> I wanted to test btrfs compression using fio command but somehow >> during fio writes, I don't see code taking route of compression blocks >> where as If I do a copy to btrfs compression enabled mount point then >> I can easily see code falling through compression.c. >> >> Here's how I do my setup >> >> 1. mkfs.btrfs /dev/sdb1 >> 2. mount -t btrfs -o compress=zlib,compress-force /dev/sdb1 /mnt >> 3. cp <some large test file> /mnt >> 4. dmesg shows print staments from compression.c and zlib.c confirming >> compression routine was invoked during write >> 5. now, copy back from btrfs mount point to home directory also shows >> decompress call invokation >> >> Now, try same with fio commands: >> >> fio command >> >> fio --directory=/mnt/ --numjobs=1 --direct=0 --buffered=1 >> --ioengine=libaio --group_reporting --bs=64k --rw=write --iodepth=128 >> --name=test --size=10G --runtime=180 --time_based >> >> But it seems to write uncompressed data. >> >> Any help here? what's missing? >> >> Thanks >> Shally >> -- >> 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 > > 1. mount -t btrfs -o compress=zlib,compress-force -> compress-force=zlib > 2. Tune fio to generate compressible data > How do I "tune" fio to generate data. I had assumed once compression is enabled on btrfs any system fwrite call will simply compress data into it .Isn't it so? Can you share fio command that I can test? Thanks Shally > > -- > Have a nice day, > Timofey. -- 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
