Skip to content
This repository has been archived by the owner on Feb 12, 2019. It is now read-only.

incorrect quota state #1983

Open
initbar opened this issue Dec 19, 2018 · 4 comments
Open

incorrect quota state #1983

initbar opened this issue Dec 19, 2018 · 4 comments

Comments

@initbar
Copy link

initbar commented Dec 19, 2018

keybase fs quota shows that I'm using 29 GB of storage -- when /keybase/{private, public}/initbar directories are empty:

screenshot_2018-12-19_00-02-37

keybase fs reset doesn't seem to work (or perhaps I'm using them incorrectly) as it says reset cannot be done.

screenshot_2018-12-19_00-04-38

Is there any way to fix this incorrect quota state?

@strib
Copy link
Contributor

strib commented Dec 19, 2018

There does seem to be an issue with tracking quotas. We haven't prioritized it since generally we give out so much quota people don't even get close to using it up. We will get there some day. I suspect you had a bunch of data in those folders and some point and then deleted it?

The fs reset command is intended for a different situation, where your folder is completely broken and needs to be reset from scratch. It's not intended for resetting quotas, though eventually that might be a good use for it.

Sorry for the rough experience. If you get close to your limit, please let us know and we can help you.

@voobscout
Copy link

keybase fs quota
Usage:          -7205742 bytes
Quota:          250.00 GB
df -h
Filesystem                     Type  Size  Used Avail Use% Mounted on
/dev/fuse                      fuse  250G -8.0Z  -16E 100% /keybase

A better question is - does that affect integrity or is it just a quota calculation thing?

@strib
Copy link
Contributor

strib commented Jan 8, 2019

Just quota calculation. It doesn't affect your data at all.

@voobscout
Copy link

Good to know, thanks!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants