Sorry for the wrong subject. I had an error at boot, same as the one described. I remember adding settings about checking LVM2 at boot when I set up my LVM group. Currently traveling, so can'r give you more details, but I guess new iniscript broke something with LVM. Regards ####Sent from my Galaxy S2 running Cyanogenmod 9#### Come and chat on Googletalk On Jul 3, 2012 7:06 PM, "Tom Gundersen" <teg@xxxxxxx> wrote: > On Jul 3, 2012 4:36 PM, "Arno Gaboury" <arnaud.gaboury@xxxxxxxxx> wrote: > > > > Dear list, > > > > I refer to this bug report: > > > >> https://bugs.archlinux.org/task/30517 > > > > > > I have exactly the same situation at boot, and this didn't happend > before. > > The bug report is about lvm, and your email appears to be about btrfs... > Seems some info is missing. > > As to the bug report, it was just assigned to me, so I will sort it or > tonight (I hope). > > Tom > > > Form my kernel.log: > > > > > > > >> Jul 3 16:27:01 localhost kernel: [ 240.373550] INFO: task > btrfs-transacti:353 blocked for more than 120 seconds. > >> Jul 3 16:27:01 localhost kernel: [ 240.373554] "echo 0 > > /proc/sys/kernel/hung_task_timeout_secs" disables this message. > >> Jul 3 16:27:01 localhost kernel: [ 240.373557] btrfs-transacti D > ffff880402ae3b58 0 353 2 0x00000000 > >> Jul 3 16:27:01 localhost kernel: [ 240.373562] ffff880402bc3c80 > 0000000000000046 ffff880402ae3790 ffff880402bc3fd8 > >> Jul 3 16:27:01 localhost kernel: [ 240.373568] ffff880402bc3fd8 > ffff880402bc3fd8 ffff880408daa7b0 ffff880402ae3790 > >> Jul 3 16:27:01 localhost kernel: [ 240.373580] ffff88041f493740 > 0000000000013740 ffff880400000000 ffff880402bc3bc8 > >> Jul 3 16:27:01 localhost kernel: [ 240.373583] Call Trace: > >> Jul 3 16:27:01 localhost kernel: [ 240.373590] [<ffffffff81013580>] ? > __switch_to+0x120/0x410 > >> Jul 3 16:27:01 localhost kernel: [ 240.373595] [<ffffffff81468b29>] > schedule+0x29/0x70 > >> Jul 3 16:27:01 localhost kernel: [ 240.373598] [<ffffffff81468df7>] > schedule_preempt_disabled+0x27/0x40 > >> Jul 3 16:27:01 localhost kernel: [ 240.373600] [<ffffffff814674a8>] > __mutex_lock_slowpath+0x148/0x340 > >> Jul 3 16:27:01 localhost kernel: [ 240.373603] [<ffffffff814676b6>] > mutex_lock+0x16/0x30 > >> Jul 3 16:27:01 localhost kernel: [ 240.373625] [<ffffffffa013d2bb>] > btrfs_run_ordered_operations+0x3b/0x210 [btrfs] > >> Jul 3 16:27:01 localhost kernel: [ 240.373636] [<ffffffffa011d3a4>] > btrfs_commit_transaction+0x74/0xaa0 [btrfs] > >> Jul 3 16:27:01 localhost kernel: [ 240.373646] [<ffffffffa011ca4c>] ? > join_transaction.isra.22+0x2dc/0x310 [btrfs] > >> Jul 3 16:27:01 localhost kernel: [ 240.373650] [<ffffffff81073b60>] ? > abort_exclusive_wait+0xb0/0xb0 > >> Jul 3 16:27:01 localhost kernel: [ 240.373660] [<ffffffffa0115e25>] > transaction_kthread+0x235/0x2b0 [btrfs] > >> Jul 3 16:27:01 localhost kernel: [ 240.373669] [<ffffffffa0115bf0>] ? > btrfs_alloc_root+0x50/0x50 [btrfs] > >> Jul 3 16:27:01 localhost kernel: [ 240.373671] [<ffffffff810731d3>] > kthread+0x93/0xa0 > >> Jul 3 16:27:01 localhost kernel: [ 240.373674] [<ffffffff8146bbe4>] > kernel_thread_helper+0x4/0x10 > >> Jul 3 16:27:01 localhost kernel: [ 240.373677] [<ffffffff81073140>] ? > kthread_freezable_should_stop+0x70/0x70 > >> Jul 3 16:27:01 localhost kernel: [ 240.373680] [<ffffffff8146bbe0>] ? > gs_change+0x13/0x13 > > > > > > Is it really a bug, or did I miss something or did something wrong? > > > > TY for any advise. >
