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

[stable9.1] Backport of filecache repair step OLD2 #29486

Closed
wants to merge 15 commits into from

Conversation

PVince81
Copy link
Contributor

@PVince81 PVince81 commented Nov 7, 2017

Resend of #29407

@tomneedham

Vincent Petry and others added 15 commits November 7, 2017 10:04
Whenever a parent-child relationship describes a specific path but the
entry's actual path is different, this new repair step will adjust it.

In the event where another entry already exists under that name, the
latter is deleted and replaced by the above entry. This should help
preserve the metadata associated with the original entry.
When fixing failed cross-storage moves in the file cache and using the
storage id filter, we filter by target storage for phase 1. However, we
also need to fix the source storages in phase 2. To do so, a list of
affected source storages is now gathered in phase 1 to be run on phase
2.
This instead of iterating over all storages which is way less efficient
due to the 1-N nature of potential failed cross-storage moves that we
are repairing.

If singleuser mode is enabled and "--all --repair" is passed, all
storages will be repaired in bulk (no repair filter). If not, it will
fall back to iterating over each storage which is slower.
@PVince81
Copy link
Contributor Author

PVince81 commented Nov 7, 2017

#29487

@PVince81 PVince81 closed this Nov 7, 2017
@PVince81 PVince81 changed the title [stable9.1] Backport of filecache repair step [stable9.1] Backport of filecache repair step OLD2 Nov 7, 2017
@PVince81 PVince81 deleted the stable9.1-repair branch November 7, 2017 09:09
@lock
Copy link

lock bot commented Aug 2, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Aug 2, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants