-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Upload quota consumed without files uploaded #22817
Comments
There is no way to cancel an upload at the moment. You can delete the file, and in the background it will still be uploaded, and then deleted once the upload is complete. Supporting cancellations is complicated due to the way KBFS works, though in the future we might find a way to do it. If your quota is not recovered after the upload is completely done, let me know. |
This is the actual problem |
You're sure the upload is complete though? It might still be going. You can try |
Yes, already tried, nothing shows up |
Ok. I will look at your logs tomorrow when I'm working. In general though, the quota is so big that we usually don't worry about it. If it never recovers and you fill up the rest of the space, we can always fix it manually. |
Ok thanks |
I looked into your logs and I confirmed the upload completely correctly. There was a conflict resolution involved (where another device wrote to the folder while this device was), which makes the bytes tracking a little more complicated. In any case, yeah this seems like a quota tracking bug but we will likely not treat it with high priority. If you do end up needing more quota just let us know. Thanks! |
Ok, thanks |
I uploaded a big file to test the Keybase file storage, but after I noticed there was not a way to abort the upload, I deleted the partially uploaded file from the file explorer. The client continued uploading it, and now I have 7.5 GB of upload quota occupied (I see 242.5 GB of free space instead of 250 GB) without any file to delete (nothing shows up in the private folder where I uploaded it).
my log id: 242b8f6a078707be18c6d51c
The text was updated successfully, but these errors were encountered: