EXT4 error: no quota engine running

[gnumdk]

Hello,

i've got this errors when i run dmesg, is this important ? What does it mean ?

VZDQ: Tried to clean orphans on qmblk with 1 state
BUG: Quota files for 111 are broken: no quota engine running
EXT4-fs (dm-2): ext4_orphan_cleanup: deleting unreferenced inode 8259914
VZDQ: Tried to clean orphans on qmblk with 1 state
BUG: Quota files for 111 are broken: no quota engine running
EXT4-fs (dm-2): ext4_orphan_cleanup: deleting unreferenced inode 8259913
VZDQ: Tried to clean orphans on qmblk with 1 state
BUG: Quota files for 108 are broken: no quota engine running
EXT4-fs (dm-2): ext4_orphan_cleanup: deleting unreferenced inode 7475237
VZDQ: Tried to clean orphans on qmblk with 1 state
BUG: Quota files for 108 are broken: no quota engine running
EXT4-fs (dm-2): ext4_orphan_cleanup: deleting unreferenced inode 7475236
EXT4-fs (dm-2): 4 orphan inodes deleted
EXT4-fs (dm-2): recovery complete

 

[dietmar]

I assume you run vzdump in snapshot mode?

 

[gnumdk]

I assume you run vzdump in snapshot mode?

Yes, backup is configured in snapshot mode...

http://forum.openvz.org/index.php?t=msg&goto=46009&

 

[dietmar]

Does the backup complete successfully? If not, I suggest to use ext3 instead of ext4 (default for pve)

 

[tom]

see also this http://bugzilla.openvz.org/show_bug.cgi?id=2085

 

[mir]

Just out of curiosity. Has anyone done some performance comparisons regarding using ext3 or ext4 on proxmox 2?

 

[jazzl0ver]

Faced same issue on Proxmox 3.0:

