search for: kjournald2

...hread 3057 S< [dlm_recv/1] worker_thread 3058 S< [dlm_recv/2] worker_thread 3059 S< [dlm_recv/3] worker_thread 3060 S< [dlm_send] worker_thread 3061 S< [dlm_recoverd] dlm_recoverd 3067 S< [kjournald2] kjournald2 3068 S< [ocfs2cmt] ocfs2_commit_thread 3082 D+ /usr/bin/perl /root/make_pa ocfs2_cluster_lock make_panic D 0000000000000002 0 3082 3021 ffff8801360f1a38 0000000000000046 ffffffffa0240b08 ffff88013703ea40 ffff88013eb877f8 000000000000...

...e,data=writeback,errors=panic) /dev/cciss/c0d0p9 on /squid-cache1 type ext4 (rw,noexec,nodev,noatime,data=writeback,errors=panic) /dev/cciss/c0d0p10 on /squid-data type ext4 (rw,noexec,nodev,noatime,data=writeback,errors=panic) Dmesg reports: [ 242.297469] EXT4-fs: barriers enabled [ 242.302098] kjournald2 starting: pid 2509, dev cciss!c0d0p8:8, commit interval 5 seconds [ 242.311272] EXT4 FS on cciss!c0d0p8, internal journal on cciss!c0d0p8:8 [ 242.311331] EXT4-fs: delayed allocation enabled [ 242.311386] EXT4-fs: file extents enabled [ 242.311562] EXT4-fs: mballoc enabled [ 242.311627] EXT4-fs...

...+0xe79/0x1950 [jbd2] [ 1920.052320] [<ffffffff8100331e>] ? xen_end_context_switch+0xe/0x20 [ 1920.052327] [<ffffffff810912f6>] ? finish_task_switch+0x46/0xf0 [ 1920.052331] [<ffffffff815141a3>] ? _raw_spin_unlock_irqrestore+0x13/0x20 [ 1920.052338] [<ffffffffa0058be2>] ? kjournald2+0xb2/0x240 [jbd2] [ 1920.052341] [<ffffffff810a7e60>] ? prepare_to_wait_event+0xf0/0xf0 [ 1920.052347] [<ffffffffa0058b30>] ? commit_timeout+0x10/0x10 [jbd2] [ 1920.052353] [<ffffffff8108809d>] ? kthread+0xbd/0xe0 [ 1920.052357] [<ffffffff81087fe0>] ? kthread_create_on_n...

After upgrading from 2.6.28.10 to 2.6.29.3 I've saw following new errors in kernel log: May 12 14:46:41 falcon-cl5 May 12 14:46:41 falcon-cl5 (6757,7):ocfs2_read_locked_inode:466 ERROR: status = -22 Only one node is mounted volumes in cluster: /dev/sde on /home/apache/users/D1 type ocfs2 (rw,_netdev,noatime,heartbeat=local) /dev/sdd on /home/apache/users/D2 type ocfs2

