Hi People,
I have a bit of a strange one I'm not sure how to track down - or what I did to create the problem in the first place for that matter.
I use a Task Scheduler rsync job to back up my Photostation shared folder to a secondary Synology. The statement reads;
In this way should the primary ever drop out, I can basically, manually failover to the secondary with minimal fuss + I have a backup. This setup has run successfully for years, previously.
I know that shared folder perms are controlled by - and within the PhotoStation app rather than Control Panel. You _can_ of course, play with the folder perms in both the DSM file manager and in ssh. I admit to sometime - somewhere in the not _too_ distant past playing with perms in either or both of the above (file mgr and ssh). But, at this point, I am stuffed if I can recall what I did. Either way, I have now ended up with the following scenario.
When the above code runs - from the Task Scheduler, I see the following results;
admin@PrimaryNAS:/volume1/photo$ ll
total 0
drwxrwxrwx+ 1 PhotoStation PhotoStation 118 Dec 20 20:34 .
drwxr-xr-x 1 root root 1344 Dec 21 05:05 ..
drwxrwxrwx+ 1 sync fotos 570 Dec 15 20:33 Baron
drwxrwxrwx+ 1 root root 174 Dec 15 06:28 @eaDir
drwxrwxrwx+ 1 sync fotos 1210 Dec 20 20:34 Kraft
drwxrwxrwx+ 1 sync fotos 1362 Dec 20 20:34 Misc
drwxrwxrwx+ 1 root root 0 Jul 15 16:02 #recycle
drwxrwxrwx+ 1 sync fotos 208 Nov 27 22:47 Romeo
drwxrwsrwt 1 baker users 22 Jun 20 2019 .TemporaryItems
drwxrwxrwx+ 1 sync fotos 108 Jun 4 2020 To Be Sorted
admin@BackupNAS:/volume1/photo$ ll
total 60
drwxrwxrwx 8 root root 4096 Dec 21 09:57 .
drwxr-xr-x 39 root root 4096 Dec 21 00:00 ..
d--------- 42 sync fotos 4096 Dec 15 20:33 Baron
d--------- 29 sync fotos 4096 Dec 20 20:34 Kraft
drwxrwx--- 31 sync fotos 4096 Dec 20 20:34 Misc
drwxrwxrwx 2 root root 4096 Dec 10 2017 #recycle
drwxrwx--- 23 sync fotos 4096 Nov 27 22:47 Romeo
drwxrwx--- 12 sync fotos 4096 Jun 4 2020 To Be Sorted
It seems ALL perms are getting removed on dirs "Baron" and "Kraft" with the consequent result, that every cmd attempting to execute on those 2 dirs fails with "Permission Denied". Even IF I manually reset the appropriate dir perms on both Baron and Kraft on the BackupNAS first and then re-run the Task Scheduler job from the Primary, the end result is what you see above.
Can anyone shed some light pls on what I may have done to be causing this?
I have a bit of a strange one I'm not sure how to track down - or what I did to create the problem in the first place for that matter.
I use a Task Scheduler rsync job to back up my Photostation shared folder to a secondary Synology. The statement reads;
/usr/bin/rsync -a --exclude='@eaDir' --exclude='#recycle' --exclude='.TemporaryItems' /volume1/photo/ sync@BackupNAS:/volume1/photoIn this way should the primary ever drop out, I can basically, manually failover to the secondary with minimal fuss + I have a backup. This setup has run successfully for years, previously.
I know that shared folder perms are controlled by - and within the PhotoStation app rather than Control Panel. You _can_ of course, play with the folder perms in both the DSM file manager and in ssh. I admit to sometime - somewhere in the not _too_ distant past playing with perms in either or both of the above (file mgr and ssh). But, at this point, I am stuffed if I can recall what I did. Either way, I have now ended up with the following scenario.
When the above code runs - from the Task Scheduler, I see the following results;
admin@PrimaryNAS:/volume1/photo$ ll
total 0
drwxrwxrwx+ 1 PhotoStation PhotoStation 118 Dec 20 20:34 .
drwxr-xr-x 1 root root 1344 Dec 21 05:05 ..
drwxrwxrwx+ 1 sync fotos 570 Dec 15 20:33 Baron
drwxrwxrwx+ 1 root root 174 Dec 15 06:28 @eaDir
drwxrwxrwx+ 1 sync fotos 1210 Dec 20 20:34 Kraft
drwxrwxrwx+ 1 sync fotos 1362 Dec 20 20:34 Misc
drwxrwxrwx+ 1 root root 0 Jul 15 16:02 #recycle
drwxrwxrwx+ 1 sync fotos 208 Nov 27 22:47 Romeo
drwxrwsrwt 1 baker users 22 Jun 20 2019 .TemporaryItems
drwxrwxrwx+ 1 sync fotos 108 Jun 4 2020 To Be Sorted
admin@BackupNAS:/volume1/photo$ ll
total 60
drwxrwxrwx 8 root root 4096 Dec 21 09:57 .
drwxr-xr-x 39 root root 4096 Dec 21 00:00 ..
d--------- 42 sync fotos 4096 Dec 15 20:33 Baron
d--------- 29 sync fotos 4096 Dec 20 20:34 Kraft
drwxrwx--- 31 sync fotos 4096 Dec 20 20:34 Misc
drwxrwxrwx 2 root root 4096 Dec 10 2017 #recycle
drwxrwx--- 23 sync fotos 4096 Nov 27 22:47 Romeo
drwxrwx--- 12 sync fotos 4096 Jun 4 2020 To Be Sorted
It seems ALL perms are getting removed on dirs "Baron" and "Kraft" with the consequent result, that every cmd attempting to execute on those 2 dirs fails with "Permission Denied". Even IF I manually reset the appropriate dir perms on both Baron and Kraft on the BackupNAS first and then re-run the Task Scheduler job from the Primary, the end result is what you see above.
Can anyone shed some light pls on what I may have done to be causing this?
