Search results

PS: what the heck does the shared option do anyway? One would think it meant shared, rather than the other meaning of shared which only PVE knows about meaning its not shared.

Thanks, I only needed to store the kernel boot files and initial ram disk which are small but beyond the shared config. I come from proper engineering background, so I went for the simplest solution; create a directory which rsyncs to others using cron, rather than faffing about adding layers...

I looked through that link but there must be something wrong with me. I do NOT understand how it does what I asked for. It only seems to know how to replicate its own files. It has the restriction of container, iso etc. What I want is a mount point that replicates between sites and has a...

So I know it has a clusterfs already on it for the machine configs etc. I looked at adding storage replication but seemed like a lot of unnecessary faff, so I may as well create a directory and a cron to rsync. I just thought there would be an out of the box way. I really thought the shared...

I have 3 nodes joined together and I have imported some legacy KVM virtual machines. These require kernel boot images which I have configured in the conf file as an argument. At the moment I have put those files on an NFS share that all nodes can see so they have the same path on all nodes...

indeed.

That could well be correct, once I upgraded (for a different reason, a bug requiring tables to be constantly manually analyzed) and we still had the problem I stopped doing it. I believe the problem is linked to the kernel so upgrading a program isn't going to fix anything. I say that because...

What problem with MariaDB did you see? The first issue we saw with MariaDB is that queries suddenly started never returning, when that was in a cluster the entire cluster then would not return queries because I presume it was waiting forever for a node to commit. My memory is sketchy on this...

We've had had the issue on all containers and VM's. MariaDB just seems to to notice it early on and thats where we first noticed it. I still don't think its actually anything to do with fs-freeze at all, since its occurred without the qm-guest, qm-guest just happens to be the only process able...

what did you need to have in place to restore from a snapshot to a fresh prox node? I assume as a bare min the vm config file then use zfs receive.. the snapshotted partitions (I have 3) the machine state if we had one. I think this is independent of the partitions but the filename must...

Its been around for some time - I believe it hasn't been fixed because they are looking in the wrong place - concentrating on the fs-thaw and scratching their heads. We don't have the necessary agent installed for fs-freeze/thaw to be called inside the VM, and yet the problem still occurs. So...

OK, here's my plan. Which I have gathered from about two dozen posts on the issue: I am using the autosnap you mention there. Then I send that to a backup NFS drive we have mounted $ zfs send rpool/data/vm-101-disk-1@Backup_2023_01_20 | bzip2 | pv >...

It is ZFS. Its a cluster of 3 HA and it replicates to the other two. We have a backup storage mounted as well. How did you implement this?

Is it possible its nothing to do with fs-freeze / thaw? I don't have the guest agent but its very much the same problem on snapshot - basically disks become inaccessible. I posit that if thats the underlying issue, then the fs-thaw will also fail. In my case there is nothing in the log to...

I'm here because we're using snapshots to backup a warehouse management server and the snapshot breaks the FS locking up the VM permanently. But everyone tells me its the guest agent having an issue with fs-freeze and fs-unfreeze; apparently a bug thats been around for a long while and everyone...

Sometime last year I found that when snapshotting a running container with mariadb would cause the database to be unable to complete any queries - the process was running but queries just stacked up. It was as if the fs was missing briefly but could not recover. It was assumed it was a mariadb...

One of our datacentres had a power outage but the proxmox mode was not shutdown before the power was lost. There has been some updates applies a few weeks ago to take it to 7.2.3. After the restart the IO delay has reduced - which sounds like a good thing. Is this expected and is there...

scratch that - its related to that first node. Its exactly the same migrating back. 10% speed. Yep, pushing it back the way.... You can see its now 10% - that looks like its deliberately capped somewhere?

OK that is copying very quickly now. Sorry there is such a long gap in the middle but you can see the inbound copy was 12MByte/s The outbound is now 120MBytes. So yeah - its the secure method that slows it down by exactly 90.0%.

It restored in about 11 minutes 54Gb. That means that the limitation was NOT related to write performance of the disk, in this case it was read from the network performance. So, that means its unsolved as of now. I will try the unsecure copy and see if that makes any difference.