Definitly something wrong with v4

[ozgurerdogan]

At ovh I have a test machine, and same machine can backup to nfs, ftp, or cifs with no problem with v3. But with version 4.2 it hangs and can not backup. I am pretty sure now something is wrong with version 4.2 and many people complaning it.

I hope someone find a way to backup to ftp mount as it is important to keep backup seperate place.

 

[tom]

this is a quite general statement with no content. Just for a couple of user have issues, so I am pretty sure that your problems are caused by a configuration problem.

if you found a bug, pleaes report it via https://bugzilla.proxmox.com

 

[ozgurerdogan]

Well you might be right. But there is no content in sys logs. It just hangs and I have to cancel it. If you advise something, I would be happy to try it.

 

[ozgurerdogan]

But sometimes I get these error in logs after it hangs:

Jun 12 19:34:20 vztlfr3 kernel: INFO: task task UPID:vztlf:7215 blocked for more than 120 seconds.
Jun 12 19:34:20 vztlfr3 kernel: Tainted: P O 4.4.8-1-pve #1
Jun 12 19:34:20 vztlfr3 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jun 12 19:34:20 vztlfr3 kernel: task UPID:vztlf D ffff8802c7d53da8 0 7215 1 0x00000004
Jun 12 19:34:20 vztlfr3 kernel: ffff8802c7d53da8 ffff8806cbbe0050 ffff88085b920dc0 ffff8803cfc244c0
Jun 12 19:34:20 vztlfr3 kernel: ffff8802c7d54000 ffff8802c7d53de8 ffff8808206b2bc0 ffff8806cbbe0000
Jun 12 19:34:20 vztlfr3 kernel: ffff88039f844280 ffff8802c7d53dc0 ffffffff81844885 ffff8808206b2af0
Jun 12 19:34:20 vztlfr3 kernel: Call Trace:
Jun 12 19:34:20 vztlfr3 kernel: [<ffffffff81844885>] schedule+0x35/0x80
Jun 12 19:34:20 vztlfr3 kernel: [<ffffffff81310d7f>] request_wait_answer+0x12f/0x280
Jun 12 19:34:20 vztlfr3 kernel: [<ffffffff810c3702>] ? __wake_up_common+0x52/0x90
Jun 12 19:34:20 vztlfr3 kernel: [<ffffffff810c3d80>] ? wait_woken+0x90/0x90
Jun 12 19:34:20 vztlfr3 kernel: [<ffffffff81310f39>] __fuse_request_send+0x69/0x90
Jun 12 19:34:20 vztlfr3 kernel: [<ffffffff81310f87>] fuse_request_send+0x27/0x30
Jun 12 19:34:20 vztlfr3 kernel: [<ffffffff8131a188>] fuse_flush+0x148/0x190
Jun 12 19:34:20 vztlfr3 kernel: [<ffffffff8120982f>] filp_close+0x2f/0x70
Jun 12 19:34:20 vztlfr3 kernel: [<ffffffff8122b0b3>] __close_fd+0xa3/0xc0
Jun 12 19:34:20 vztlfr3 kernel: [<ffffffff81209893>] SyS_close+0x23/0x50
Jun 12 19:34:20 vztlfr3 kernel: [<ffffffff818489b6>] entry_SYSCALL_64_fastpath+0x16/0x75

 

[tom]

looks like an issue on the storage.

please add your complete details about the physical storage (hardware) and the configuration involved.

 

[ozgurerdogan]

This is standart ovh dedicated server. No raid array. And latest proxmox version. I tried ext3, ext4 and xfs but none of them made any difference. I also tried NFSi Cifs and ftp mounts. I am having same issue with 3 different server. But with proxmox v3 all backup gooes well.
Intel D-1520 4c/8t 2.2 GHz/2.6 GHz
RAM: 32 GB DDR4 ECC 2133 MHz
Disks: 2x 2 TB SATA3

proxmox-ve: 4.2-52 (running kernel: 4.4.8-1-pve)
pve-manager: 4.2-11 (running version: 4.2-11/2c626aa1)
pve-kernel-4.4.8-1-pve: 4.4.8-52
pve-kernel-4.2.8-1-pve: 4.2.8-41
lvm2: 2.02.116-pve2
corosync-pve: 2.3.5-2
libqb0: 1.0-1
pve-cluster: 4.0-40
qemu-server: 4.0-79
pve-firmware: 1.1-8
libpve-common-perl: 4.0-67
libpve-access-control: 4.0-16
libpve-storage-perl: 4.0-51
pve-libspice-server1: 0.12.5-2
vncterm: 1.2-1
pve-qemu-kvm: 2.5-19
pve-container: 1.0-67
pve-firewall: 2.0-29
pve-ha-manager: 1.0-31
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u2
lxc-pve: 1.1.5-7
lxcfs: 2.0.0-pve2
cgmanager: 0.39-pve1
criu: 1.6.0-1
zfsutils: 0.6.5-pve9~jessie

 

[tom]

And all your problems are related to the provided backup storage from OVH? (available via cifs, nfs and ftp)

As you have two disks, I suggest you backup to the second disk and then upload the files to the remote backup storage.

 

[ozgurerdogan]

You might be right. Thing is upload speed is only 2-4 MBps to upload storage. Maybe that is causing system hang. So even manually uploading is slow.

 

[LnxBil]

Did I understand you correctly that you upload your files via FTP to a off-site backup location directly via fuse?

• Hopefully, this setup is fully-encrypted, otherwise this is extremely dangerous!
• Try to use backup to local disk and upload via post-backup-hook to your secured ftp location.