-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
v0.11.0-rc1 underreports RepoSize significantly #8579
Comments
Thanks for the report. It looks like a function got missed as part of #6803 (i.e. https://github.com/ipfs/go-ds-flatfs/blob/27a1f1eee3538be7ff43b7f1a5c73122427738fb/flatfs.go#L1094). @guseggert could you take a look through the other datastores to:
This is going to look like ipfs/go-datastore#184. I'd definitely check out FlatFS, Badger (1+2) and S3 datastores as those are the mostly commonly used ones. |
@ylempereur Could you upgrade to RC2 and verify that it fixes this issue for you? https://github.com/ipfs/go-ipfs/releases/tag/v0.11.0-rc2 |
@guseggert That did it! the correct size is now being reported when using rc2. Thank you |
Checklist
Installation method
ipfs-update or dist.ipfs.io
Version
Config
Description
My datastore contained over 2GB before I switched to the latest binary (and was reporting it correctly in v0.10.0), it now reports around 230MB (in repo stat and webui).
I have run some tests and the pinned data is still there and reachable. Adding and removing data (using add, pin rm and repo gc) do not appear to alter the reported repo size (while the data becomes reachable after add and unreachable after gc).
My install is mostly default, with the exception that I'm using the AcceleratedDHTClient.
Please advise.
The text was updated successfully, but these errors were encountered: