Search results

1) on each node : systemctl stop pve-ha-lrm then (when all lrm are down) 2) on each node: systemctl stop pve-ha-crm

proxmoxer is a client lib (a wrapper to proxmox rest api), why do you need to use it on pve node directly ?

don't seem to be a FS, but more an s3 like object storage, it'll not work

It's use for any qcow2 storage, including file storage. (local,nfs,...). External snapshot allow snap/delete snap without interruption. Current internal snapshot freeze the vm when deleting snapshot for example.

(I forgot to say that for snapshot, we use qcow2 sub-allocated cluster (l2_extended=on) with 128k cluster size, so metadatas are 32x smaller than base image (64k cluster without suballocated cluster). around 4MB memory for 1TB image https://www.youtube.com/watch?v=NfgLCdtkRus Also, the memory...

the cache value is a max value, it's only allocated when you need to load specific metadatas (and unused metadatas are flushed after 10min). It's not too much different than zfs btw, where you need memory to handle metadatas too. so , yes, if you read full disk with 8TB datas in less than...

I don't known who as recommend you tu use consumer ssd with zfs or ceph, but performance will be horrible. (because lack of power-loss protection, so the fsync for the zfs/ceph journal can't be cached). pm1643 (or any other enterprise ssd with plp) should works fine.

it should work with bridge-vlan-aware, but don't use 1 in bridge vids. (bridge-vids 1006) . (don't add native vlan in bridge-vids)

this is internal plumbing, ln_ && pr_ are veth interfaces, like a virtual link, between bondv77 && exemple bridge.

rm -rf /var/lib/pve-cluster/* on each node, and "systemctl restart pve-cluster"

what do you have change ? size ? min_size ?

I can speak about my solaris 2 nodes zfs that died 15year ago, with 3 days of downtime because of zil crash on 2 disk at the same time if you want ;) Never had a single downtime with ceph since 2015. what about rollback on 2 previous snapshot on zfs and create a new snapshot branches? what...

https://patchew.org/Libvirt/20200515034606.5810-1-hhan@redhat.com/20200515034606.5810-4-hhan@redhat.com/ https://github.com/qemu/qemu/commit/e0ae49871ae697b5d1a8853e79cbee35fda2145b if you want to test: diff --git a/src/PVE/Storage/ZFSPlugin.pm b/src/PVE/Storage/ZFSPlugin.pm index...

Another thing in my setup, I'm using ecmp with 4 path, and I just found an issue with a workaround here: https://vyos.dev/T5424

I mean, the vm firewall bridges. (my hosts have around 150vm, with 3 interfaces, so 450fwbr bridges). And frr is listening to netlink coming from all bridges. for vnet, I think I have around 40~50 vnet by host. I have 100k evpn routes. (for my case, I was also wondering if it could be a...

"ceph-volume lvm activate --all" on your target node, should rescan osd, and add them in the correct location in the crush map

rdma should be easy to implement in qemu initiator, it's just iser:// instead isci:// in the url. direct lun access through the kernel is not easy, because proxmox is distributed, and currently, if you remove a lun or resize it, or replace it (delete/add), the other nodes don't known about...

@bbgeek17 if you have time to test, I have send 2 patches: 1) bumping max qcow2 cache size up to 1GB memory (it should handle 8TB image without performance degradation) https://lists.proxmox.com/pipermail/pve-devel/2025-August/074555.html 2) saferemove speed improvement using blkdiscard...

could be interesting to see your custom crush rules

size=2/ min_size=2 . This is not going to work, it'll go readonly if you loose any osd. use min_size=1