Still getting Kernal Hangs on backup

[Milkwyrm]

I have a fully up to date 2.1 install that is hanging on backup still. this time with LZOP
It is a standalone machine backing up to an NFS share on a FreeNAS box.

EDIT: I did complete a backup without incident using GZIP

Apr 30 16:48:21 Server01 kernel: INFO: task lzop:7857 blocked for more than 120 seconds.
Apr 30 16:48:21 Server01 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Apr 30 16:48:21 Server01 kernel: lzop D ffff8802376ee400 0 7857 7855 0 0x00000000
Apr 30 16:48:21 Server01 kernel: ffff8802186ddb68 0000000000000046 ffff8802186ddae8 ffffffffa04dbec0
Apr 30 16:48:21 Server01 kernel: ffff8802685779c0 ffff88027cbf6280 ffff880218000001 ffffffff81123975
Apr 30 16:48:21 Server01 kernel: ffffffffa04ea1a8 ffff8802376ee9a0 ffff8802186ddfd8 ffff8802186ddfd8
Apr 30 16:48:21 Server01 kernel: Call Trace:
Apr 30 16:48:21 Server01 kernel: [<ffffffff81123975>] ? mempool_alloc+0x65/0x150
Apr 30 16:48:21 Server01 kernel: [<ffffffff81120bf0>] ? sync_page+0x0/0x50
Apr 30 16:48:21 Server01 kernel: [<ffffffff81512663>] io_schedule+0x73/0xc0
Apr 30 16:48:21 Server01 kernel: [<ffffffff81120c2d>] sync_page+0x3d/0x50
Apr 30 16:48:21 Server01 kernel: [<ffffffff8151302f>] __wait_on_bit+0x5f/0x90
Apr 30 16:48:21 Server01 kernel: [<ffffffff81120de3>] wait_on_page_bit+0x73/0x80
Apr 30 16:48:21 Server01 kernel: [<ffffffff810944f0>] ? wake_bit_function+0x0/0x40
Apr 30 16:48:21 Server01 kernel: [<ffffffff811392f5>] ? pagevec_lookup_tag+0x25/0x40
Apr 30 16:48:21 Server01 kernel: [<ffffffff811212eb>] wait_on_page_writeback_range+0xfb/0x190
Apr 30 16:48:21 Server01 kernel: [<ffffffff811214b8>] filemap_write_and_wait_range+0x78/0x90
Apr 30 16:48:21 Server01 kernel: [<ffffffff811bf75a>] vfs_fsync_range+0xba/0x190
Apr 30 16:48:21 Server01 kernel: [<ffffffff811bf89d>] vfs_fsync+0x1d/0x20
Apr 30 16:48:21 Server01 kernel: [<ffffffffa049f920>] nfs_file_flush+0x70/0xa0 [nfs]
Apr 30 16:48:21 Server01 kernel: [<ffffffff8118bd5c>] filp_close+0x3c/0x90
Apr 30 16:48:21 Server01 kernel: [<ffffffff8106dddf>] put_files_struct+0x7f/0xf0
Apr 30 16:48:21 Server01 kernel: [<ffffffff8106dea3>] exit_files+0x53/0x70
Apr 30 16:48:21 Server01 kernel: [<ffffffff8106fa8d>] do_exit+0x1ad/0x920
Apr 30 16:48:21 Server01 kernel: [<ffffffff81070258>] do_group_exit+0x58/0xd0
Apr 30 16:48:21 Server01 kernel: [<ffffffff810702e7>] sys_exit_group+0x17/0x20
Apr 30 16:48:21 Server01 kernel: [<ffffffff8100b182>] system_call_fastpath+0x16/0x1b

Any ideas how I can prevent this..

root@Server01:~# pveversion -v
pve-manager: 2.1-1 (pve-manager/2.1/f9b0f63a)
running kernel: 2.6.32-11-pve
proxmox-ve-2.6.32: 2.0-66
pve-kernel-2.6.32-10-pve: 2.6.32-63
pve-kernel-2.6.32-11-pve: 2.6.32-66
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.3-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.8-3
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.7-2
pve-cluster: 1.0-26
qemu-server: 2.0-39
pve-firmware: 1.0-15
libpve-common-perl: 1.0-27
libpve-access-control: 1.0-21
libpve-storage-perl: 2.0-18
vncterm: 1.0-2
vzctl: 3.0.30-2pve5
vzprocps: 2.0.11-2
vzquota: 3.0.12-3
pve-qemu-kvm: 1.0-9
ksm-control-daemon: 1.1-1

root@Server01:~# pveperf
CPU BOGOMIPS: 36261.44
REGEX/SECOND: 901260
HD SIZE: 94.49 GB (/dev/mapper/pve-root)
BUFFERED READS: 232.54 MB/sec
AVERAGE SEEK TIME: 6.76 ms
FSYNCS/SECOND: 2775.56
DNS EXT: 4.17 ms
DNS INT: 0.94 ms

 

[taspenatu]

The kernel message is only an information that the lzop process is very slow. It will disappear if your storage gets fast.

We had similar problems with a Thecus N8800 and NFS3.

Try to use NFS4. FreeNAS 8 should support it.
But you have to create the storage via command line. The web interface won't work.

create /etc/nfsmounts.conf

[ NFSMount_Global_Options ]
        vers=4

and then the storage

# pvesh create /storage -storage <storageid> -type nfs -export <nfs export> -server <freenas server> -path /mnt/pve/<storageid>

Regards
Frank

 

[GT1]

Try to use NFS4. FreeNAS 8 should support it.

it does not.

 

[taspenatu]

it does not.

Ok, than try to use a CIFS share as described here http://pve.proxmox.com/wiki/Storage...MBa.29_share_on_Proxmox_VE_via_.2Fetc.2Ffstab

And please include the mountpoint into your monitoring since no remount will occur on errors.