| Huge system load with vzdump --snap [message #31025] |
Fri, 13 June 2008 22:10 |
seanfulton
Messages: 105
Registered: May 2007
|
Senior Member |
|
|
I'm wondering if anyone else is experiencing really high system loads while running vzdump with the --snap option. I've seen the load progressively climb to well over 100 doing repeated backups (backing up 10 running VEs) and am wondering if anyone else is experiencing a similar problem.
I am using the 2.6.18-53.1.19.el5.028stab053.14 kernel and 1.0.2 version of vzdump.
Coincidentally, I've had problems like the following:
EXT3 FS on dm-1, internal journal
ext3_orphan_cleanup: deleting unreferenced inode 28445005
ext3_orphan_cleanup: deleting unreferenced inode 48877477
ext3_orphan_cleanup: deleting unreferenced inode 28444936
ext3_orphan_cleanup: deleting unreferenced inode 28444580
ext3_orphan_cleanup: deleting unreferenced inode 28444579
ext3_orphan_cleanup: deleting unreferenced inode 28444285
ext3_orphan_cleanup: deleting unreferenced inode 32772
ext3_orphan_cleanup: deleting unreferenced inode 32771
ext3_orphan_cleanup: deleting unreferenced inode 32770
ext3_orphan_cleanup: deleting unreferenced inode 32769
ext3_orphan_cleanup: deleting unreferenced inode 16187404
ext3_orphan_cleanup: deleting unreferenced inode 32983200
ext3_orphan_cleanup: deleting unreferenced inode 32983532
ext3_orphan_cleanup: deleting unreferenced inode 32983526
ext3_orphan_cleanup: deleting unreferenced inode 32983232
ext3_orphan_cleanup: deleting unreferenced inode 32983201
ext3_orphan_cleanup: deleting unreferenced inode 1425413
ext3_orphan_cleanup: deleting unreferenced inode 33263485
ext3_orphan_cleanup: deleting unreferenced inode 11272212
ext3_orphan_cleanup: deleting unreferenced inode 33672865
ext3_orphan_cleanup: deleting unreferenced inode 46940183
ext3_orphan_cleanup: deleting unreferenced inode 33522372
ext3_orphan_cleanup: deleting unreferenced inode 33522371
ext3_orphan_cleanup: deleting unreferenced inode 33522370
ext3_orphan_cleanup: deleting unreferenced inode 33522369
ext3_orphan_cleanup: deleting unreferenced inode 32538629
ext3_orphan_cleanup: deleting unreferenced inode 32538628
ext3_orphan_cleanup: deleting unreferenced inode 32538627
ext3_orphan_cleanup: deleting unreferenced inode 32538626
ext3_orphan_cleanup: deleting unreferenced inode 32538625
ext3_orphan_cleanup: deleting unreferenced inode 52986475
ext3_orphan_cleanup: deleting unreferenced inode 52986474
ext3_orphan_cleanup: deleting unreferenced inode 52986330
ext3_orphan_cleanup: deleting unreferenced inode 52986184
ext3_orphan_cleanup: deleting unreferenced inode 48857586
ext3_orphan_cleanup: deleting unreferenced inode 48857575
ext3_orphan_cleanup: deleting unreferenced inode 48857574
ext3_orphan_cleanup: deleting unreferenced inode 48857573
ext3_orphan_cleanup: deleting unreferenced inode 48857572
EXT3-fs: dm-1: 39 orphan inodes deleted
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
reported in dmesg and I believe those are related to the nightly backuups (they come up with great regularity).
I am using ATA100 drives connected to a dual XEON machine.
sean
|
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
