We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
10.0.22000.1219; Invalid command line option: --version
4.19.104
22.04
Using an encrypted harddrive mounted with Veracrypt 1.25.9. And rsync version 3.1.3 protocol version 31.
I mount the harddrive first with Veracrypt and then with sudo mount... within WSL2.
sudo mount...
Then I run rsync with the target folder a subfolder on the harddrive.
It should copy files and directories to the harddrive.
Only folders are created. Files fail with the error Operation not permitted (1).
Apparently, that could be worked around with sudo rsync..., but this is not a very appealing and secure solution.
sudo rsync...
No response
The text was updated successfully, but these errors were encountered:
Try adding -o metadata,uid=1000,gid=1000, or at least the uid/gid. See this comment on #3187.
-o metadata,uid=1000,gid=1000
uid
gid
Sorry, something went wrong.
Works. Thank you.
No branches or pull requests
Version
10.0.22000.1219; Invalid command line option: --version
WSL Version
Kernel Version
4.19.104
Distro Version
22.04
Other Software
Using an encrypted harddrive mounted with Veracrypt 1.25.9.
And rsync version 3.1.3 protocol version 31.
Repro Steps
I mount the harddrive first with Veracrypt and then with
sudo mount...
within WSL2.Then I run rsync with the target folder a subfolder on the harddrive.
Expected Behavior
It should copy files and directories to the harddrive.
Actual Behavior
Only folders are created. Files fail with the error Operation not permitted (1).
Apparently, that could be worked around with
sudo rsync...
, but this is not a very appealing and secure solution.Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: