-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Auto-repair ghost files #24499
Comments
but we have to be careful with temporal scenarios ... |
Indeed, maybe call |
I get it... but this 'could' open up a can of worms. If a mountpoint is not there (user mounting external disk as their data dir for example) a sync from the client might delete all entries... and with it all shares/comments etc. Wouldn't it be better to allow deletion of not found files? But a get would return a temp not available? |
Fixed by #24813 by detecting a failed deletion and then calling |
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. |
In some bug situations, it can happen that a file was removed from storage but the filecache still contains it. In such situations, it is impossible for the user to delete the file while it still appears in the web UI and Webdav.
One solution is usually running
occ files:scan
.However, it would be good if ownCloud could detect this situation and auto-clean the bogus entry.
To detect this:
@icewind1991
The text was updated successfully, but these errors were encountered: