Skip to content
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

Closed
leerspace opened this issue Nov 7, 2017 · 7 comments
Closed

Error: manifest has unsupported version: 2 (we support 4) #4375

leerspace opened this issue Nov 7, 2017 · 7 comments
Assignees

Comments

@leerspace
Copy link
Contributor

leerspace commented Nov 7, 2017

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

Initializing daemon...
Error: manifest has unsupported version: 2 (we support 4)

This looks like it might be coming from badger.

@leerspace
Copy link
Contributor Author

It looks like the on-disk format for badger changed with #4364 and #4327. So this is probably expected.

@magik6k
Copy link
Member

magik6k commented Nov 7, 2017

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:

  • Build it
  • Make sure your daemon isn't running
  • Make a backup of ~/.ipfs (or wherever your repo is)
  • Run the tool

@magik6k
Copy link
Member

magik6k commented Nov 7, 2017

Once ipfs-inactive/badgerds-upgrade#1 gets merged I'll add a better error message to badgerds.

@magik6k magik6k self-assigned this Nov 7, 2017
@leerspace
Copy link
Contributor Author

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?

@whyrusleeping
Copy link
Member

@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.

@leerspace
Copy link
Contributor Author

leerspace commented Nov 10, 2017

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).

@magik6k
Copy link
Member

magik6k commented Nov 11, 2017

Closing with #4379

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

No branches or pull requests

3 participants