Search results

  1. J

    Lazy KSM after upgrading to kernel 4.13.13-5

    Hello Have anyone else noticed 'lazyness' in KSM with kernel pve 4.13.13-5. May patches for Meltdown and Spectre have any impact for this? Before we could share up to 2TB of memory in our test cluster. Now the sharing is very slow and it can share only about 100GB in whole cluster. Cluster...
  2. J

    ocfs2 kernel bug

    Hello again, After five hours of testing, one node rebooted by unknown reason, probably because of out of memory. The cluster continued working fine and faulty node joined back into cluster without problems. No ocfs2 releated errors or warnings were found from /var/log/messages nor syslog. I...
  3. J

    ocfs2 kernel bug

    Hello We have similar problems with our 8-node OCFS2 cluster used in our lab Proxmox VE. The latest kernel 4.13.13-5 made things a little bit more stable, but still our nodes crashed randomly under high IO load. We can have up to 50 our stresstest VM's and after a while (30min to 2hours) node...
  4. J

    Container bind mounts via api

    Hi I have nfs mount in a proxmox server. I would like to bind it to container via json api. I have managed to bind the nfs directory into container by configuring it by hand into file /etc/pve/lxe/<vmid>.conf And everything works fine. When i try to create new container with mp0 mountpoint...

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!