Dirty-bitmaps reset if reboot vm from inside

scasrl said:
If I restart the vm from its console the dirty-bitmaps are reset, I thought they were supposed to persist, am I wrong?
Click to expand...
I would expect so. I just tested it with two backups (to the same PBS) with a reboot in between (via SSH from inside the VM) and it did reuse the dirty bitmap.

Can you show your VM configuration file to see if there is something that might prevent dirty bitmaps from being used? I don't know what that might be but hopefully more knowledgeable people here can tell.
 
leesteken said:
I would expect so. I just tested it with two backups (to the same PBS) with a reboot in between (via SSH from inside the VM) and it did reuse the dirty bitmap.
Click to expand...
Please note that a reboot is not the same as stop/start.

And no, we do not persist the dirty bitmap on stop, because we are afraid of changes from external sources.
 
Here the conf of the vm
The vm has 5 snapshots

agent: 1,fstrim_cloned_disks=1
boot: order=scsi0;ide2;net0
cores: 2
cpu: xxxxxxxxxxx
ide2: none,media=cdrom
memory: 4096
meta: creation-qemu=8.1.2,ctime=1707924728
name: xxxxxxxxx
net0: virtio=xxxxxxxxxxbridge=xxxxxxx,firewall=1
numa: 1
onboot: 1
ostype: l26
parent: xxxxxxxxxxxxxxx
scsi0: local-zfs:vm-xxxxxx-disk-0,discard=on,iothread=1,size=64G
scsihw: virtio-scsi-single
smbios1: uuid=xxxxxxxxxxx
sockets: 2
vmgenid: xxxxxxxxxxxxxxxxxxxxxxx
 
Last edited:
Hi,
please share the output of pveversion -v.

Did you maybe to a rollback or disk resize in between backups too? What do you see in the VM's Task History?

Are subsequent backups going to the same target storage?

Please share the full backup task logs for the previous working backup and following backup with the issue. If it's a single backup, you can find it in the VM's Task History, if it is a backup job, the node's Task History.
 
You must log in or register to reply here.
Top Bottom