On Tue, Oct 18, 2016 at 02:51:11PM +0200, Marcin Mirosław wrote: > W dniu 18.10.2016 o 14:45, Kent Overstreet pisze: > > The issue is that right now btree node coalescing is only run as a batch pass > > when mark and sweep GC runs (it has nothing to do with GC, it just runs at the > > same time in the current code). At some point we need to come up with a good way > > of triggering it as needed. > > > > Try triggering a gc, and then check mount time: > > > > echo 1 > /sys/fs/bcache/<uuid>/internal/trigger_gc > > No change: > [ 8417.101640] bcache (dm-12): starting mark and sweep: > [ 8433.795575] bcache (dm-12): mark and sweep done > [ 8433.795842] bcache (dm-12): starting journal replay: > [ 8433.796064] bcache (dm-12): journal replay done, 129 keys in 90 > entries, seq 28581 > [ 8433.796075] bcache (dm-12): journal replay done > [ 8433.796076] bcache (dm-12): starting fs gc: > [ 8433.799493] bcache (dm-12): fs gc done > [ 8433.799495] bcache (dm-12): starting fsck: > [ 8433.800613] bcache (dm-12): fsck done > > > /dev/mapper/system10-bcache 9,8G 421M 9,4G 5% /mnt/test well that's odd. I'll work on getting some more information out of coalescing tomorrow. -- To unsubscribe from this list: send the line "unsubscribe linux-bcache" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
