Roland Kammerer

hm, yes, without thinking it through completely, such things could happen. The "when to create a diskless and when to remove it" logic is currently in the plugin: if there...

I don't see why this would not be compatible, LINSTOR itself uses drbdadm/drbdsetup. That would need a better error report. Anyways, I don't have time to maintain that project and...

But then you already have `blockdev`, and more importantly `-m` of `linstor`. IMO it is a good feature request, and we have a nice library for the conversions. But don't...

In general I prefer async communication like mailing lists/PRs. Other than that I would vote for IRC. That is something I have idling around in some tmux session anyways. I...

I have some ideas why this happened in the first place, and by checking if this is the case, I was not able to reproduce it. My best guess is...

@arcandspark > Are you restoring to a Linstor storage target when you get these "size ... updated" messages? yes, in my case that was a DRBD/LINSTOR disk where the backing...

thank you for the very detailed and helpful logs, and sorry this took a bit longer for a response... I have an idea and will try to reproduce it in...

"unfortunately" I still can not reproduce this. First I thought it might be a (block)size issue between zfs and lvm, but backup+restore worked as expected. then I thought it might...

once more thanks for the detailed info. I always tested with alpine images, I did check the EFI disk box... whatever did the trick, debian or q35, I now could...

this should be fixe in https://github.com/LINBIT/linstor-proxmox/commit/2dfcc496de4316ee89248edc91d7b0e18faec3ec . @arcandspark can you confirm this fixes the issue for you. just replace the file/the line and maybe `systemctl restart pvedaemon`.