[DRBD-user] linstor-proxmox: Intentionally removing diskless assignment

Andreas Pflug pgadmin at pse-consulting.de
Wed Dec 18 14:11:01 CET 2019


Am 18.12.19 um 14:02 schrieb Roland Kammerer:
> On Wed, Dec 18, 2019 at 01:16:02PM +0100, Andreas Pflug wrote:
>> The migration appears fully sucessful to me, drbdadm status shows
>> UpToDate on all nodes and Primary on the MigrationTargetHost only as
>> expected.
> 
> And on the migration source? Is there still an assignment in linstor for
> that node? "linstor r l".
> 
> Guess at that point I would just try to "r d" on linstor level, maybe
> help it on the migration source node with some "drbdsetup down", maybe
> even '--force' to just get rid of it.


Everything looks fine when migration has finished, no dangling resources
or other visible anomalies in drbdadm or linstor on any node; just those
error messages.

The only non-standard configuration detail in my installation is an
alternate network interface designated to DRBD traffic, assigned to all
storage pools (including the diskless via DfltDisklessStorPool).

Regards,
Andreas


More information about the drbd-user mailing list