Search results

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

Hi, I have already see this in production (on pve8), but I never found what was the problem. (So,I'm doing network config update carefully currently, with empty host, and reloading frr one by one). I wonder if it couldn't be related to the fwbr bridges for iptables , where frr could have...

if new kernel have changed interface name, the mtu from /etc/network/interfaces can't applied, as it's still defined on old name interface. (thanks systemd for the name change after each kernel update) pve9 have the new network interface pining to avoid this problem.

Fingerprints are only needed for self signed certicates, for normal certificate you really don't want to use fingerprint, or it'll break each the certificate is changed/refreshed.

@bbgeek17 in your article: "When a snapshot is created, subsequent writes are redirected to a new LVM logical volume. On a thin-provisioned SAN, storage for these writes is allocated on demand. When a snapshot is deleted, the system merges data from the previous QCOW image and LVM logical...

I have done test with blkdiscard --zeroing, from my tests, it's around 4~5x faster than the current csteam code (without throttling). Another benefit, is seem that is skip already zeroed block. so if you create,delete,create,delete,... it's a lot faster the second times if the block has not...

each snapshot have his own cache. (not that the cache value is a max value, by default 32MB max, but nothing is loaded until you begin to read differents part of disk). Also, metadatas not used are removed after 10min. I just sent a simple patch to the mailing, to increase the max cache size to...

about " When a snapshot is deleted, the system merges data from the previous QCOW image and LVM logical volume into the new QCOW image and logical volume. This merge process allocates additional storage in the new logical volume but does not release any storage from the old one." the option...

Hi, thanks for the article, I hope you enjoy my work ^_^ about performance, they are still performance improvement possible, mostly with qemu l2 cache size. Currently it's really depend of the qcow2 volume size, it's working up to around ~256GB. for bigger volume, we need to add an option in...