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.

Sign up for GitHub

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

Jump to bottom

Top-level subvolume extraction fails with 'Failed to run synchronizer: File exists' #239

Open
srd424 opened this issue Jun 13, 2020 · 0 comments
Open

Top-level subvolume extraction fails with 'Failed to run synchronizer: File exists' #239

srd424 opened this issue Jun 13, 2020 · 0 comments

Comments

@srd424
Copy link
Contributor

srd424 commented Jun 13, 2020

If the toplevel directory of a tree is a subvolume, mkdir_or_mksubvol() never seems to get called for it, so it is not created as subvolume. However ca_decoder_finalize_child() checks the subvolume status against the flags and fails with EEXIST, leading to a "Failed to run synchronizer: File exists" message.

Can be worked around by creating the subvolume by hand before calling casync.

This is a different bug to #237.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@srd424