Recent content by Chicken76

Thank you @fiona I bit the bullet and shut down the VM during lunch break. No problems starting it up after. Doing a manual backup right now and it's running normally. So the problem is solved and the thread can be closed.

Backup jobs have failed with the message: ERROR: Backup of VM 104 failed - VM 104 qmp command 'backup' failed - Node 'drive-scsi1' is busy: block device is in use by block job: mirror So I did the following: qm monitor 104 qm> info block-jobs Type mirror, device drive-scsi1: Completed...

I just upgraded my PBS from 3.4 to 4.2 and pbs3to4 still gives me a warning after rebooting: I assume this is not really a problem, just the script was written before kernel 7.0 was an option?

I even grabbed a screenshot of the ping window:

Environment: PVE 8.4.14 VM with VirtIO NIC configured in a VLAN some three switches away I have another device connected to a port that's native in that VLAN everything worked fine for months, years, eons Today I had to unplug that device and change it's position and arrange the cables a bit...

So I've just added a second PBS server as a storage for backups in my cluster. The first backups have been done last night on this PBS and I saw the "INFO: scsi0: dirty-bitmap status: existing bitmap was invalid and has been cleared" message in the logs, which was expected. Now what's gotten me...

I'm not very knowledgeable in this but I think compression would be preserved only if zfs send <-> zfs receive would be used, which I don't think Proxmox does.

I've removed today a node from the cluster at work and to my surprise some backup jobs started running. I've followed the steps in the documentation and removed from command line, and everything worked fine except for that "could not kill node" error, but the guide warns about it happening and...

Does it really? I found this: https://github.com/openzfs/zfs/discussions/12769 The metadata does, but not the blocks with the actual content.

Firstly, sorry about resurrecting this old thread. Does the special_small_blocks apply to zvols? I thought it only applied to datasets.

I see now. It refers to PVE and PBS running side-by-side on the same installation of Debian. You definitely don't need to upgrade a separate machine running PBS 2.4 to 3 before upgrading PVE 7 to 8.

Thank you for clearing things up. I still have a question: what does the line "Co-installed Proxmox Backup Server: see the Proxmox Backup Server 2 to 3 upgrade how-to" mean in the prerequisites section of the PVE 7-to-8 guide? At first glance it sounds like PBS needs to be upgraded to v3 before...

This thread needs to be resurrected now that we have PVE8 and PBS3. So what does the compatibility matrix look like currently?

That's because I didn't create the first partition (BIOS boot). How do you create a partition before sector 2048? Neither fdisk nor gdisk will let me. But the good news is it worked even without the first partition. There was a warning but every step proceeded fine. The only other warning I...

@Stoiko Ivanov Thank you for the advice. I am still trying out all the steps in a virtual machine. When adding the new partition to the pool, zpool complains like this: root@pvetest:~# zpool attach rpool /dev/sda3 /dev/sdb2 cannot attach /dev/sdb2 to /dev/sda3: no such device in pool I ended...