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

Cache: also check if the file id is already in the cache during upgrade #2096

Merged
merged 2 commits into from
Mar 4, 2013

Conversation

icewind1991
Copy link
Contributor

Should solve upgrade issues if only some of the configured storages were migrated previously.

The only way a a file id can already exists in the cache is when a previous upgrade attempt fails after at least one storage has been successfully upgraded

@MTGap @karlitschek @DeepDiver1975

Should solve upgrade issues if only some of the configured storages were migrated previously
@karlitschek
Copy link
Contributor

Very good to have this fixed 👍

@MTGap
Copy link
Contributor

MTGap commented Mar 4, 2013

Can you do just one query with the id to see if it is already in the filecache?

@eMerzh
Copy link
Member

eMerzh commented Mar 4, 2013

Great ! btw its a ref to #2091

@eMerzh
Copy link
Member

eMerzh commented Mar 4, 2013

It works great for me with a external drive attached (Google)

@icewind1991
Copy link
Contributor Author

@MTGap right, fixed in the above commit

@MTGap
Copy link
Contributor

MTGap commented Mar 4, 2013

👍 Waiting for build to finish.

@bartv2
Copy link
Contributor

bartv2 commented Mar 4, 2013

👍 looks good

MTGap pushed a commit that referenced this pull request Mar 4, 2013
Cache: also check if the file id is already in the cache during upgrade
@MTGap MTGap merged commit db23c88 into master Mar 4, 2013
@MTGap MTGap deleted the cache-upgrade-id branch March 4, 2013 22:55
@lock lock bot locked as resolved and limited conversation to collaborators Aug 18, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants