<\/p>\n
I tested bcache<\/strong> about year ago on my spare\/backup server and it worked quite fine. But since then every newer kernel had new issues, even on mailing list there were suggestions that bcache<\/strong> should be marked back as experimental<\/em>. So, after some time I abandoned bcache<\/strong> and started to wait for something more stable and configuration friendly. In the same time dm-cache<\/strong> was also available, but it’s setup was quite challenging and dangerous (using dmsetup<\/em> and raw calculated numbers – very easy way to make a horrible mistake). There was also quite friendly way to manage dm-cache<\/strong> using LVM2<\/strong> tools, but only in plans \ud83d\ude42<\/p>\n Right now, LVM2<\/strong> have all promised featured for managing dm-cache<\/strong>, so I gave it a try \ud83d\ude42<\/p>\n Just to sum up my experience:<\/p>\n It’s time to get back to Slackware<\/strong>. Current version is 14.1, so everything described here is based on this version.<\/p>\n Stock 3.10.17 kernel is little too old for good dm-cache work, so I recommend to get something at least from 3.14 series. You could compile it yourself or grab from slackware-current tree<\/a> which have currently 3.14.33.<\/p>\n LVM2<\/strong> version shipped with Slackware 14.1 is almost last version without dm-cache<\/strong> support, so there is a need to grab latest version and compile it. For complete support you need also thin-provisioning-tools<\/strong> with fsck-like tools for dm-cache<\/strong>.<\/p>\n Just get my lvm2 package<\/a> and install it. You may also need mkinitrd patch (see above).<\/p>\n Start is easy and well documented in man lvmcache<\/strong>. <\/p>","protected":false},"excerpt":{"rendered":" bcache vs. dm-cache I tested bcache about year ago on my spare\/backup server and it worked quite fine. But since then every newer kernel had new issues, even on mailing list there were suggestions that bcache should be marked back …<\/span> Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6],"tags":[65],"_links":{"self":[{"href":"https:\/\/majek.sh\/en\/wp-json\/wp\/v2\/posts\/1600"}],"collection":[{"href":"https:\/\/majek.sh\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/majek.sh\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/majek.sh\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/majek.sh\/en\/wp-json\/wp\/v2\/comments?post=1600"}],"version-history":[{"count":36,"href":"https:\/\/majek.sh\/en\/wp-json\/wp\/v2\/posts\/1600\/revisions"}],"predecessor-version":[{"id":1632,"href":"https:\/\/majek.sh\/en\/wp-json\/wp\/v2\/posts\/1600\/revisions\/1632"}],"wp:attachment":[{"href":"https:\/\/majek.sh\/en\/wp-json\/wp\/v2\/media?parent=1600"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/majek.sh\/en\/wp-json\/wp\/v2\/categories?post=1600"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/majek.sh\/en\/wp-json\/wp\/v2\/tags?post=1600"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}\n
\n
\n
Requirements<\/h1>\n
Recent kernel<\/h2>\n
Recent LVM2<\/h2>\n
Hard way (compile everything yourself)<\/h3>\n
\n
\nPatch: slackware-mkinitrd-dm-cache.patch<\/a>.
\nApply:<\/p>\n
\npatch -p0 < \/somewhere\/slackware-mkinitrd-dm-cache.patch<\/div><\/div>\n<\/li>\nLazy way<\/h3>\n
Configuration<\/h1>\n
\nJust quick howto assuming that you have volume group named vg_group<\/strong>, your physical cache device (ssd) is \/dev\/sdb1<\/strong> and you want to cache volume named lv_home<\/strong>.<\/p>\n\n