...ait+0x4e/0x80 [<ffffffffa01e881f>] jbd2_journal_commit_transaction+0x19f/0x14b0 [jbd2] [<ffffffff810096f0>] ? __switch_to+0xd0/0x320 [<ffffffff8107e00c>] ? lock_timer_base+0x3c/0x70 [<ffffffff810920d0>] ? autoremove_wake_function+0x0/0x40 [<ffffffffa01eef78>] kjournald2+0xb8/0x220 [jbd2] [<ffffffff810920d0>] ? autoremove_wake_function+0x0/0x40 [<ffffffffa01eeec0>] ? kjournald2+0x0/0x220 [jbd2] [<ffffffff81091d66>] kthread+0x96/0xa0 [<ffffffff8100c14a>] child_rip+0xa/0x20 [<ffffffff81091cd0>] ? kthread+0x0/0xa0 [<fffffff...

...tion+0xa5c/0x1950 [jbd2] [ 1680.060283] [<ffffffff8100331e>] ? xen_end_context_switch+0xe/0x20 [ 1680.060292] [<ffffffff810912f6>] ? finish_task_switch+0x46/0xf0 [ 1680.060297] [<ffffffff815141a3>] ? _raw_spin_unlock_irqrestore+0x13/0x20 [ 1680.060304] [<ffffffffa0015be2>] ? kjournald2+0xb2/0x240 [jbd2] [ 1680.060309] [<ffffffff810a7e60>] ? prepare_to_wait_event+0xf0/0xf0 [ 1680.060314] [<ffffffffa0015b30>] ? commit_timeout+0x10/0x10 [jbd2] [ 1680.060321] [<ffffffff8108809d>] ? kthread+0xbd/0xe0 [ 1680.060326] [<ffffffff81087fe0>] ? kthread_create_on_node+...

...d2] [<ffffffff8100d02f>] load_TLS+0x7/0xa [<ffffffff8100d69e>] __switch_to+0x133/0x258 [<ffffffff81039ac2>] finish_task_switch+0x88/0xb9 [<ffffffff81071011>] arch_local_irq_save+0x11/0x17 [<ffffffff8105fcd3>] autoremove_wake_function+0x0/0x2a [<ffffffffa0163156>] kjournald2+0xc0/0x20a [jbd2] [<ffffffff8105fcd3>] autoremove_wake_function+0x0/0x2a [<ffffffffa0163096>] kjournald2+0x0/0x20a [jbd2] [<ffffffff8105f681>] kthread+0x76/0x7e [<ffffffff81356ef4>] kernel_thread_helper+0x4/0x10 [<ffffffff8105f60b>] kthread+0x0/0x7e [<ffffffff81356e...

...er+0x3d2/0x492 [ 340.320146] [<ffffffff81d31dbc>] ? _raw_spin_unlock_irqrestore+0x47/0x5c [ 340.320151] [<ffffffff81156945>] ? try_to_del_timer_sync+0xa5/0xce [ 340.320154] [<ffffffff8111cde6>] ? trace_hardirqs_on_caller+0x3d2/0x492 [ 340.320157] [<ffffffff8143febd>] kjournald2+0x246/0x6e1 [ 340.320160] [<ffffffff8143febd>] ? kjournald2+0x246/0x6e1 [ 340.320163] [<ffffffff8143fc77>] ? commit_timeout+0xb/0xb [ 340.320167] [<ffffffff8111112e>] ? prepare_to_wait_event+0x3f7/0x3f7 [ 340.320171] [<ffffffff810ccde3>] kthread+0x252/0x261 [ 340.32...

...he guest's partitions under /sysroot before you will be able to examine them. bash: cannot set terminal process group (-1): Inappropriate ioctl for device bash: no job control in this shell ><rescue> mount /dev/vg_f11x64/lv_root /sysroot EXT4-fs (dm-0): barriers enabled kjournald2 starting: pid 269, dev dm-0:8, commit interval 5 seconds EXT4-fs (dm-0): internal journal on dm-0:8 EXT4-fs (dm-0): delayed allocation enabled EXT4-fs: file extents enabled EXT4-fs: mballoc enabled EXT4-fs (dm-0): mounted filesystem with ordered data mode ><rescue> ls /sysroot/...

...[ 340.320146] [<ffffffff81d31dbc>] ? _raw_spin_unlock_irqrestore+0x47/0x5c > [ 340.320151] [<ffffffff81156945>] ? try_to_del_timer_sync+0xa5/0xce > [ 340.320154] [<ffffffff8111cde6>] ? trace_hardirqs_on_caller+0x3d2/0x492 > [ 340.320157] [<ffffffff8143febd>] kjournald2+0x246/0x6e1 > [ 340.320160] [<ffffffff8143febd>] ? kjournald2+0x246/0x6e1 > [ 340.320163] [<ffffffff8143fc77>] ? commit_timeout+0xb/0xb > [ 340.320167] [<ffffffff8111112e>] ? prepare_to_wait_event+0x3f7/0x3f7 > [ 340.320171] [<ffffffff810ccde3>] kthread+0...

...[ 340.320146] [<ffffffff81d31dbc>] ? _raw_spin_unlock_irqrestore+0x47/0x5c > [ 340.320151] [<ffffffff81156945>] ? try_to_del_timer_sync+0xa5/0xce > [ 340.320154] [<ffffffff8111cde6>] ? trace_hardirqs_on_caller+0x3d2/0x492 > [ 340.320157] [<ffffffff8143febd>] kjournald2+0x246/0x6e1 > [ 340.320160] [<ffffffff8143febd>] ? kjournald2+0x246/0x6e1 > [ 340.320163] [<ffffffff8143fc77>] ? commit_timeout+0xb/0xb > [ 340.320167] [<ffffffff8111112e>] ? prepare_to_wait_event+0x3f7/0x3f7 > [ 340.320171] [<ffffffff810ccde3>] kthread+0...

Recently, I got many reports about perfermance degradation in embedded system(Android mobile phone, webOS TV and so on) and easy fork fail. The problem was fragmentation caused by zram and GPU driver mainly. With memory pressure, their pages were spread out all of pageblock and it cannot be migrated with current compaction algorithm which supports only LRU pages. In the end, compaction cannot

Recently, I got many reports about perfermance degradation in embedded system(Android mobile phone, webOS TV and so on) and easy fork fail. The problem was fragmentation caused by zram and GPU driver mainly. With memory pressure, their pages were spread out all of pageblock and it cannot be migrated with current compaction algorithm which supports only LRU pages. In the end, compaction cannot

Are these the current functional procedures for dropping a dom0 on a jaunty 64 bit server? xen-tools: http://bderzhavets.wordpress.com/2009/08/14/attempt-of-prevu-xen-3-4-1-hypervisor-on-ubuntu-jaunty-server-64-bit/ kernel: http://bderzhavets.wordpress.com/2009/07/07/building-xenified-2-6-30-1-kernel-via-xen-patches-2-6-30-2-tar-bz2/ Regarding the patches used in the above procedure from here:

This version fixes three bugs in the 2nd patch of this series that caused kernel BUG when the system was under race. We weren't accounting with t_oustanding_credits correctly, and there were race conditions caused by the fact the I had overlooked the fact that __jbd2_log_wait_for_space() and jbd2_get_transaction() requires j_state_lock to be write locked. Theodore Ts'o (3): jbd2: Use

...ffffffff81007cbc>] ? xen_clocksource_read+0x1c/0x20 Nov 5 13:44:20 192.168.1.6 kernel 04 [kern.warning] kernel: [ 6868.035116] [<ffffffff81d4eed1>] ? _raw_spin_lock_irqsave+0x11/0x50 Nov 5 13:44:20 192.168.1.6 kernel 04 [kern.warning] kernel: [ 6868.035128] [<ffffffff8128e5df>] ? kjournald2+0xaf/0x240 Nov 5 13:44:20 192.168.1.6 kernel 04 [kern.warning] kernel: [ 6868.035140] [<ffffffff810cd2d0>] ? wake_up_atomic_t+0x30/0x30 Nov 5 13:44:20 192.168.1.6 kernel 04 [kern.warning] kernel: [ 6868.035152] [<ffffffff8128e530>] ? commit_timeout+0x10/0x10 Nov 5 13:44:20 192.168....

...ffffffff81007cbc>] ? xen_clocksource_read+0x1c/0x20 Nov 5 13:44:20 192.168.1.6 kernel 04 [kern.warning] kernel: [ 6868.035116] [<ffffffff81d4eed1>] ? _raw_spin_lock_irqsave+0x11/0x50 Nov 5 13:44:20 192.168.1.6 kernel 04 [kern.warning] kernel: [ 6868.035128] [<ffffffff8128e5df>] ? kjournald2+0xaf/0x240 Nov 5 13:44:20 192.168.1.6 kernel 04 [kern.warning] kernel: [ 6868.035140] [<ffffffff810cd2d0>] ? wake_up_atomic_t+0x30/0x30 Nov 5 13:44:20 192.168.1.6 kernel 04 [kern.warning] kernel: [ 6868.035152] [<ffffffff8128e530>] ? commit_timeout+0x10/0x10 Nov 5 13:44:20 192.168....

On Sun, Nov 07 2010 at 6:05pm -0500, Andi Kleen <andi@firstfloor.org> wrote: > On Sun, Nov 07, 2010 at 10:39:23PM +0100, Milan Broz wrote: > > On 11/07/2010 08:45 PM, Andi Kleen wrote: > > >> I read about barrier-problems and data getting to the partition when > > >> using dm-crypt and several layers so I don''t know if that could be > >