Skip to content

Conversation

@Guiorgy
Copy link
Contributor

@Guiorgy Guiorgy commented Oct 3, 2025

chown may fail when the destination file system doesn't support Unix ownership attributes. Since the success of chown isn't critical, if this happens, just print a warning and continue.

Fixes #37

Demo:

  • Before this PR:

    $ sudo vackup export diun_data diun_data.tar.gz
    diun_data
    ./
    ./diun.db
    chown: /mount-volume/diun_data.tar.gz: Operation not permitted
    Error: Failed to start busybox backup container
    $ ls
    diun_data.tar.gz
  • After this PR:

    $ sudo vackup export diun_data diun_data.tar.gz
    diun_data
    ./
    ./diun.db
    chown: /mount-volume/diun_data.tar.gz: Operation not permitted
    Warning: Failed to change ownership of the diun_data.tar.gz file
    Successfully tar'ed volume diun_data into file diun_data.tar.gz
    $ ls
    diun_data.tar.gz

chown may fail when the destination file system doesn't support Unix ownership attributes. Since the success of chown isn't critical, if this happens, just print a warning and continue.
@Guiorgy Guiorgy force-pushed the continue-on-chown-fail branch from 4570f10 to 864f375 Compare October 3, 2025 12:01
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

Successfully merging this pull request may close these issues.

chown: /mount-volume/VOLUME_NAME.tar.gz: Operation not permitted

1 participant