To backup the data files on a Windows Server, in OMV 2.2.6, I created a series of remote shares using the remote share plugin.
As part of each remote share, I created a directory on the boot flash card that appeared to operate as a pass-through symlink. (It's pretty obvious that the actual contents of the all the remote shares were not resident on an 8GB card.)
In this scenario, under <Storage>, <Filesystems> and in fstab, all I see are locally connected drives and their partitions.
_______________________________________________________________________
To do the same thing in 3.0.68 Erasmus, I have locally connected drives and partitions in <Storage>, <Filesystems>. That's to be expected. However, all remote mounts defined in the remote mount plugin also appear as local file systems with stat's in <Storage>, <File Systems> and are defined in fstab. Adding to that, all the remote mounts appear as individual disks under <System Information>, <Disk usage>.
This, in itself, is not a problem. However, I tried to unmount a real local, unreferenced and unused data drive. Since all the remote mounts seem to be refreshing on a continual basis (there are nine of them) the <unmount> button for the data drive in <Storage>, <File Systems> is greyed out most of the time. When it becomes available for a few seconds, I clicked on it and got an error message. The drive wouldn't unmount.
Finally, I physically disconnect it and rebooted. At that point, it was no longer mounted, but it showed up as "missing". I deleted it in <Storage>, <File Systems> and, while the dialog box returns no errors, it didn't go away. I even removed the drive's definition in /etc/fstab, rebooted, and it still shows up as "missing" in the GUI. This is more of a curiosity thing to me, that's not really important, but it would be nice to be able to purge an unreferenced, wiped, missing drive.
Also having several remote mounts appear as if they're local file systems, constantly updating with statistic's, doesn't seem to be ideal. OMV 2.0's remote share seemed to be a more elegant solution. (On the other hand, this is just an opinion based on my very narrow use of the two plug-in's.)
Thanks