Proxmox 5.2 VM stalled during restore backup

Morbious

New Member
Feb 27, 2018
12
0
1
46
Hi,

I have problem with restoring machines on proxmox5.2 with kernel pve-kernel-4.15.17-1-pve.
Problem is that when I restore machine from backup everything is going all right but when task gets 100% it stalled and VM machines that are running got stalled. Everything is freezing.

After few minutes each VM starts working properly, but in logs I get :
[168958.670230] INFO: task monit:2443 blocked for more than 120 seconds.
[168958.670730] Not tainted 4.4.0-131-generic #157-Ubuntu
[168958.671155] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[168958.671776] monit D ffff880a0a817dd0 0 2443 1 0x00000000
[168958.671779] ffff880a0a817dd0 ffff880a081e7888 ffff880a10962640 ffff880a0bf1cc80
[168958.671781] ffff880a0a818000 000000000000a567 ffff880a081e7888 ffff880a081e7824
[168958.671783] ffff880a0a817e18 ffff880a0a817de8 ffffffff8184f0e5 ffff880a081e7800
[168958.671785] Call Trace:
[168958.671789] [<ffffffff8184f0e5>] schedule+0x35/0x80
[168958.671791] [<ffffffff812fa849>] jbd2_log_wait_commit+0xa9/0x130
[168958.671793] [<ffffffff810c80b0>] ? wake_atomic_t_function+0x60/0x60
[168958.671796] [<ffffffff812fd45c>] jbd2_complete_transaction+0x5c/0xa0
[168958.671800] [<ffffffff8129ce36>] ext4_sync_file+0x1e6/0x350
[168958.671802] [<ffffffff8124a2ee>] vfs_fsync_range+0x4e/0xb0
[168958.671804] [<ffffffff8124a3ad>] do_fsync+0x3d/0x70
[168958.671806] [<ffffffff8124a650>] SyS_fsync+0x10/0x20
[168958.671807] [<ffffffff8185328e>] entry_SYSCALL_64_fastpath+0x22/0xc1


In dom0 I get:

[Wed Jan 2 11:49:28 2019] INFO: task kvm:6369 blocked for more than 120 seconds.
[Wed Jan 2 11:49:28 2019] Tainted: P O 4.13.13-2-pve #1
[Wed Jan 2 11:49:28 2019] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[Wed Jan 2 11:49:28 2019] kvm D 0 6369 1 0x00000000
[Wed Jan 2 11:49:28 2019] Call Trace:
[Wed Jan 2 11:49:28 2019] __schedule+0x3cc/0x860
[Wed Jan 2 11:49:28 2019] schedule+0x36/0x80
[Wed Jan 2 11:49:28 2019] schedule_timeout+0x1da/0x350
[Wed Jan 2 11:49:28 2019] ? dm_make_request+0x74/0xc0
[Wed Jan 2 11:49:28 2019] io_schedule_timeout+0x1e/0x50
[Wed Jan 2 11:49:28 2019] ? io_schedule_timeout+0x1e/0x50
[Wed Jan 2 11:49:28 2019] wait_for_completion_io+0xb4/0x140
[Wed Jan 2 11:49:28 2019] ? wake_up_q+0x80/0x80
[Wed Jan 2 11:49:28 2019] submit_bio_wait+0x68/0x90
[Wed Jan 2 11:49:28 2019] blkdev_issue_flush+0x5c/0x90
[Wed Jan 2 11:49:28 2019] blkdev_fsync+0x35/0x50
[Wed Jan 2 11:49:28 2019] vfs_fsync_range+0x4b/0xb0
[Wed Jan 2 11:49:28 2019] do_fsync+0x3d/0x70
[Wed Jan 2 11:49:28 2019] SyS_fdatasync+0x13/0x20
[Wed Jan 2 11:49:28 2019] entry_SYSCALL_64_fastpath+0x1e/0xa9

I have same the machine but with different version of proxmox 5.1 which is running all right.
I change kernel to old version (4.13) which is running properly on proxmox 5.1 but it didn;t help.
 
I would recommended to Upgrade your PVE on the newest Version, then Reboot and check again if the Problem is persistent. Most of such Problems are resolve by upgrading and Reboot.
 
I upgraded to 5.3 and still have the same problem.
Even copying trough network machine gets stalled for few minutes and than is running again...
On the same machine (for dom0) with proxmox 5.1 everything is working all right - fast and smoth...
I'm in dead point what can be wrong.
 

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!