Permission errors on files without write permissions #629
Comments
|
Is the destination filesystem local or on some kind of NAS? Are directory permissions okay, do they allow access? |
|
No its a remote system mounted by NFS. The directory permissions do allow writing by the user account running the rsync job. I do notice a lot of interruptions to the connection to the remote destination in /var/log/messages. But shouldn't the temp file still be there if it couldn't be re-named because the permissions changed to 544 before the network interruption? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
rsync version 3.1.2 protocol version 31 CentOS 7.9.2009
rsync is producing Permission errors at the destination for files with 544 permissions:
/panzura/MiSeq/230929_M06717_0137_000000000-KYLRM/Thumbnail_Images/L001/C54.1/s_1_2117_c.jpg
does exist
/panzura/MiSeq/230929_M06717_0137_000000000KYLRM/Thumbnail_Images/L001/C533.1/.s_1_1104_t.jpg.5dffqa
does not. On the source side there is a file with a related name:
so the file on the destination side seems to be a temporary file created by rsync in the process of synchronizing the directory tree.
The common thread of these two errors seems to be the 544 permissions meaning the user running the rsync process does not have write permissions on the file. However, many other similiar files were synchronized to the destination without error.
I have not been able to find any known bug in rsync that would account for this.
We are unable to update the rsync version since CentOS is no longer being supported and there doesn't seem to be a package for later versions than 3.1.2 for that OS.
The text was updated successfully, but these errors were encountered: