Search results

If you're using a local ZFS pool with LXC on a filesystem (the default for local ZFS storage) rather than a disk image , you can shrink or grow the filesystem at any time with (adjust 100G to the desired size): zfs set refquota=100G POOL/FILESYSTEM Disk images or block devices can only be...

Initial testing looks good. Everything that was in the 4.14 branch should be in 4.15 so I'm expecting that this issue will be fully resolved by the new kernel. Thanks everyone.

This issue produces similar output to yours: https://forum.proxmox.com/threads/apparmor-preventing-lxcs-starting-after-update.42060/#post-202268

These lines makes me think the argument for "rootfs" is incorrect. Edit /etc/pve/lxc/CONTAINERID.conf and confirm that rootfs makes sense in the new environment. Also make sure there is a /var/lib/lxc/CONTAINERID directory. If that looks ok, use this command to collect more detailed startup...

You do not have to do a zpool export before upgrading ZFS. Just do a "apt-get update && apt-get dist-upgrade", then reboot. Anyone that wants to argue the point should ask themselves how a ZFS root filesystem would get updated if it had to be exported (inaccessible) to be updated (requiring...

I saw the reference and wanted to add some clarification: the issue in my thread is a kernel bug and has been unrecoverable in my experience (waiting up to 3 days). The hypervisor has to be rebooted once the namespace cloning bug is hit. The issue has a distinctive stack trace on lxc monitor...

UPDATE: Proxmox has released a 4.15 kernel (see below). Please focus your testing on that kernel. You can download the kernel (required) and headers (optional) from here: https://www.dropbox.com/sh/k7ad34tvwadsjpv/AABGqx036UWpht1mYDMJTh5Ea?dl=0 To install: dpkg -i...

I've seen this on multiple Xeon based servers. The problem is occurring in the kernel's network namespace management so I don't think it's going to be an issue with the filesystem choice, CPU architecture, etc. These may play into a timing component that is exacerbated by particular combinations...

Fabian: I do use NFS inside containers on my home server but not on two of the hypervisors that have had a network namespace lockup at work. It has been very easy to duplicate the issue at home (minutes - likely the NFS patch listed) but much harder on the hypervisors at work (up to 3 days of...

Good news: I bisected the 4.14 kernel releases and determined that 4.14.4 is the first working kernel version. Looking at the change log, I'd bet that this is the fix we're after: commit 84779085fa10014b9e8208d7e71b54bced73075c Author: Vasily Averin <vvs@virtuozzo.com> Date: Thu Nov 2 13:03:42...

In my experience, mysterious shutdowns are most often due to power supply issues. If you have the option of trying a different power supply, I would start there.

Will do. If it fails, I'll figure out exactly which version works but it may take a few days as I can only test in the evenings.

That command doesn't show processes from container 154. It's simply matching anything in the output of ps with the text "154" anywhere on the line.

Correct, 4.14.20 (or later) completely resolve the issue.

This could indicate that the trigger for the issue is sensitive to timing / performance at the storage layer. With a smaller ARC (especially 1GB) performance will be degraded and the delays may reduce the occurrence of the issue. All of our environments run large ARCs (32GB minimum) tuned for...

Sure, with LVM you can create a snapshot but you'll need some free space to hold the write area while the filesystem is locked for the backup. LVM snapshots have a significant performance penalty so they may not be a great option depending on how much disk write your environments see. Another...

It's a kernel issue with network namespace cloning. Don't worry if that doesn't make sense. To confirm that you are having the same issue, wait for an LXC container to fail to start, then run: grep copy_net_ns /proc/*/stack If that returns anything, you're having the same issue. Proxmox is...

That sounds like an interaction with another app on your laptop/workstation -- like a Virus Scanner, Internet Protection Suite, Windows Firewall (accidentally blocked outbound at some point?), etc. Try disabling as much as you are comfortable doing and/or try from a different workstation if you...

If you're using ZFS, you can create snapshots of a live filesystem (no pause / downtime). Snapshots are always crash consistent and can be used for restore or rollback directly on the server. They are generated very quickly (seconds) and can be kept indefinitely (storage space dependent). You...

Ok, that's the expected results (Proxmox is running and has bound the port). Next confirm that systemd isn't dumping anything unusual for pveproxy: systemctl status pveproxy I'm suspicious that your browser may be in a bad state. Please try clearing the cache entirely for whatever browser...