Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rsync: failed to set times ... Operation not permitted (1) #238

Open
dnacombo opened this issue Mar 31, 2022 · 1 comment
Open

rsync: failed to set times ... Operation not permitted (1) #238

dnacombo opened this issue Mar 31, 2022 · 1 comment

Comments

@dnacombo
Copy link

Describe the bug
Not sure it's a bug or a feature request.
I need to synch 2 folders on a nfs and local drive. The security restrictions are important on the nfs, so I don't have the ability to change the access time on the root directory I want to sync. This triggers the following error :

rsync: failed to set times on "/network/lustre/blah/DATAfolder/.": Operation not permitted (1)

My two questions are:

  • Is there any way I can turn off setting times on the target directory? or ideally just the root of the target directory?
  • Is there a chance that this time setting operation of the root directory is actually the last one performed by rsync, or triggers an exception that doesn't halt the execution, so I actually don't care too much...

To Reproduce
Run osync in an environment where times cannot be set on the root target directory.

Environment (please complete the following information):

  • Full osync version (including build): 2021062901
  • OS: Linux Mint 19.1 Cinnamon
  • Bitness x64
  • Shell (busybox or else) bash
@deajan
Copy link
Owner

deajan commented Apr 8, 2022

Sorry for the late reply.
Could you try to add --no-times to RSYNC_OPT_ARGS in config file ?
Be aware that synchroniation is time based, so ignoring access time is okay, mtime isn't.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants