I used the same steps to verify it and can conconfirm it's succeeded fio --name=test1 --filename /dev/bcache0 --direct 1 --rw=randrw --bs=32k,4k --ioengine=libaio --iodepth=1
Then I monitoring the cache_available_percent and writeback rate. I no longer see the cache_available_percent dropped to 30 and writeback rate stucked at 4k. I can see the rate got accelerated while the dirty buckets hit the writeback_rate_*_fp_term, which is expected ** Tags removed: verification-needed-groovy ** Tags added: verification-done-groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900438 Title: Bcache bypasse writeback on caching device with fragmentation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1900438/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs