[DRBD-user] Error upgrading linstor controller 0.7.5 > 0.9.5

doug at dimick.net doug at dimick.net
Wed Apr 10 16:43:10 CEST 2019

Thank you, Gabor. I was able to delete the unneeded resources, and the upgrade has now completed successfully. Much appreciated!



From: Gábor Hernádi <gabor.hernadi at linbit.com> 
Sent: Tuesday, April 9, 2019 11:26 PM
To: Doug Dimick <doug+drbd at dimick.net>
Cc: drbd-user at lists.linbit.com
Subject: Re: [DRBD-user] Error upgrading linstor controller 0.7.5 > 0.9.5


Hello again,


thanks for sending me the database, I was able to find the bug in our migration as well as a workaround for you until we release a fix for this.

The problem is that you had resources with no volumes in them. The migration basically iterates over all existing volumes using database-joins to gather all data of the corresponding resource, resource-definition and volume-definition. Within this volume-based iteration all data "above" are also created (that means, layer-specific database entries for the volumes themselves, but also for the corresponding resource, its resource definition and volume definition, each only if necessary). 

The fact that you had resources with 0 volumes simply prevented the migration to not create any layerData on those resources without volumes, which caused later the NullPointerException as mentioned in my previous mail.


So the workaround for you is to downgrade and start the previously working version (in your case v0.7.5), and please delete the two resources without volumes (in your case, the "empty" resources had "102" and "202" in their names). It should be safe to delete them as they had no volumes anyways, so there is no data on your disk which will be actually deleted :) (only entries in the linstor database)

The resource-definitions can stay, they do not hurt, just delete the (empty) resources.

Afterwards you should be able to upgrade, start and let the new version migrate everything.


Of course I will start looking in how to fix this so that the next version of linstor can handle this situation out of the box. 


Thanks for the report,

Best regards,


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20190410/193cb0ce/attachment.htm>

More information about the drbd-user mailing list