THere is bcache tools in Debian Stretch and bcache module in bpo stretch kernel. There is nothing implemented in omv UI or backend to handle bcache.
This appears to be accurate, from what I can tell I set up bcache correctly in CLI and OMV even recognizes it. As soon as I try to mount it for a shared folder it crashes, though.
I tried LVM's caching feature before bcache because it seemed like it was more reliable and closer to business grade. OMV can mount the logical volumes set up in this program. Unfortuntately, actually performed worse while caching, than with a stand alone spinning disk. I could not get documents to promote into SSD. This blog appears to be correct regarding performance based on my own testing: Nikolaus Rath's Website.
I's a great addition if you rely on anachronistic RAID modes (eg. a RAID6) since such a RAID shows high sequential performance but sucks totally at random IO. This is where bcache can shine since it accelerates especially random writes.
This is exactly why I was also looking into OMV/bcache and how I found this thread. I am working on a cloud migration but my company works with very large files (including 4K video) and also super small files that need to be built into sprites. We still need a local server for the speed and upload caching (hybrid solution).
OMV seems more consumer-targeted but has all of the security features we should need. It also seems much easier to use than ClearOS which is marketed to businesses as a MS Server alternative.
It's so close to working with bcache... if I was a developer I might look under the hood and assess how much time it would take to resolve the situation. For any curious users that want to look at the stack trace:
- Error #0:
- exception 'OMV\Exception' with message 'Device '/dev/bcache01' is not available after a waiting period of 10 seconds.' in /usr/share/php/openmediavault/system/blockdevice.inc:486
- Stack trace:
- #0 /usr/share/openmediavault/engined/rpc/filesystemmgmt.inc(609): OMV\System\BlockDevice->waitForDevice(10)
- #1 /usr/share/php/openmediavault/rpc/serviceabstract.inc(528): OMVRpcServiceFileSystemMgmt->{closure}('/tmp/bgstatusIY...', '/tmp/bgoutputrj...')
- #2 /usr/share/openmediavault/engined/rpc/filesystemmgmt.inc(642): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure), NULL, Object(Closure))
- #3 [internal function]: OMVRpcServiceFileSystemMgmt->create(Array, Array)
- #4 /usr/share/php/openmediavault/rpc/serviceabstract.inc(124): call_user_func_array(Array, Array)
- #5 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('create', Array, Array)
- #6 /usr/sbin/omv-engined(536): OMV\Rpc\Rpc::call('FileSystemMgmt', 'create', Array, Array, 1)
- #7 {main}
I really wish this worked, a couple of us at the office were really excited to do a Linux file-server deployment... now we're a little less excited because we have to sell the value/benefits of very large SSD's to the decision makers, haha.