Skip to content

Dangling ghost files from failed restore cause next restore to fail #18

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
Closed
xemul opened this issue Aug 12, 2015 · 1 comment
Closed

Dangling ghost files from failed restore cause next restore to fail #18

xemul opened this issue Aug 12, 2015 · 1 comment
Assignees
@xemul
Labels
bug
Milestone
1.8

Comments

@xemul
Copy link
Member

xemul commented Aug 12, 2015

Originally described in issue #16
@xemul xemul added the bug label Aug 12, 2015
@xemul xemul self-assigned this Sep 23, 2015
@xemul xemul added this to the 1.8 milestone Sep 24, 2015
xemul added a commit that referenced this issue Sep 28, 2015
@xemul
ghost: Remove ghost files if restore fails
efa7dcf 
Issue #18. When restore fails ghost files remain there. And
to remove them we have to know their list, paths to original
files (to construct the ghost name) and the namespace ghost
lives in.

For the latter we keep the restore task namespace at hands
till the final stage and setns into it to kill ghosts.

Signed-off-by: Pavel Emelyanov <[email protected]>
@xemul
Copy link
Member Author

xemul commented Sep 28, 2015

Fixed with efa7dcf

It was ... quite a lot of code moves...

@xemul xemul closed this as completed Sep 28, 2015
@throwbear throwbear mentioned this issue May 15, 2021
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@xemul xemul

Labels
bug
Projects
None yet
Milestone
1.8
Development

No branches or pull requests
1 participant
@xemul