kelinger
commented
9 months ago Yes, like you, I migrated to a local NAS (Synology in my case). I also found that NFS was more complicated than it should be. For one, Rclone doesn't natively support NFS (which would have been the ultimate solution). I mounted the NFS share to the host running OmniStream and then used aliases and local definitions but this really made OmniStream more unwieldy. This also meant that I would have to make a lot of changes to OmniStream and the menus to truly support this. Docker also doesn't work well (in my opinion) with volumes that come from other mounts as Docker ends up passing the empty folder that was created FOR the mount, not the mount itself. I had to get around this with OmniMount but that required using some Docker magic.
So, to make sure this doesn't become a huge response, the short answer is: i got it working with OmniStream using SMB instead of NFS.
If your media is shared as SMB as well as NFS, you can create two entries in your Rclone config like I did:
[SynologySMB]
type = smb
host = 192.168.1.21
user = kelinger
pass = <removed>
idle_timeout = 0s
[OmniSynology]
type = alias
remote = SynologySMB:OmniStreamThe "SynologySMB" entry defines the connection to the NAS while the "OmniSynology" alias is what I'm configuring in OmniStream as my remote. Note that the line remote = SynologySMB:OmniStream tells Rclone to use that SMB connection to the Synology and the name of the share on Synology is "OmniStream" (since you likely have other things shared on your NAS).
This got me up and running and allowed OmniStream to function the same as the cloud (Google) storage option. Of course, it was faster.
Unfortunately, this had one side effect: updates that occur outside of the mount (such as if you add or change files outside of OmniStream or the TurboSync process itself, which is kind of essential to the whole setup) they aren't reflected back to the mount for up to 96 hours. Google sent us a notification when changes occurred; SMB did not. So, the one last thing you need to do is add this line to vfs.conf inside the "omnimount" config directory:
DIRCACHE=10s
This will override the default setting.
Now, even better news: I'm about 90% complete with a new OmniMount that will natively support NFS. The changes to OmniStream are finished and already posted and there are three new variables added to the OmniStream configs that manage this process. What will happen is that it will override the mount process so that it is mounted using native Linux NFS instead of Rclone but then it still uses the overlay process for managing the downloads and changes with a delayed sync back to the NAS every 15 minutes (like it is today with Google or whomever else you may have used).
These variables don't do anything yet on the published versions of OmniStream and OmniMount but the actual process is in a testing phase right now. This means I should be able to release it in the next couple days.
mahogl
Since google killed the unlimited storage plan, i have now moved my media library to a local NAS solution running Truenas Scale. But i have been so happy with OmniStream that would love to continue to use it locally.
I have installed at Debian linux machine that would be hosting Omnistream, but i have run into a problem when i try to mount my nfs share into the rclone.
rclone.conf [glocal] type = alias remote = /data/solsky/
plexsus@roger:/data/solsky$ df -h 192.168.1.100:/mnt/tank/data/solsky 72T 40T 32T 56% /data/solsky /data/solsky 16E 0 16E 0% /home/plexsus/OmniStream/mnt/glocal uploadcache:unsynced:glocal 1.1P 61G 1.1P 1% /home/plexsus/OmniStream/mnt/cloud
plexsus@roger:/data/solsky$ rclone lsd glocal: -1 2023-09-18 20:38:59 -1 media
But the folder "/home/plexsus/OmniStream/mnt/glocal" is for some reason empty, but if i look in the local mount "/data/solsky" i see the media folder. And also in omni menu when i configure rclone and media directory it does find the directory.
What i think is the problem is some kind of permission issue, i have changed the user "plexsus" uid/grp to 3000 to match what i have configured in Truenas. and on the local mount i can read/write files without problem.
From what i read in another case you have migrated to a local NAS aswell @kelinger, so when you have the time i would realy apricate if you could share some of your experience on how to move from cloud storage to local storage with Omnistream. I think that would help alot other user also, since many are moving from cloud to local storage at the moment.
Thanks again for the excellent work you do with Omnistream
Best Regards, Marius