Thanks for testing it out and for the additional info. :)
Right now, I'm testing it with a single Remote that contains a single node, so there's not really an alternative path to a second node if the first one becomes unreachable. I have...
Moving the config file doesn't stop the VM; nothing watches /etc/pve and kills a running kvm process when its config moves away. All you've changed is which node PVE thinks owns the guest, so the process on vm1 carries on running and writing to...
Thats what it should do if the vm is configured for HA (HA replicates the vm disks from PVE node vm0 to PVE node vm1 with ZFS replicas) if you migrate a vm to different PVE node the replication is automaticaly reversed and it replicates from PVE...
and the retention settings
The only write once read many (WORM) I know are the identically named LTO tapes. As long as you secure your PBS properly, e.g. not attaching it to any AD/LDAP/OID to keep the attach surface small, you're safe. PBS acts...
One thing that may happen during the first 30 minutes is that caches are warmed up, ARC may fill, other processes start and consume memory.
Let memtest86+ run for multiple rounds, at least over night - or longer.
Yes, PBS uses this technique, Veeam implemented it's own. Therefore you need the worker VMs. Hoepfully they'll adapt to the correct API PVE provides in order to have a better integration.
and the retention settings
The only write once read many (WORM) I know are the identically named LTO tapes. As long as you secure your PBS properly, e.g. not attaching it to any AD/LDAP/OID to keep the attach surface small, you're safe. PBS acts...
and the retention settings
The only write once read many (WORM) I know are the identically named LTO tapes. As long as you secure your PBS properly, e.g. not attaching it to any AD/LDAP/OID to keep the attach surface small, you're safe. PBS acts...
Yes, it's probably not necessary in practice but it remains ironic: that which makes check-summing redundant filesystems perfect for swap is exactly what makes them impossible to use for swap.
I guess a md-raid1 of multiple md-integrity (without...
Good question, it made me do a short googling. Following older stackoverflow thread from the results has some interesting points:
https://unix.stackexchange.com/questions/269098/silent-disk-errors-and-reliability-of-linux-swap
The basic argument...
Why? lxcs are not dependent on any logical handoffs. if the device is accessible to the host, its accessible to the container.
You wouldnt be passing the device, you'd give permission for the container to access its driver. the bus location is...
just to add a bit of context and hopefully make things a bit more clear for future readers
not quite - the output comes from listing the entry in the `debian/NEWS` file from the Debian Upstream zfs-linux source package...
I found the root cause of the issue, and it was related to the NIC chipset.
I was initially using an HPE FLR560, which is based on an Intel chipset X520-DA2 that apparently does not handle VXLAN properly in my setup. As a result, I was...
Hi, i have the logs of pvestatd[3335]: failed to spawn fuse mount, process exited with status 256 resolve proxmox, I like to know how I can resolve it because the esxi server work in this moment or someone have this in the past ? and how resolve...
The Samsung 860 EVO was one of the drives with severe issues with ATA Trim. The error you are describing looks like the drive is not "available" at boot-time. Loader still works and then it is gone.
Maybe a regression, concerning those mentioned...