Jun 9 00:30:01 vm-box-3 vm-box-3 vzdump[636151]: <root@pam> starting task UPID:vm-box-3:0009B4F9:024CA8CC:51B39449:vzdump::root@pam:
Jun 9 00:30:01 vm-box-3 vm-box-3 vzdump[636153]: INFO: starting new backup job: vzdump 101 100 103 104 105 107 112 113 115 118 117 --quiet 1 --mode snapshot --compress lzo --storage trendy-images
Jun 9 00:30:01 vm-box-3 vm-box-3 pmxcfs[2629]: [status] notice: received log
Jun 9 00:30:01 vm-box-3 vm-box-3 vzdump[636153]: INFO: Starting Backup of VM 101 (openvz)
Jun 9 00:30:03 vm-box-3 vm-box-3 kernel: VZDQ: Tried to clean orphans on qmblk with 1 state
Jun 9 00:30:03 vm-box-3 vm-box-3 kernel: BUG: Quota files for 112 are broken: no quota engine running
Jun 9 00:30:03 vm-box-3 vm-box-3 kernel: EXT4-fs (dm-1): ext4_orphan_cleanup: deleting unreferenced inode 42995786
Jun 9 00:30:03 vm-box-3 vm-box-3 kernel: VZDQ: Tried to clean orphans on qmblk with 1 state
Jun 9 00:30:03 vm-box-3 vm-box-3 kernel: BUG: Quota files for 101 are broken: no quota engine running
Jun 9 00:30:03 vm-box-3 vm-box-3 kernel: EXT4-fs (dm-1): ext4_orphan_cleanup: deleting unreferenced inode 39721125
Jun 9 00:30:03 vm-box-3 vm-box-3 kernel: VZDQ: Tried to clean orphans on qmblk with 1 state
Jun 9 00:30:03 vm-box-3 vm-box-3 kernel: BUG: Quota files for 101 are broken: no quota engine running
Jun 9 00:30:03 vm-box-3 vm-box-3 kernel: EXT4-fs (dm-1): ext4_orphan_cleanup: deleting unreferenced inode 39721124
Jun 9 00:30:03 vm-box-3 vm-box-3 kernel: VZDQ: Tried to clean orphans on qmblk with 1 state
Jun 9 00:30:03 vm-box-3 vm-box-3 kernel: BUG: Quota files for 101 are broken: no quota engine running
Jun 9 00:30:03 vm-box-3 vm-box-3 kernel: EXT4-fs (dm-1): ext4_orphan_cleanup: deleting unreferenced inode 39721123
Jun 9 00:30:03 vm-box-3 vm-box-3 kernel: VZDQ: Tried to clean orphans on qmblk with 1 state
Jun 9 00:30:03 vm-box-3 vm-box-3 kernel: BUG: Quota files for 101 are broken: no quota engine running
Jun 9 00:30:03 vm-box-3 vm-box-3 kernel: EXT4-fs (dm-1): ext4_orphan_cleanup: deleting unreferenced inode 39721122
Jun 9 00:30:03 vm-box-3 vm-box-3 kernel: VZDQ: Tried to clean orphans on qmblk with 1 state
Jun 9 00:30:03 vm-box-3 vm-box-3 kernel: BUG: Quota files for 101 are broken: no quota engine running
Jun 9 00:30:03 vm-box-3 vm-box-3 kernel: EXT4-fs (dm-1): ext4_orphan_cleanup: deleting unreferenced inode 39721121
Jun 9 00:30:03 vm-box-3 vm-box-3 kernel: EXT4-fs (dm-1): 6 orphan inodes deleted
Jun 9 00:30:03 vm-box-3 vm-box-3 kernel: EXT4-fs (dm-1): recovery complete
Jun 9 00:30:03 vm-box-3 vm-box-3 kernel: EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts:
Jun 9 00:31:03 vm-box-3 vm-box-3 vzdump[636153]: INFO: Finished Backup of VM 101 (00:01:02)
Jun 9 00:31:03 vm-box-3 vm-box-3 vzdump[636153]: INFO: Starting Backup of VM 103 (qemu)
Jun 9 00:31:04 vm-box-3 vm-box-3 qm[636727]: <root@pam> update VM 103: -lock backup
Jun 9 00:31:34 vm-box-3 vm-box-3 pvestatd[3032]: WARNING: unable to connect to VM 107 socket - timeout after 31 retries
Jun 9 00:31:44 vm-box-3 vm-box-3 pvestatd[3032]: WARNING: unable to connect to VM 104 socket - timeout after 31 retries
Jun 9 00:31:47 vm-box-3 vm-box-3 pvestatd[3032]: WARNING: unable to connect to VM 107 socket - timeout after 31 retries
Jun 9 00:31:47 vm-box-3 vm-box-3 pvestatd[3032]: status update time (6.134 seconds)
...
Jun 9 00:34:16 vm-box-3 vm-box-3 pvestatd[3032]: WARNING: unable to connect to VM 115 socket - timeout after 31 retries
Jun 9 00:34:18 vm-box-3 vm-box-3 kernel: INFO: task jbd2/dm-0-8:1652 blocked for more than 120 seconds.
Jun 9 00:34:18 vm-box-3 vm-box-3 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jun 9 00:34:18 vm-box-3 vm-box-3 kernel: jbd2/dm-0-8 D ffff880838624880 0 1652 2 0 0x00000000
Jun 9 00:34:18 vm-box-3 vm-box-3 kernel: ffff88083b6c1c10 0000000000000046 ffff88083b6c1b70 ffff8805ae1917c0
Jun 9 00:34:18 vm-box-3 vm-box-3 kernel: ffff88083b6c1bd0 ffffffff8140b5ec ffff88083b6c1bc0 ffffffff8109f5b3
Jun 9 00:34:18 vm-box-3 vm-box-3 kernel: ffff88083b6c1bb0 0000000000000282 ffff88083b6c1fd8 ffff88083b6c1fd8
Jun 9 00:34:18 vm-box-3 vm-box-3 kernel: Call Trace:
Jun 9 00:34:18 vm-box-3 vm-box-3 kernel: [<ffffffff8140b5ec>] ? dm_table_unplug_all+0x5c/0x100
Jun 9 00:34:18 vm-box-3 vm-box-3 kernel: [<ffffffff8109f5b3>] ? ktime_get_ts+0xb3/0xf0
Jun 9 00:34:18 vm-box-3 vm-box-3 kernel: [<ffffffff811c7760>] ? sync_buffer+0x0/0x50
Jun 9 00:34:18 vm-box-3 vm-box-3 kernel: [<ffffffff8151b563>] io_schedule+0x73/0xc0
Jun 9 00:34:18 vm-box-3 vm-box-3 kernel: [<ffffffff811c77a0>] sync_buffer+0x40/0x50
Jun 9 00:34:18 vm-box-3 vm-box-3 kernel: [<ffffffff8151c470>] __wait_on_bit+0x60/0x90
Jun 9 00:34:18 vm-box-3 vm-box-3 kernel: [<ffffffff811c7760>] ? sync_buffer+0x0/0x50
Jun 9 00:34:18 vm-box-3 vm-box-3 kernel: [<ffffffff8151c51c>] out_of_line_wait_on_bit+0x7c/0x90
Jun 9 00:34:18 vm-box-3 vm-box-3 kernel: [<ffffffff81095340>] ? wake_bit_function+0x0/0x50
Jun 9 00:34:18 vm-box-3 vm-box-3 kernel: [<ffffffff811c80f6>] __wait_on_buffer+0x26/0x30
Jun 9 00:34:18 vm-box-3 vm-box-3 kernel: [<ffffffffa0116f97>] jbd2_journal_commit_transaction+0xa07/0x1410 [jbd2]
Jun 9 00:34:18 vm-box-3 vm-box-3 kernel: [<ffffffff810096d2>] ? __switch_to+0xc2/0x2f0
Jun 9 00:34:18 vm-box-3 vm-box-3 kernel: [<ffffffff8107c8d8>] ? lock_timer_base.isra.76+0x38/0x70
Jun 9 00:34:18 vm-box-3 vm-box-3 kernel: [<ffffffffa011d6b8>] kjournald2+0xb8/0x200 [jbd2]
Jun 9 00:34:18 vm-box-3 vm-box-3 kernel: [<ffffffff81095300>] ? autoremove_wake_function+0x0/0x40
Jun 9 00:34:18 vm-box-3 vm-box-3 kernel: [<ffffffffa011d600>] ? kjournald2+0x0/0x200 [jbd2]
Jun 9 00:34:18 vm-box-3 vm-box-3 kernel: [<ffffffff81094d68>] kthread+0x88/0x90
Jun 9 00:34:18 vm-box-3 vm-box-3 kernel: [<ffffffff810096d2>] ? __switch_to+0xc2/0x2f0
Jun 9 00:34:18 vm-box-3 vm-box-3 kernel: [<ffffffff8100c22a>] child_rip+0xa/0x20
Jun 9 00:34:18 vm-box-3 vm-box-3 kernel: [<ffffffff81094ce0>] ? kthread+0x0/0x90
Jun 9 00:34:18 vm-box-3 vm-box-3 kernel: [<ffffffff8100c220>] ? child_rip+0x0/0x20

root@vm-box-3:~# pveversion -v
pve-manager: 3.0-20 (pve-manager/3.0/0428106c)
running kernel: 2.6.32-20-pve
proxmox-ve-2.6.32: 3.0-100
pve-kernel-2.6.32-20-pve: 2.6.32-100
pve-kernel-2.6.32-19-pve: 2.6.32-96
lvm2: 2.02.95-pve3
clvm: 2.02.95-pve3
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.0-1
pve-cluster: 3.0-4
qemu-server: 3.0-15
pve-firmware: 1.0-22
libpve-common-perl: 3.0-4
libpve-access-control: 3.0-4
libpve-storage-perl: 3.0-6
vncterm: 1.1-3
vzctl: 4.0-1pve3
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-12
ksm-control-daemon: 1.1-1

Are there any other suggestions besides changing ext4 to ext3?

 

[hk@]

I'd be interested in a solution too.
(or a hint not to use ext4 during setup would be nice)

is there a safe way to convert back to ext3 besides reinstall or dump everything and re-make the filesystem on /dev/mapper/pve-data?

and finally if only mkfs does the final trick - what are the suggested options to make it right this time?
(I assume restoring the backups then should work fine)

thank you in advance,
hk