Problems with EXT4 and ProxMox 2.0?

oeginc

Member
Mar 21, 2009
133
0
16
I just noticed I'm getting thousands of these messages in my logs everyday...

VZDQ: Tried to clean orphans on qmblk with 1 state
BUG: Quota files for 208243 are broken: no quota engine running
EXT4-fs (dm-4): ext4_orphan_cleanup: deleting unreferenced inode 26878991
VZDQ: Tried to clean orphans on qmblk with 1 state
BUG: Quota files for 208243 are broken: no quota engine running
EXT4-fs (dm-4): ext4_orphan_cleanup: deleting unreferenced inode 26878977
VZDQ: Tried to clean orphans on qmblk with 1 state
BUG: Quota files for 208243 are broken: no quota engine running
EXT4-fs (dm-4): ext4_orphan_cleanup: deleting unreferenced inode 26878973
EXT4-fs (dm-4): 35 orphan inodes deleted
EXT4-fs (dm-4): recovery complete
EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts:

It doesn't sound good.... This is my SSD drive, which is why it's ext4 instead of ext3...
Is there a problem with EXT4? Is this happening because of the snapshot backups,
or something else?

Also, on a side note, I've been getting this on one of the servers:

INFO: task master:254713 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
master D ffff88062a0f8c40 0 254713 254652 209010 0x00020000
ffff88015a7b3a58 0000000000200086 0000000000000000 ffff880627c0f0f8
ffff88002821e2a8 ffff88002821e240 ffff88015a7b39e8 ffffffff811209fe
000000000001b200 ffff88062a0f91e0 ffff88015a7b3fd8 ffff88015a7b3fd8
Call Trace:
[<ffffffff811209fe>] ? find_get_page+0x1e/0xa0
[<ffffffffa02e300d>] do_get_write_access+0x29d/0x510 [jbd2]
[<ffffffff810944f0>] ? wake_bit_function+0x0/0x40
[<ffffffffa02e33d1>] jbd2_journal_get_write_access+0x31/0x50 [jbd2]
[<ffffffffa0327fe8>] __ext4_journal_get_write_access+0x38/0x70 [ext4]
[<ffffffffa03014c3>] ext4_reserve_inode_write+0x73/0xa0 [ext4]
[<ffffffffa030153c>] ext4_mark_inode_dirty+0x4c/0x1d0 [ext4]
[<ffffffffa0301830>] ext4_dirty_inode+0x40/0x60 [ext4]
[<ffffffff811b976b>] __mark_inode_dirty+0x3b/0x160
[<ffffffff811a96ca>] file_update_time+0x10a/0x1a0
[<ffffffff81199164>] pipe_write+0x2c4/0x640
[<ffffffff8118e91a>] do_sync_write+0xfa/0x140
[<ffffffff8119fcc4>] ? user_path_at+0x64/0xa0
[<ffffffff810944b0>] ? autoremove_wake_function+0x0/0x40
[<ffffffff811af300>] ? mntput_no_expire+0x30/0x110
[<ffffffff8119c831>] ? path_put+0x31/0x40
[<ffffffff81012af9>] ? read_tsc+0x9/0x20
[<ffffffff8109f039>] ? ktime_get_ts+0xa9/0xe0
[<ffffffff8118ebf8>] vfs_write+0xb8/0x1a0
[<ffffffff8118f601>] sys_write+0x51/0x90
[<ffffffff811a522c>] ? sys_poll+0x7c/0x110
[<ffffffff81049583>] ia32_sysret+0x0/0x5
INFO: task master:311304 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
master D ffff8803140c63c0 0 311304 311262 209016 0x00020000
ffff880585725a58 0000000000200082 0000000000000000 0000000000000000
ffff8805857259c8 ffffffff81059d82 ffff8805857259e8 ffffffff811209fe
000000000001b200 ffff8803140c6960 ffff880585725fd8 ffff880585725fd8
Call Trace:
[<ffffffff81059d82>] ? default_wake_function+0x12/0x20
[<ffffffff811209fe>] ? find_get_page+0x1e/0xa0
[<ffffffffa02e300d>] do_get_write_access+0x29d/0x510 [jbd2]
[<ffffffff810944f0>] ? wake_bit_function+0x0/0x40
[<ffffffffa02e33d1>] jbd2_journal_get_write_access+0x31/0x50 [jbd2]
[<ffffffffa0327fe8>] __ext4_journal_get_write_access+0x38/0x70 [ext4]
[<ffffffffa03014c3>] ext4_reserve_inode_write+0x73/0xa0 [ext4]
[<ffffffffa030153c>] ext4_mark_inode_dirty+0x4c/0x1d0 [ext4]
[<ffffffffa0301830>] ext4_dirty_inode+0x40/0x60 [ext4]
[<ffffffff811b976b>] __mark_inode_dirty+0x3b/0x160
[<ffffffff811a96ca>] file_update_time+0x10a/0x1a0
[<ffffffff81199164>] pipe_write+0x2c4/0x640
[<ffffffff8118e91a>] do_sync_write+0xfa/0x140
[<ffffffff8119fcc4>] ? user_path_at+0x64/0xa0
[<ffffffff810944b0>] ? autoremove_wake_function+0x0/0x40
[<ffffffff811af300>] ? mntput_no_expire+0x30/0x110
[<ffffffff8119c831>] ? path_put+0x31/0x40
[<ffffffff81012af9>] ? read_tsc+0x9/0x20
[<ffffffff8109f039>] ? ktime_get_ts+0xa9/0xe0
[<ffffffff8118ebf8>] vfs_write+0xb8/0x1a0
[<ffffffff8118f601>] sys_write+0x51/0x90
[<ffffffff811a522c>] ? sys_poll+0x7c/0x110
[<ffffffff81049583>] ia32_sysret+0x0/0x5
 
I have the same problem with ext4.

Will reinstall the Server and use ext3 instead. There is no workaround as i know.
 
As I mentioned, this is my SSD drive and ext3 doesn't support TRIM so that really isn't an option unfortunately...
 
use SSD which does not need trim.