-
Notifications
You must be signed in to change notification settings - Fork 76
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
database seems empty after upgrade #208
Comments
Can you send us the version of the database, where the upgrade didn't work? |
This is the backup before/while upgrade: |
Apparently there is an issue with the After migrating your database, Linstor loads every internal resource layer-trees and runs their intializers. However, an initializer of a resource which was created with internal metadata still sees at this point the I believe we have found and fixed the bug, which will be included in the next release. Until then, you should be able to temporarily remove the mentioned property and afterwards perform the upgrade. This issue might occur after every controller-restart, so re-inserting the property after upgrading will only work until you restart the controller. Until we do the release, you might want to use the resource-definition as a target for this specific property instead of the resource-group to avoid this bug for now. After the bugfix-release you should be able to safely use this property on resource-group level again. |
Because of #128 (comment) and a new blocksize=16k on ZFS I migrated from internal to external metadata. But some weren't already migrated but now they are. |
After update from 1.7.3.-1 to 1.11.0-1 the database looks empty.
r l; v l; sp l; rd l; every table looks empty.
I replaced the new database with the last backup (linstordb.mv.db-2020-12-30T00:17+00:00.bak), but it still wont work.
The version from once before (linstordb.mv.db-2020-08-02T20:33+00:00.bak) worked.
This is the first start, after update without reboot.
The upgrade
The databases
Last database backup (2020-12)
Old Database (2020-08) but it works
The text was updated successfully, but these errors were encountered: