Recent content by Nemesiz

  1. N

    Is this a ZFS related problem?

    Temporary: #swapoff -a Permanently: edit /etc/fstab
  2. N

    Very specific setup, needing very specific advisory

    Samba ?
  3. N

    CEPH setup

    SSD as DB/WAL for SSD may not give expected performance. What was Ceph slow performance at the beginning ( not disk itself )? As of small/lab Ceph cluster I do not see much lose of using EC vs replica.
  4. N

    CEPH setup

    You told it is slow but did not told the numbers. With ceph you can create CRUSH rules where pool must save data. You can create new class, new root to distribute the data.
  5. N

    Is this a ZFS related problem?

    Hi, looking at given issue link try to turn off swap
  6. N

    STEC ssd disk wearout show in GUI

    Hello, I use a bunch of STEC ssd. They are old but runs good and have high endurance. Regular smartctl doesn't return all needed information. Proxmox GUI show wearout as N/A. To get more information I use #sdmcmd64 In Diskmanage.pm get_wear_leveling_info try to detect from regular smart fields...
  7. N

    [bug] [WebUI] Ceph OSD control and multiple roots

    This is my types # types type 0 osd type 1 osd-link type 2 disk-group type 3 host type 4 chassis type 5 rack type 6 row type 7 pdu type 8 pod type 9 room type 10 datacenter type 11 zone type 12 region type 13 root If OSD belongs directly to HOST Proxmox GUI show active control buttons of OSD...
  8. N

    CEPH setup

    You can rise osd_memory_target but HP PM9A3 is more for read intensive. Try not to use them to see how will Ceph performance.
  9. N

    High Latency on a new HDD-disks (ceph)

    Take IO metering tools and watch HDD load
  10. N

    Cannot migrate VM, because HA resource vm is not allowed

    To recreate bug I delete all HA rules and created again. From that moment all server shutdown went very well.
  11. N

    High Latency on a new HDD-disks (ceph)

    Try to disable write-cache for HDD
  12. N

    Cannot migrate VM, because HA resource vm is not allowed

    VM could exist only in one HA rule. It should be a bug.
  13. N

    Cannot migrate VM, because HA resource vm is not allowed

    It require to be upgraded. In node shutdown VM should be moved to another node by HA rule priority but it stays blocked.
  14. N

    Cannot migrate VM, because HA resource vm is not allowed

    Could it be related to this? https://github.com/proxmox/pve-ha-manager/commit/dc200f10963fcb7ca81ea05246ce69bf03117629 # pveversion -v proxmox-ve: 9.2.0 (running kernel: 7.0.12-1-pve) pve-manager: 9.2.3 (running version: 9.2.3/d0fde103346cf89a) proxmox-kernel-helper: 9.2.0 proxmox-kernel-7.0...
  15. N

    Cannot migrate VM, because HA resource vm is not allowed

    Hello, I'm not sure which update caused this issue, but using HA Affinity Rules I can't migrate a VM to another node. In migration dialog I see: Cannot migrate VM, because HA resource vm:121 is not allowed on the selected target node. Using console # qm migrate 121 nmz-cl-1 --online...
Top Bottom
Back