Search results

  1. T

    Shared LVM on iSCSI: how safe is it?

    That link no longer works. There is Proxmox Cluster File System (pmxcfs). I tested lvm on iscsi on my home cluster and seems to work fine, but that does not really guarantee it's safe for production.
  2. T

    /proc/spl/kstat/zfs/[poolname]/io file missing

    On Linux it's in /proc/spl/kstat/zfs/<poolname>/iostats but that doesn't seem very useful.
  3. T

    Hotplug memory limits total memory to 44GB

    You'd have to rmmod vhost, but vhost_net depends on that etc.
  4. T

    Balooning problem - "Out of puff!" but host has plenty of free memory

    The secret is in /etc/ksmtuned.conf setting KSM_THRES_COEF=20 which reserves 20% of ram for your host OS. Requires restarting ksmtuned.service. I'm not sure if that's always safe when VM's are running.
  5. T

    Why does Proxmox use swap when I have ~170 GiB of RAM available?

    A totally different explanation could be NUMA. If you have multiple CPUs and VMs using lots of memory, it could be that one CPU is low on memory. See for example https://sitano.github.io/2014/08/20/numa-swap/
  6. T

    How to get the exactly backup size in proxmox backup

    Yes i added just that, will submit when tested
  7. T

    How to get the exactly backup size in proxmox backup

    Peter Maloney did some more work on estiname-size.py, also adding optional json output: https://github.com/petermaloney/pve/blob/main/pbs/estiname-size.py
  8. T

    [SOLVED] I have this error during remote sync

    Manually changing location or the path in /etc/proxmox-backup/datastore.cfg will also cause this. Remember to restart proxmox-backup-proxy.service
  9. T

    vm resize disk offline error

    Right, in our case qm resize[\ICODE], but that works. Since that cluster is due for upgrade i suppose it's a problem that will go away. Thanks.
  10. T

    vm resize disk offline error

    Works, but a bit slower: avg 0.51 seconds
  11. T

    vm resize disk offline error

    When trying to grow one particular disk for a VM. The "please wait" takes about 4 seconds. Between 0.025 and 0.040 seconds. Maybe there's some lock involved somewhere?
  12. T

    vm resize disk offline error

    For people looking for "Could not determine current size of volume", this is the place :) I'm having the same problem with a qcow on an NFS mount, qemu-img info returns instantly with correct data.
  13. T

    [solved] Remove Orphaned Snapshot?

    Great, that does the trick indeed, just threw warning like lvremove snapshot 'pve/snap_vm-101-disk-0_premigration' error: Failed to find logical volume "pve/snap_vm-101-disk-0_premigration" which was the problem indeed
  14. T

    VMs freezing and unreachable when backup server is slow

    Any way to increase the cache size?
  15. T

    vzdump - bwlimit only on write speeds?

    I tried setting that for pbs storage, but getting errors like "update storage failed: unexpected property 'bwlimit'" Not supported for PBS?
  16. T

    vzdump - bwlimit only on write speeds?

    So how was it solved?
  17. T

    [SOLVED] Ceph HEALTH_WARN: no active mgr

    In my case i got it fixed by running on one node: pveceph mgr destroy pvetest1 pveceph mgr create and waited a bit. After this the "got timeout(500)" and other timeout issues went away.
  18. T

    VMs freezing and unreachable when backup server is slow

    I had similar issues with a bad/slow connection to PBS
  19. T

    VMs freezing and unreachable when backup server is slow

    Does this mean adjusting bwlimit might help?
View older results
Top Bottom
Back