Search results

Finally I tried Proxmox 7.1 where this solution is not enough. Googling further I came across the solution. Setting children_max=8 within /etc/udev/udev.conf solved the problem.

Thanks for the fix @gurubert, worked for me too.

I use shared LVM on top of a number of FC/SAS-connected storages (one VG per LUN though). Works like a charm.

I'm not quite sure this issue applies only to the very latest version. The following is seen in the graphite relay log

Hello, Carbon (particularly carbon-c-relay) expects one metric per line. Current PVE implementation breaks this rule. The following patch corrects this bug --- /usr/share/perl5/PVE/Status/Graphite.pm.orig 2016-04-26 20:03:02.961141497 +0000 +++ /usr/share/perl5/PVE/Status/Graphite.pm...

In my case it doesn't matter where I mount nfs share. At least for now. Yes. I'm absolutely sure this script works when it is called from hosts command line. This share can be mounted as storage at Datacenter level.

Yeah. I understand that. Using the bind mounting of storage is the most simple and transparent way. Thank you

I mistakenly replaced "pre-start" with "pre-mount" which gave the described result. pre-start shows network configured and even shows exports on remote hosts. But little did it help mounting: ip -4 a [snip] 7: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc mq state UP group default qlen...

Well, I can accept NFS storage as a work-around. Thank you. Can I hope your team will ever implement pre-start hook functionality for pct? (:

According to lxc.container.conf manual page lxc.hook.pre-start is "A hook to be run in the host's namespace". But from what I see it's not quite so: 1. /etc/pve/lxc/125.conf contains the following line lxc.hook.pre-mount: /etc/pve/lxc/${LXC_NAME}.mount 2. /etc/pve/lxc/125.mount is a shell...