I was bored a couple days ago and decided to build my very first NAS (probably the first mistake right then and there lol)
Anyway, I ended up installing OMV with a couple of newly purchase EXOS 6TBs (was on sale and considerably cheaper than Ironwolf of similar capacity; authenticity checks out :). The installation went OK and I set up the unionfs along with a few shared folders on SMB and started copying my repo's over through LAN; all fine and dandy.
Next, I have a seedbox hosted externally. Somethings are downloaded now and then and I'd like to grab whatever that's downloaded on that remote seedbox to my shiny OMV. I checked the web GUI to see what's available in the arsenal that can accomplish that. After browsing through some documentations, I find rsync among other things. So I set up an rsync job and did a test run - ALL OK, it was able to grab that was in the remote "downloaded" folder to my local folder.
Then I discovered a problem. The local folder that rsync points to as destination folder (let's call it @Seedbox) can no longer be modified when browsing via SMB. I tried to copy a new folder to @Seedbox and couldn't even find the "Paste" option. I then tried to 'touch' a testfile by logging in as root on SSH in @Seedbox folder. That works and testfile appears on SMB - but cannot be modified (rename, delete, etc.).
So I did some test:
- Add a new Shared Folder (let's call it @NewFolder)
- Add @NewFolder to SMB shares
- @NewFolder appears on SMB on my mac - can be fully modified
- Create a new rsync job that uses @NewFolder as destination folder - @NewFolder can still be modified over SMB
- Do a test run of the new rsync job --- this is what breaks @NewFolder over SMB
So my question is:
1. Is the destination folder of rsync supposed to be like this?
2. In a broader sense, is rsync even the right tool to accomplish this job?
Sorry for my rambling. And thank you for your time (and patience)