Recent content by rholighaus

Having the same issue too. Any updates?

Somehow since PVE 7.3 this doesn't seem to work anymore. When logging in via SSH, I am still getting this output: root@carrier-2:~# pveversion perl: warning: Setting locale failed. perl: warning: Please check that your locale settings: LANGUAGE = (unset), LC_ALL = (unset), LC_CTYPE...

I had containers getting stuck, in particular a Ubuntu container in which I am running software using snap. The only way to resolve the issue was rebooting the PVE node. Not nice. I found this solution: Check the content of /sys/fs/cgroup/freezer/lxc/[container_number]/freezer.state. If it...

Thanks Denis Kulikov your fix is a life saver! Has anybody tested the behaviour with PVE7 and LXC 4.0?

There is a temporary fix in this thread once the container is frozen: https://forum.proxmox.com/threads/storage-replication-regulary-hangs-after-upgrade.72690/post-373688

I still have the occasional container freeze of an Ubuntu container with snap running wekan after either backup (vzdump) or replication issuing an lxc-freeze command. Much less often but every few weeks. Only solution is to reboot the PVE node. Is that a regression or will I have to live with this?

Hi Stoiko, The container has recently been upgraded from Ubuntu 18.04 LTS to 20.04 LTS. It seem to freeze when it receives an lxc-freeze command issued by the Proxmox backup routine. I can sometimes provoke by trying to create a snapshot using the GUI. Underlying storage is ZFS. As it's a...

Could it be that this reappears? I have the container freeze again, only resolution is to reboot the PVE host... # pveversion -v proxmox-ve: 6.3-1 (running kernel: 5.4.106-1-pve) pve-manager: 6.3-6 (running version: 6.3-6/2184247e) pve-kernel-5.4: 6.3-8 pve-kernel-helper: 6.3-8 pve-kernel-5.3...

We have been using two HP DL360 Gen8 with Samsung pm833a/pm1643 in a striped mirror ZFS setup for many years. Very fast and reliable - but you need to use a proper HBA, preferably one that support SAS3.

After cleaning up the snapshot and lxc config, the snapshot of this container is left over again after last night's backup. And it's locked. No error message as you can see. I am running znapzend to take hourly snapshots, replicate them to one or more remote sites and keep offsite snapshots...

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...

Thank you @carsten2 I still think an export/import function for seeding a remote site would be a cool feature. @fabian do you want me to log a feature request?

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?

Maybe a notation similar to the one in ZFS sync?

Just to update that with kernel 5.4.44-2, the problem seems to have disappeared.