-
-
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
Error: manifest has unsupported version: 2 (we support 4) #4375
Comments
This is expected, there is a WIP tool for that - ipfs-inactive/badgerds-upgrade#1 - if you really want to, you may give it a try:
|
Once ipfs-inactive/badgerds-upgrade#1 gets merged I'll add a better error message to badgerds. |
That seemed to work without issues as far as I can tell. I've only run it so far on a mostly empty repository, but I can now use v0.4.12-rc2 on it! Is this expected to be something that automatically gets run when v0.4.12 is released (if an older badger datastore is detected)? Or will it be a manual upgrade? |
@leerspace as badger is currently experimental, it will not be run automatically. Moving forward though, this sort of thing will likely be included as a migration between versions. Now that datastores are user-configurable we need to look into more advanced upgrade management. |
Thanks for the info. I won't wait for 0.4.12 with the expectation that it will be an automatic badger update and will instead update my nodes manually (using magik6k's badgerds-upgrade utility). |
Closing with #4379 |
Version information:
go-ipfs version: 0.4.12-rc2-
Repo version: 6
System version: amd64/linux
Golang version: go1.9.2
Type: Bug
Severity: Critical
Description:
The IPFS daemon fails to start after updating to v0.4.12-rc2. It fails with an error message saying
This looks like it might be coming from badger.
The text was updated successfully, but these errors were encountered: