Forum Discussion

Aspirant

Dec 12, 2019

ReadyNAS OS Rsync job permissions incorrect

We've set up a DR Rsync job to copy data on NAS1 to NAS2. We'd like to have the job running weekly but when the job runs, it copies the data but creates a completely bizzare (and very incorrect) set of NTFS permissions on the NAS2 side. The set of permissions is the same whatever we set as the source; from an entire share to a single folder. The permissions set does not match what is set on NAS1 (source) or the NTFS permissions set on the source(s).

It seems to be a problem with the Rsync job itself or the ReadyNAS OS (6.10.2). Windows copy completes as expected and I've tried using SyncBack to run the job and this also copies correctly.

Has anyone else come across such a bizzare problem or have any insight?

Thanks in advance.

20 Replies

Replies have been turned off for this discussion

StephenB
Guru - Experienced User
Dec 12, 2019
Of course there are no NTFS permissions involved (since the NAS doesn't use the NTFS file system).

Have you looked at the btrfs file permissions with ssh?
- DCA-IT
  Aspirant
  Dec 12, 2019
  Hi Stephen, thanks for your response.
  
  What are the permissions I'm seeing when I browse to the shared folder (or any of the sub-folders) in Windows Explorer and view Properties > Security > Advanced? These don't match anything I can see when I connect to the NAS via the web console and look at the permissions set there in Network Access or File Access.
  
  I cannot seem to connect to the NAS using SSH. When I enter the credentials in Putty, the window simply vanishes. SSH is deinately enabled on the NAS though...
- DCA-IT
  Aspirant
  Dec 12, 2019
  I've managed to connect Putty using SSH now. What commands would I use to view the permissions?
  - DCA-IT
    Aspirant
    Dec 12, 2019
    I'm trying the command below to browse to the directory I want to check permissions on but when I enter the path, I get an error saying "No such file or directory exists".
    cd /<share name>/
    The directory does very much exist. I can browse to it and open files. For some reason, the command line will not see it.