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

Symlinks get restored owned by root instead of actual user #3848

Open
1 task done
archon810 opened this issue Aug 4, 2019 · 1 comment
Open
1 task done

Symlinks get restored owned by root instead of actual user #3848

archon810 opened this issue Aug 4, 2019 · 1 comment

Comments

@archon810
Copy link

  • I have searched open and closed issues for duplicates.

Environment info

  • Duplicati version: 2.0.4.23_beta_2019-07-14
  • Operating system: OpenSUSE 15.1
  • Backend: Box

Description

When restoring a Linux backup uploaded to Box back to the same Linux machine, all files seem to get their acls back correctly in my tests except for symlinks which are created as root:root instead of the original user:group.

Steps to reproduce

  1. Have symlinks not owned by root to back up.
  2. Back them up.
  3. Restore them - they're now owned by root:root.
  • Actual result:
    Symlinks are owned by root:root
  • Expected result:
    Symlinked are owned by the original user:group

Screenshots

Debug log

@ts678
Copy link
Collaborator

ts678 commented Aug 5, 2019

You could carefully try setting --restore-symlink-metadata but the manual explains that you might change the metadata on the targets instead. I don't know offhand which platforms (Linux, macOS, Windows, etc.) had that unfortunate tendency or if there's a way to avoid the issue aside from this:

v2.0.3.7-2.0.3.7_canary_2018-06-17

No longer restoring metadata on symlinks by default, as that updated the targets

v2.0.3.6-2.0.3.6_canary_2018-04-23...v2.0.3.7-2.0.3.7_canary_2018-06-17 for code-level search.

Duplicati looks like at least CreateSymlink code is mono native syscall or Alphaleonis on Windows.

.NET Core is missing suitable APIs for dealing with filesystems that contain symbolic links #26310
is one discussion of what future standards may do as they gear up for more universal OS support.

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