Search results

  1. L

    [SOLVED] udev malfunction (udisksd high cpu load)

    Fix the problem in my case the following string: ACTION=="add|change", KERNEL=="dm-*", OPTIONS:="nowatch" in file /etc/udev/rulesd/90-fixdm.rules and then command: systemctl restart udev
  2. L

    [SOLVED] udisksd using lots of CPU

    Fix the problem in my case the following string: ACTION=="add|change", KERNEL=="dm-*", OPTIONS:="nowatch" in file /etc/udev/rulesd/90-fixdm.rules and then command: systemctl restart udev
  3. L

    zfs error: cannot destroy : dataset is busy

    Be carefull and do not destroy needed disk, as it was in my case:(. And now I know about is my backup working or not.
  4. L

    zfs error: cannot destroy : dataset is busy

    I have had the similar situation on test server with undestroyable "vm-137-disk-2" that was not mount, without any snapshots and VM 137 did not exist from long ago: >zfs destroy -r -f rpool/data/vm-137-disk-2 cannot destroy 'rpool/data/vm-137-disk-2': dataset is busy I have fixed this with...

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!