Search results

  1. rholighaus

    Container locked after backup, stuck at delete vzdump backup snapshot

    I'm running a nightly backup of VMs and LXCs to PBS. Almost every night, one of the containers leaves a vzdump snapshot hanging that I have to manually remove and edit the lxc config file to remove the lock and snapshot from there. Containers and VMs are stored on zfs. Any idea what...
  2. rholighaus

    PBS Initial Sync for Remote (off-site) Server using USB disk?

    Is there a recommended procedure to kick-start a remote (off-site) server with a USB disk instead of having to sync potentially hundreds of Gigabytes over a WAN link?
  3. rholighaus

    [SOLVED] Proliant DL360e GEN8 freezes with kernel 5.4.44

    After rebooting, PVE completely stops working after some seconds when booted on the new kernel 5.4.44 - even on the console. No panic, no nothing. Just frozen. Ping stops replying, too. When booting on kernel 5.4.41, the system runs fine. Can I help debug? The mentioned system is our backup and...
  4. rholighaus

    [SOLVED] Bug? zpool auto-trim=on leads to high iowait on SSD pool

    Hi, Our system has the following setup. It boots from a USB stick which holds the /root filesystem to prevent ZFS issues when booting as it doesn't support UEFI boot yet. The pool rpool consists of Samsung pm1633a enterprise SSDs in an external SAS enclose and ususally perform well. After...
  5. rholighaus

    LXC container with Wekan/snapd freezes completely

    We are running the wekan snap package in an LXC container and it works well, but about once a day, it completely freezes, stops responding to ping requests. Only way to stop it is lxc-stop -n 121 --kill and restart it using pct start 121. The container's /var/log/syslog just stops at the time...
  6. rholighaus

    ZFS Storage Replication - transferred size bigger than actual disc size

    We are using ZFS storage replication. A container running on host carrier-1 is replicated to carrier-2. NAME USED AVAIL REFER MOUNTPOINT rpool/data/subvol-115-disk-1 3.29G 96.7G 3.26G /rpool/data/subvol-115-disk-1 rpool/data/subvol-115-disk-2 333G 82.6G...
  7. rholighaus

    ZFS replication via migration network - sporadic problems finding target IP address

    We have a cluster of 2 production nodes and 2 PVE nodes that are only working as ZFS replication destinations. As recommended, we have recently created a separate migration network and entered it in /etc/pve/datacenter.cfg: # use dedicated migration network migration: secure,network=10.1.2.0/24...
  8. rholighaus

    Feature request: VM migration (restart mode)

    In a replicated ZFS environment, containers can be easily migrated from one node to another, as the only supported migration mode of a running container is restart mode. It works quick and reliably if replication happends e.g. hourly or more often. For VMs, the system does not allow to select...
  9. rholighaus

    ZFS Replication running away?

    I have the following file system that gets replicated to two other PVE nodes: root@carrier:~# zfs list -ospace -tall -r rpool/data/subvol-104-disk-2 NAME AVAIL USED USEDSNAP USEDDS USEDREFRESERV USEDCHILD rpool/data/subvol-104-disk-2...
  10. rholighaus

    ZFS snapshots and replication: Sufficient as backup?

    Hi all, We are currently running a PVE cluster with multiple machines and serve about 15 LXC containers and 10 VMs. We are using PVE replication (every 15min) to onsite PVE machines and znapzend to create hourly snapshots that are also replicated off site. This should protect us against a...
  11. rholighaus

    ZFS - consistent replication of VMs with database applications

    I want to migrate existing Windows Server 2012R2 VMs from Hyper-V to Proxmox. The VMs in question are either based on Oracle or MS SQL databases running within the VM. Currently, they are backed up via a commercial backup solution that backs up the VM disks on the Hyper-V host. As those VMs are...
  12. rholighaus

    Container RAM usage display not considering cache

    I am running various containers that seem to be using a lot of memory, according to the Summary View. The RAM usage is therefore red - see screenshot. When digging into the container, however, it quickly shows that most of the "used" memory is actually used as cache - so tainting it red in the...

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!