Recent content by Jannoke

  1. J

    One zfs pool slows down all other zfs pools

    This is specified in the first post - Dual E5-2699v4. Cpu load is not high during write. Also the total speed of all pools can reach easliy over 4 figures.
  2. J

    One zfs pool slows down all other zfs pools

    All the good and constructive questions @UdoB and @chrcoluk . All pools are INDEPENDENT as stated. This is Zpool info for verification: root@bla:~# zpool status pool: zf_2tbnvme state: DEGRADED status: One or more devices could not be used because the label is missing or invalid...
  3. J

    One zfs pool slows down all other zfs pools

    Hey chatgpt - It's always grumpy people like you who come to comment. Question is about what happens if situation like this arises. Throwing stuff like make it a mirror is useless - I know how to make pools and what different raid levels are. Also this is not hw purchase thread so you why are we...
  4. J

    One zfs pool slows down all other zfs pools

    It might be more like zfs question, but maybe someone has had experience. So i have few zfs pools on one machine. One of pools is running on simple consumer (dramless) nvme's (3 disk raidz1, one disk missing).. There is only one virtual machine on that specific pool . While filling disk on that...
  5. J

    [SOLVED] Proxmox 8 to 9 - NFS on ZFS not working anymore

    I have now tested some things. 1) all my nodes have been restarted 3) it mounts, but it shows all contents with ???: root@blake:/mnt/pve/BackupData35# ls -lah ls: cannot access 'template': Stale file handle ls: cannot access 'longtime': Stale file handle ls: cannot access 'backup': Stale file...
  6. J

    [SOLVED] Proxmox 8 to 9 - NFS on ZFS not working anymore

    Have 4 node setup (1 node is just a miniPC for management). one node has ZFS volume with shared folder over NFS that other nodes use. After upgrade other nodes cannot access the NFS anymore. They kinda mount it and show files with "?" in beginning. But i cant read or write on volume. GUI...
  7. J

    Recommended amount of swap?

    For last 15 years i have been running all server swapless. There is no point to delay inevitable - if you are out of ram , you are out of ram. It will make everything slow, trash the hard drives (now we have ssd/nvme that actually wear out significally) . Better a horrible end than endless...
  8. J

    Windows 10 VM: Stop Code Hypervisor Error

    If you run nested virtualization and gpu passhtrough you suppose to set cpu = host, so that you will have all the needed cpu features
  9. J

    [SOLVED] Proxmox stuck after pve kernel reboot

    Thanks. this was it "indeed stuck" made me rethink everything. Switched to AMD 6600XT as it was quick way to find out and it worked straight away. There was additional problem going on - after installing pve kernel my network adapter changed from ens7s0 to ens6s0. This was the reason for no lan...
  10. J

    [SOLVED] Proxmox stuck after pve kernel reboot

    x470 Prime Pro AMD Ryzen 3900 4x32GB DDR4 3600Mhz RTX4060/GT730/RTX4070 ( tried multiple) Will get stuck after installing pve kernel: List of kernels. If i boot any other it works. This is debian 12 install, fully updated and following wiki
  11. J

    Node with question mark

    It means you have something that intermittently takes too much time to query for pvestatd daemon (mountpoint, some other info shown in gui). Usually slow disks or unreliable nfs mount.
  12. J

    "No IOMMU detected, please activate it." I did AFAIK.

    So tested all the bioses upto 3.1 and still no go - I would like to say that's something was broken in kernel , rather than MB support. Is there anything to try out that would be out of ordinary? EDIT: Got it working with 3.4 bios. Under PCI/PCIe settings there is SR-IOV . This needs to be...
  13. J

    "No IOMMU detected, please activate it." I did AFAIK.

    Same problem. I know it worked before (and it was 3.1 bios indeed). Now machines are in production and did not needed IOMMU until now. Bios has been updated to 3.4 in the meantime. X10DRi-T4+ MB which is basically same bios. All the same things done as OP. root@blake:~# dmesg | grep -e DMAR -e...
  14. J

    Proxmox VE 8.1 released!

    If you follow exactly the guide on ceph upgrade it is all good. I made the upgrade. Yes, it's ok to have some nodes running older version. It will report it on ceph status page also, but works. Make the upgrade as guide says and restart the daemons.