Search results

Ich bin nicht sicher, welches Problem das löst, aber denk dran: Das hilft nicht viel, wenn mal die Platte abraucht.

Thank you! Edit for reference in case someone checks here later: The target was correctly changed to the cluster partner. All I needed to do was turn replication back on. On the shell of node B, I could see a new ZFS snapshot being created. This was then replicated normally to the cluster...

Danke Dir! Edit als Referenz, falls jemand später hier nachschaut: Das Replikationsziel war korrekt auf den Clusterpartner geändert. Es war ausreichend, die Replikation einfach wieder einzuschalten. Auf der shell von Knoten B konnte ich sehen, wie ein neuer ZFS Snapshot angelegt wurde. Dieser...

Hallo zusammen, ich habe einen Container auf Knoten A meines Clusters vertüddelt. Ich habe ein Backup vom Freitag und der Container wird alle 15 Minuten repliziert. Ich habe die Replikation sofort gestoppt, so dass sich die Replik auf Knoten B im gewünschten Zustand befindet. Ich würde es...

Hi, messed up a container on node A of my clustered environment. I have a backup from Friday and the container is replicated every 15 mins. I immediately stopped the replication, so the replica on node B is in the desired state. I'd prefer to not lose today's work and use the replica instead of...

Thank you!

Hi, I'm trying to understand how proxmox makes snapshots of VMs and LXCs. If the VM disks and LXC volumes are stored on a ZFS storage - does proxmox then use the ZFS snapshot capability? If not, what's more efficient in terms of disk space - creating a snapshot using ZFS or the proxmox GUI?

Experimenting with 2 nodes (+ QDevice) in my homelab. Old PCs, no enterprise-grade hardware. I have an LXC with a bindmount to a local disk (500GB, no shared storage available) on node1. The disk is not setup as a proxmox data store. Data rarely changes on this disk. Similar local disk available...

OMG, it's right there before my eyes and ... Guess I need some sleep. Or more coffee. Thank you!

I have a small test cluster (without HA). Node 1 runs an lxc, which is replicated to other nodes. In case node 1 goes down, how do I start the container on another node using the replica?

+1, this would be good to have.

1 OP has lxc running and changes option in /etc/ssh/sshd_config 2 OP makes new template of lxc 3 OP deploys new lxc using said template 4 change from 1 is nor reflected in new lxc

Than you, I will. It would be consistent with the new behaviour, as attaching now doesn't need a container restart. Have a good week!

Applied patch and tested. Testcase 1: Mounting a host directory into running LXC using pct set 100 -mp0 /mnt,mp=/media/usb. If not existant, the mountpoint is immediately created and the host directory is mounted into the LXC. Very nice! Testcase 2) Mounting a host directory into running LXC...

Hi Fiona, that's great, thank you very much. Would you like me to test that patch (currently running 7.2-7)? Would it be sufficient to patch /usr/share/perl5/PVE/LXC/Config.pm, or would I need to do something else?

Hi, well, the title says it all: Can I bind-mount a directory into a running lxc?

Hi @Fabian_E, no worries, reporting bugs is my way to contribute :-) Thank you for the patch and have a good week!

@Fabian_E : Anything else I can do to help track this down?

I don't think so, because the latest version in buster is 3.4.14-0+deb10u1 and that's what I had when removing. I had installed pve 6 first quarter of last year and replaced postfix directly after installation. dpkg still shows the old buster version (pve 6 = buster has postfix...

Hi all, there's a glitch I found that's possibly a bug. I replaced postfix with nullmailer, both provide mail-transport-agent. postfix is in state 'removed' (rc in dpkg terms). No other packages changed / installed / removed. Looking at updates I found this: apt list --upgradable does not...