Recent content by kwinz

No outages with the one Ceph monitor down, I still had full read and write functionality. And besides this hickup last week it has been solid for years.

Thanks everyone! It's relieving that Proxmox backported the data corruption fix to 17.2.8-pve2 On my end I now successfully dealt with my issue by: 1. Following https://pve.proxmox.com/wiki/Ceph_Quincy_to_Reef (18.x) 2. at this point a ceph monitor on one node pve4 still refused to start even...

I am on Proxmox 8.4.16 on the paid subscritiption. Proxmox VE 8.4 should still be supported until August 2026. https://forum.proxmox.com/threads/proxmox-ve-support-lifecycle.35755/ I just upgraded a cluster and to my surprise after rebooting the first server its Ceph Monitor failed to start! So...

Hi, today I ran updates of PVE (8.1.3) as usual, and I got this prompt: I have PVE subscriptions and licenses installed on all servers. I can't believe I didn't find anything about this with the forum search function. I think that this is just telling me that the package has to be...

Related: https://forum.proxmox.com/threads/pve7-and-ecc-notification.93682/

That's good to know, thank you! PS: Could you share a link / mailing list thread / issue number / patch or fix commit for that ext4 bug where trim is only used once on an extent? I want to make sure that my kernel is not affected.

Thanks! Is this still needed with Proxmox VE 7.4?

So to summarize: we have two independent people reporting TRIM/DISCARD isn't working for VMs on Ceph RBD and we still don't know why after two years? Have you tried bdev_async_discard and bdev_enable_discard globally (or on each OSD)? Source...

> Would ZFS compression add significantly, as Backups are already compressed ? No, it will not. > What is the advantage of using ZFS (consuming memory) instead of ext4 on a raid controller for backup space? Proxmox Backup server indeed has a lot of features that make some of the ZFS features...

Hi, so far I did backups as a different user. Now I deleted all old backups, and garbage collected the old backups. According to the GUI the Proxmox backup server (PBS) is completely empty. However if I attempt to do backups as the new user, I am getting errors like: INFO: creating Proxmox...

I have a backup job with Mode: stop (not snapshot or suspend). After I manually aborted this backup job via GUI's "Stop" button, the VMs remained locked. And I could not backup them any more. ERROR: Backup of VM 108 failed - VM is locked (backup) INFO: Failed at 2023-03-11 11:09:33 INFO...

I have the same issue. I am wondering if this intentional. Maybe the service is intended to stop if it's unused? Similar to the Chrome update service: https://serverfault.com/questions/510100/how-can-i-fix-this-windows-2012-dashboard-error-google-update-service Did you find any new information...

Appreciate the reply! I was just asking because you mentioned you did the hardware upgrade to expensive NVMe because the verifications "needed too much time, so they overlaped". Not running them as often could also have solved the overlapping problem, right? And secondly I noticed that you are...

AFAIK the majority of work is handled in the PVE clients, the PBS server is untrusted and mainly only does dedup. So it would also make sense to check your PVE hardware. I see that you didn't receive any response for half a year. What did you end up buying for PBS? And what's your performance now?

Technically I don't see why it wouldn't work like I suggested. On restore recreate the template image (or just its disk) from scratch from backup if it doesn't exist yet. Clone the VM again. This recreates the parent-child relationship. And then selectively overwrite the blocks that have changed...