-
-
Notifications
You must be signed in to change notification settings - Fork 729
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
missing original owner and group after extract #8088
Comments
Did you run root is required to change user or group away from the current user/group. |
Hi Thomas, thanks for that hint. Indeed, after I run borg extract from the root user, everything works as expected. Thanks Wolfgang |
Not sure the docs point that out, but this is how chown/chgrp works on UNIX / Linux / ... in general. Just imagine you could create a suid binary owned by your user and then you could chown that to root. :-) |
Have you checked borgbackup docs, FAQ, and open GitHub issues?
Yes
Is this a BUG / ISSUE report or a QUESTION?
Question
System information. For client/server mode post info for both machines.
Your borg version (borg -V).
borg 1.2.6
Operating system (distribution) and version.
Synology OS
Hardware / network configuration, and filesystems used.
How much data is handled by borg?
just a few for testing
Full borg commandline that lead to the problem (leave away excludes and passwords)
Describe the problem you're observing.
I can create the repo, doing the backup and after that, find the files I've backup'ed in the repo. With the detailed list command I can see, that Owner and Goup name is stored inside the repo:
After the restore with borg extract I find all my files belonging to admin / users. I tried extract with and without the parameter --numeric-ids, the result is still the same.
What do I have to do to change this behavior?
Additional Info: Files to be backed up are on my Synology NAS A, the repo is on my Synology NAS B.
Thanks Wolfgang
Can you reproduce the problem? If so, describe how. If not, describe troubleshooting steps you took before opening the issue.
Include any warning/errors/backtraces from the system logs
The text was updated successfully, but these errors were encountered: