I use an external HDDs connected directly to my OMV using USB3 to copy files in and out of my OMV. These external HDDs are usually formatted with NTFS or HFS. I'm getting much faster write/read speeds than copying over wifi or even gigabit Ethernet.
I found out that with UFSD I get much better write speeds than with mount.ntfs . In addition, CPU utilization is substantially reduced. These are some benchmark tests I did:
Read : 77.4 MB/s with CPU utilization : ~22%
Write : 39.9 MB/s with CPU utilization : ~72%
*the CPU utilization mentioned above were taken by mount.ntfs process
Read : 79.9 MB/s with added CPU utilization : 0%
Write : 81.7 MB/s with added CPU utilization : 0%
As you can see, write speed is dramatically enhanced, as read speed is almost the same. In addition, a lot of CPU cycles are saved for both read and write, with huge save in write scenario.
Furthermore, with ufsd you can have ACL which isn't possible in mount.ntfs.
I'm testing with purchased Pro version of "Paragon NTFS & HFS+ for Linux" to get some extra features and utilities, but they have a community Express version free to download with a working drivers (kernel module).
The issue I have now, is that once I mount the drive manually from command line, I won't be able to add it as shared folder. So I was thinking that it's might be due to the limitation once fixed and mentioned by @votdev :
The regression is fixed in openmediavault 3.0.38, see https://github.com/openmediava…231f45a89fd2bd36e4ef0f95c.
so maybe just "ufsd" is needed to be added like "Fuseblk" was added?