Search results

  1. A

    kernel: BUG: soft lockup - CPU#6 stuck for 67s!

    I found the issue for the full disk. At one point my NFS share for the backups wasnt mounted on this server. So instead of throwing an error or something proxmox just did the backup on the local drive. When I rebooted it mounted the share on the same folder so I lost the ability to see what was...
  2. A

    kernel: BUG: soft lockup - CPU#6 stuck for 67s!

    Thanks it did work. But once again no big files. root@safecloud101:~# lsof |awk '{if($7 > 1048576) print $7/1048576 "MB" " " $9 }' | sort -n -u | tail 1.52544MB /lib/x86_64-linux-gnu/libc-2.13.so 1.95358MB /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0 2.75134MB /usr/bin/python2.7 3.98476MB...
  3. A

    kernel: BUG: soft lockup - CPU#6 stuck for 67s!

    And also if this can help this is what i see in the syslog tab on the web interface : Aug 20 17:07:18 safecloud101 pveproxy[3702]: worker 10819 started Aug 20 17:07:18 safecloud101 pveproxy[3702]: worker 10820 started Aug 20 17:07:18 safecloud101 pveproxy[10819]: error writing access log Aug 20...
  4. A

    kernel: BUG: soft lockup - CPU#6 stuck for 67s!

    Thanks for the quick reply and tips. I forgot about lsof. Since I can't find any specific large file I had to go through the whole output. But even than i could not find any open file larger than 20mb. Maybe I missed it. I found a little bash script that is supposed the only show the top 10 open...
  5. A

    kernel: BUG: soft lockup - CPU#6 stuck for 67s!

    Maybe I also realized that the hard drive is full on the server. Maybe there is a link between the 2 issues. Not sure why the hard drive is full. I use a NFS share for the Vms and backups. I just checked no vms are on the local hard drive. I used all the tricks I know to try to find big files...
  6. A

    kernel: BUG: soft lockup - CPU#6 stuck for 67s!

    Hi, I saw a few post with people with a similar problem but they seem to have this problem on their VMs. Me its on my PVE host. I get this when I have multiple containers using a lot of CPU. I decided to test it with running the stress command on multiple containers. Usually it takes about 12...
  7. A

    NFS permissions problem

    It worked! Thanks a lot!
  8. A

    NFS permissions problem

    What kind of info do you need? Its a Nexenta server. root@safecloud100:~# mount -v 192.168.52.31:/volumes/DefaultVolume/OPENVZ_SAFECLOUD2 on /mnt/pve/CT_hosting2 type nfs...
  9. A

    NFS permissions problem

    How about my problem? This guy just posted a completely different problem than mine in the thread I started!
  10. A

    NFS permissions problem

    Hi, I use a NFS share as storage for my openvz Containers. I have root access to the share : root@safecloud100:~# touch /mnt/pve/CT_Hosting/test.hosting root@MON1-STOR1:/export/home/admin# ls -l /volumes/DefaultVolume/OPENVZ_SAFECLOUD/ total 11 drwxr-xr-x 2 root nobody 2 Jul 7 11:37 dump...
  11. A

    Openvz creation very slow on nfs

    I saw a few threads about that but no one had the solution. Not sure if I was supposed to reply to those old threads. So I started a new one. I just installed 2 proxmox nodes that stores everything on a NAS(Nexenta) using NFS. After finally fixing up the permissions problems. I am able to create...

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!