[PVE-User] i see call trace in log after make backup

[Serge]

On Tue, 7 Dec 2010 04:54:02 +0000
Dietmar Maurer <dietmar at proxmox.com> wrote:

>seems to be snapshot related. What kind on backup do you run 
>exactly - OpenVZ VM or KVM VM? What kind of storage is used?

backup both - OpenVZ and KVM
backup storage: type Directory, tnabled, Active, Not shared
mounted: /dev/mapper/vg0-backup on /backup type ext3 (rw,noatime)

>Does it work when you do not use snapshot mode?
I started backup in suspend mode, will reply again when it finished

>- Dietmar
>
>> -----Original Message-----
>> From: pve-user-bounces at pve.proxmox.com [mailto:pve-user-
>> bounces at pve.proxmox.com] On Behalf Of Serge
>> Sent: Dienstag, 07. Dezember 2010 00:54
>> To: pve-user at pve.proxmox.com
>> Subject: [PVE-User] i see call trace in log after make backup
>> 
>> Hello ,
>> 
>> On backup time i getting this error:
>> 
>> Dec  7 01:07:01 core vzdump[3711]: INFO: starting new backup job: vzdump --
>> quiet --snapshot --compress --stdexcludes --ionice 4 --storage backup --
>> mailto my at mail.com --all Dec  7 01:07:01 core vzdump[3711]: INFO: Starting
>> Backup of VM 101 (openvz) Dec  7 01:07:03 core kernel:
>> ext3_orphan_cleanup: deleting unreferenced inode 4892775 [skip...] Dec  7
>> 01:07:03 core kernel: ext3_orphan_cleanup: deleting unreferenced inode
>> 4890634 Dec  7 01:07:03 core kernel: EXT3-fs: dm-4: 15 orphan inodes deleted
>> Dec  7 01:07:03 core kernel: EXT3-fs: recovery complete.
>> Dec  7 01:09:59 core vzdump[3711]: INFO: Finished Backup of VM 101
>> (00:02:58) Dec  7 01:09:59 core vzdump[3711]: INFO: Starting Backup of VM
>> 102 (openvz) Dec  7 01:10:00 core kernel: ext3_orphan_cleanup: deleting
>> unreferenced inode 4890628 [skip...] Dec  7 01:10:00 core kernel:
>> ext3_orphan_cleanup: deleting unreferenced inode 4890634 Dec  7 01:10:00
>> core kernel: EXT3-fs: dm-4: 13 orphan inodes deleted Dec  7 01:10:00 core
>> kernel: EXT3-fs: recovery complete.
>> Dec  7 01:26:39 core kernel: INFO: task umount:6720 blocked for more than
>> 120 seconds.
>> Dec  7 01:26:39 core kernel: "echo 0 >
>> /proc/sys/kernel/hung_task_timeout_secs" disables this message.
>> Dec  7 01:26:39 core kernel: umount        D ffff880206663800     0  6720   3711
>> 0x00000000
>> Dec  7 01:26:39 core kernel: ffffffff81491c30 0000000000000086
>> 0000000000000000 0000000000000086 Dec  7 01:26:39 core kernel:
>> ffffffff8101657f 0000000000000086 000000000000fa40 ffff880099f5ffd8 Dec  7
>> 01:26:39 core kernel: 0000000000016940 0000000000016940 ffff880206663800
>> ffff880206663af8 Dec  7 01:26:39 core kernel: Call Trace:
>> Dec  7 01:26:39 core kernel: [<ffffffff8101657f>] ? sched_clock+0x5/0x8 Dec  7
>> 01:26:39 core kernel: [<ffffffff810b6892>] ? find_get_pages_tag+0x46/0xdd
>> Dec  7 01:26:39 core kernel: [<ffffffff8110b607>] ? bdi_sched_wait+0x0/0xe
>> Dec  7 01:26:39 core kernel: [<ffffffff8110b610>] ? bdi_sched_wait+0x9/0xe
>> Dec  7 01:26:39 core kernel: [<ffffffff81313d8f>] ? __wait_on_bit+0x41/0x70
[skip]

-- 
With Best Regards,
Serge

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.proxmox.com/pipermail/pve-user/attachments/20101207/50df61a8/attachment.sig>