Thaddeus Hogan
Thaddeus Hogan
I am getting the same issue. This is on my reference infrastructure build so nothing that exotic has been done with it - it's pretty vanilla. After reading the last...
Update - I can reproduce this issue when restoring from a backup stored on a node's local storage, but it works fine when restoring backups stored on Proxmox Backup Server...
In my case it is DRBD/LINSTOR disk backed by ZFS, backed up to local directory, restored to DRBD/LINSTOR with ZFS backing disks. Where given the below storage config, the VM...
I prepared two identically installed Debian 12 VMs, except one is a Q35/SeaBIOS VM and the other is a Q35/OVMF EFI VM. Each VM has a single disk on the...
This issue was produced with a single backing disk on each node, attached to a SATA controller in AHCI mode - no RAID. I reproduced the issue with both enterprise...
@ghernadi - I have repeated the process with trace logging enabled. Notably, when I attempted to re-create the resize sequence that did not fail earlier, both tests resulted in the...
I was able to re-create this with just DRBD and with VMs - so this is not actually a Linstor bug. This can probably be closed, and I will open...