[DRBD-user] DM to Linstor migration issue

Roberto Resoli roberto at resolutions.it
Thu Aug 23 08:59:53 CEST 2018


Il 22/08/2018 09:45, Roland Kammerer ha scritto:
>> I checked with
>>
>> lvs --units k
>>
>> and the size was as reported by linstor-satellite error report (after "but
>> was:")
>>
> Do you still have the migration script? Could you post the part for that
> resource? Would be interesting which value the script tried to set.

Find the migration scrip (some lines commented by me because i executed 
them manually without modification), and the set of error reports here:

https://www.resolutions.it/nextcloud/index.php/s/Rr7y2Y9jiEedtqm

> Anything uncommon? Did you change the max number of peers or anything?

No. As I said after reviewing the error reports I tried to adjust the 
size of some resources (other were fine); here the commands from bash 
history:

linstor vd size vm-102-disk-1 0 15745024KiB
linstor vd size vm-103-disk-1 0 62976000KiB
linstor vd size vm-103-disk-1 0 62976000KiB
linstor vd size vm-106-disk-1 0 12595200KiB
linstor vd size vm-120-disk-1 0 10498048KiB
linstor vd size vm-120-disk-2 0 10498048KiB
linstor vd size vm-121-disk-1 0 15745024KiB
linstor vd size vm-123-disk-1 0 10498048KiB
linstor vd size vm-999-disk-1 0 10498048KiB
linstor vd size vm-999-disk-2 0 20992000KiB

The cluster is three nodes, all resorces replicated an all nodes.

After the resources terminated to sync oos remained in some of them, but 
I resolved with usual manual intervention (disconnect primary, write on 
it, adjust primary).

> It is good hat there is a fix and you guys managed to migrate. I still
> wonder why this did not trigger in my tests.
> 
> Regards, rck

I feel linstor is definitely a great improvement in solidity, thanks for 
all the efforts in its realization.

rob


More information about the drbd-user mailing list