Search results

  1. limit IO ( I/O) in LXC Container / ZFS

    Is the a tool which shows the actual disk IO on LXC / Container basis? iotop shows on process basis and so we do have to do cat /proc/NNNN/cgroup is there a tool which shows this values per container?
  2. limit IO ( I/O) in LXC Container / ZFS

    Thanks we will read. We see there is no out of the box solution. with KVM VM it is possible?
  3. limit IO ( I/O) in LXC Container / ZFS

    Is there a way in Proxmox to limit IO of LXC Container? It is on ZFS. Somethink like lxc config device set ci root limits.read 30MB lxc config device set ci root limits.write 10MB do not work. there is no lxc command. we did not find any in this forum. Thanks so much.
  4. [SOLVED] Limit IO ( I/O ) in LXC Container

    Is there a way in Proxmox to limit IO of LXC Container? It is on ZFS. Somethink like lxc config device set ci root limits.read 30MB lxc config device set ci root limits.write 10MB do not work. there is no lxc command. we did not find any in this forum. Thanks so much.
  5. Proxmox with Corosync+Ceph / how multible "routes" to ceph storage

    sadly not. we have in hosts 192.168.0.1 storage1 192.168.1.1 storage1 192.168.0.2 storage2 192.168.1.2 storage2 192.168.0.3 storage3 192.168.1.3 storage3 some weeks ago added all nodes to the cluster via pvecm add 192.168.0.1 -link0 192.168.1.2 -link1 192.168.0.2 Membership information...
  6. [SOLVED] failed to import 'rpool' on bootup after system update

    Same Problem with Proxmox 5->6 we change the /etc/default/zfs But update-initramfs not found. so if we reboot, nothing changed. what can we do?
  7. Proxmox with Corosync+Ceph / how multible "routes" to ceph storage

    Thanks. "Check that you have both IPs in your /etc/hosts and you can login with ssh from both networks." do you mean to hosts? 192.168.0.2 storage2 192.168.1.2 storage2 This does not help. May Proxmox GUI think the nodes are on 192.168.0.N .. in GUI cluster -> Overview the nodes are listed...
  8. Corosync redundancy over second nic with public ip

    Thanks. Only Corosync works well. Thanks, IPs are examples. Corosyn all is fine with tinc now. But we have other "Problems". We use eth0 for corosync and eth1 is used for proxmox internal net (communicate to hosts / nodes) and it is internal net for KVM VMs. So if eth1 is down, corosync eth1...
  9. Corosync redundancy over second nic with public ip

    Thanks. Any suggestions with VPN? We testet with tinc. But it high cpu if we test high traffic on this net. 2nd: Sadly we have no access to infrastructure in our datacenter. So VPN is the only way we see.
  10. Proxmox with Corosync+Ceph / how multible "routes" to ceph storage

    We have 3 nodes with 2 private nics eth0 - 192.168.0.0/24 corosync link 1 , ceph storage, proxmox gui and clustercommunication f.e migration eth1 - 192.168.1.0/24 corosync link 0 we have set corosync nodes to have 2 rings (ring0_addr: 192.168.1.2 / ring1_addr: 192.168.0.2). this works well...
  11. [SOLVED] many [KNET ] pmtud: possible MTU misconfiguration detected

    ok, but with ifconfig inetVPN mtu 1445 it works. any objections against the use of MTU 1445 ?
  12. Corosync redundancy over second nic with public ip

    We use proxmox 6 , this is with corosync 3 we think.
  13. [SOLVED] many [KNET ] pmtud: possible MTU misconfiguration detected

    proxmox-ve: 6.0-2 (running kernel: 5.0.15-1-pve) pve-manager: 6.0-4 (running version: 6.0-4/2a719255) pve-kernel-5.0: 6.0-5 pve-kernel-helper: 6.0-5 pve-kernel-4.15: 5.4-6 pve-kernel-5.0.15-1-pve: 5.0.15-1 pve-kernel-4.15.18-18-pve: 4.15.18-44 ceph: 14.2.1-pve2 ceph-fuse: 14.2.1-pve2 corosync...
  14. [SOLVED] many [KNET ] pmtud: possible MTU misconfiguration detected

    ifconfig inetVPN mtu 1445 seems solve the problem. we like to understand what is the reason? tinc PING and PONG, so may the packege are to big? ifconfig inetVPN mtu 1500 produce the error see above
  15. [SOLVED] many [KNET ] pmtud: possible MTU misconfiguration detected

    We get many of this errors. Aug 02 07:41:54 storage1 corosync[3283]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size. Aug 02 07:41:54 storage1 corosync[3283]: [KNET ]...
  16. Corosync redundancy over second nic with public ip

    we have ips like 52.78.. 52.76 and so on
  17. Corosync redundancy over second nic with public ip

    We have 3 Nodes. Each has eth0 with public ip and eth1 with private. no more NICs possible. privatenet: 192.168.0.0 - eth0 public: different public ips, bit all in same datacenter - eth1 we are not able to change this. 2 private networks are not possible due datacenter restrictions. we set the...

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE 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 your own in 60 seconds.

Buy now!