Hello,
I have been working on setting up a system that utilizes Resilio Sync and SAMBA to backup and access my files.
The Problem: Files added via SAMBA, via the rslsync jail user, or by the FreeNAS root user in a folder don't propagate via Resilio Sync. Only files added on my Windows clients with Resilio can add files and have them sync.
I did not realize this at first because usually the files are only added, edited, etc from Windows Clients.
Background:
FreeNAS server /w Resilio Jail created using the plugin.
Several datasets that are UNIX and mounted in the Resilio Jail.
Several datasets that are Windows and shared with SAMBA.
A single dataset "shares" that is Windows and is mounted in the Resilio Jail.
Windows 10 client that can access all SAMBA shares and has Resilio installed with permission in all folders.
All datasets are owned by user nobody group "name of dataset" and my user account for SAMBA and the user rslsync in both the Jail and in FreeNAS is part of all groups they need access to.
The problem came up attempting to move files from one SAMBA share to the samba share into the resilio folder
I created a test folder /shares/vb/test and created 4 files.
One on my Windows machine in the Sync folder.
One on my Windows machine directly in the folder using the samba share.
One using the root account on FreenNAS directly;
And one using the rslsync in the jail.
The only file that syncs back to the windows machine or any other computers that are part of the sync folder is the one that originates on the Windows machine and is placed in the sync folder. Placing the file directly in the folder via the Jail user rslsync, the root account, or the SAMBA share does not work.
As you can see all files have the same permission, same group, but different owners. rslsync is part of the "shares" group on both the FreeNAS machine and the FreeNAS jail, and the windows SAMBA user "bryan" is part of "shares" as well. How come they don't get noticed by FreeNAS and sync?
Any help is appreciated. Thank you.
I have been working on setting up a system that utilizes Resilio Sync and SAMBA to backup and access my files.
The Problem: Files added via SAMBA, via the rslsync jail user, or by the FreeNAS root user in a folder don't propagate via Resilio Sync. Only files added on my Windows clients with Resilio can add files and have them sync.
I did not realize this at first because usually the files are only added, edited, etc from Windows Clients.
Background:
FreeNAS server /w Resilio Jail created using the plugin.
Several datasets that are UNIX and mounted in the Resilio Jail.
Several datasets that are Windows and shared with SAMBA.
A single dataset "shares" that is Windows and is mounted in the Resilio Jail.
Windows 10 client that can access all SAMBA shares and has Resilio installed with permission in all folders.
All datasets are owned by user nobody group "name of dataset" and my user account for SAMBA and the user rslsync in both the Jail and in FreeNAS is part of all groups they need access to.
The problem came up attempting to move files from one SAMBA share to the samba share into the resilio folder
/shares/vb
using my Windows "e6520" computer. The files did not sync to my e6520 machine.I created a test folder /shares/vb/test and created 4 files.
One on my Windows machine in the Sync folder.
orig-from-e6520-via-resilio.txt
One on my Windows machine directly in the folder using the samba share.
orig-from-e6520-via-samba-share.txt
One using the root account on FreenNAS directly;
orig-from-trusty-root.txt
And one using the rslsync in the jail.
orig-from-trusty-rslsync.txt
The only file that syncs back to the windows machine or any other computers that are part of the sync folder is the one that originates on the Windows machine and is placed in the sync folder. Placing the file directly in the folder via the Jail user rslsync, the root account, or the SAMBA share does not work.
As you can see all files have the same permission, same group, but different owners. rslsync is part of the "shares" group on both the FreeNAS machine and the FreeNAS jail, and the windows SAMBA user "bryan" is part of "shares" as well. How come they don't get noticed by FreeNAS and sync?
Code:
root@Trusty[/mnt/tank1/ds1/shares/vb/test]# ls -al total 43 drwxrwx---+ 2 rslsync shares 6 Jan 26 11:14 . drwxrwx---+ 22 nobody shares 34 Jan 26 11:10 .. -rwxrwx---+ 1 rslsync shares 0 Jan 26 11:10 orig-from-e6520-via-resilio.txt -rwxrwx---+ 1 bryan shares 0 Jan 26 11:11 orig-from-e6520-via-samba-share.txt -rwxrwx---+ 1 root shares 2 Jan 26 11:13 orig-from-trusty-root.txt -rwxrwx---+ 1 root shares 2 Jan 26 11:14 orig-from-trusty-rslsync.txt
Any help is appreciated. Thank you.