Recent content by malevolent

That worked here as well. It's a bit annoying that we need to restart the entire PVE host when we want to delete an old VM disk...

Hi everyone, I have been using proxmox and gluster together for the last decade, I have a hyperconvergence setup based on them quite stable and fast. On my last cluster, though, I had a horrible issue a few weeks ago when upgrading proxmox with an apt upgrade that made VMs terribly slow, so I...

I use ZFS underneath GlusterFS, so changing disks are quite less painful than LVM. I don't use a replica 3 as I think it's a waste of space, so I'm with a distributed dispersed volumes.

Just faced the same issue. I had a problem with PBS and I had to reinstall it. All my backups were failing with this error. Deleting the backup jobs and re-creating them did the trick for me.

Wow, that worked here! Thank you!

Well, after months of my last comment, when I'd reinstalled PBS above a MDADM instead a RAIDZ pool. I've just faced once again the same issue. This time, though, I made sure I had verification passed, but it failed once again. I think I'm giving up with PBS, or I have very bad luck, or it is...

Sorry for not answering before, I had a bad time trying to restore a very critical and huge SQL VM (more than 6 TB) from file restoration (blessed BURP backup and my paranoia in not relying on just one backup solution) and I completely forgot about this until now, when I decided to give PBS...

I'm also experiencing this issue, none of my restorations are working at all. I've tried like 10 so far and none of them are working. One VM which recently died. My storage zpool shows no errors. I had to disable verify backups because I have several Windows VMs whose verification could last...

Same here on Proxmox 7, can't load br_netfilter in order to install kubeadm.

good to know it's on the roadmap, most of my linux VM have LVM, so currently I'm just able to restore at brick level windows VMs (funny see NTFS support before LVM :p ) EDIT: Sorry for "invading" german forum, I had the automatic translator and I didn't notice the language. Anyway, this is the...

After making several changes on ZFS, it seems I have a combination of slow disks and gluster. Fast disks have no problem with ZFS + Gluster. Those slow disks and ZFS can also create/move huge disks. But when combining the slow disks with gluster, a timeout occurs. I tried ZFS performance options...

Same here, with 2T+ disks it always fails. Creation of 4TB+ disk also fails, I need to create a 2TB disk and then grow it 2TB more. But once created , the problem of moving them is here. I'm on Gluster over ZFS

I know gluster 3.12.15 reached EOL long time ago. That doesn't meant that newer versions are better. I tested and run gluster 3.12.15 during years without a single glitch (well, with one or two, to be honest :P ). And it performs hugely better compared with newer versions, mostly because version...

Just for the record. With Debian 10 (or Proxmox 6) we cannot longer use Gluster 3.12.15 as it uses the deprecated liblvm2app. I managed to install the 3.12.15 version in one of my nodes, but on the other two was impossible to start the server daemon, and glusterfs-common had some dependencies...

Well, version 5 (and 6 as far as I can see) are far slower than 3.12.15, my VMs are now 2/3 slower. Lets see if ZFS can do some magic... but for now it's a big disappointment. Now we can install any version, perhaps I downgrade to version 3.12.15 again.