Hmmm, there may still be an issue, as I didn't encounter this yesterday when doing my task multiple times after booting with Upstart.
I'm mounting these qcow2 disk images in order to export a tarball of the filesystem. First three tarballs exported swimmingly, but the fourth time it seemed to hang, so I checked dmesg and saw this: [ 6009.696624] INFO: task jbd2/nbd0p1-8:26664 blocked for more than 120 seconds. [ 6009.696625] Tainted: P OE 3.19.0-10-generic #10-Ubuntu [ 6009.696625] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 6009.696625] jbd2/nbd0p1-8 D ffff8800c59d7b28 0 26664 2 0x00000000 [ 6009.696627] ffff8800c59d7b28 ffff8803beab3110 0000000000014200 ffff8800c59d7fd8 [ 6009.696628] 0000000000014200 ffff88040c6da740 ffff8803beab3110 ffff8803f0914d40 [ 6009.696629] ffff88041ed94af8 ffff88041efc89a0 0000000000000002 ffffffff817c44f0 [ 6009.696630] Call Trace: [ 6009.696631] [<ffffffff817c44f0>] ? bit_wait_timeout+0x70/0x70 [ 6009.696632] [<ffffffff817c3c20>] io_schedule+0xa0/0x130 [ 6009.696633] [<ffffffff817c451b>] bit_wait_io+0x2b/0x50 [ 6009.696634] [<ffffffff817c40c7>] __wait_on_bit+0x67/0x90 [ 6009.696636] [<ffffffff81380f40>] ? generic_make_request+0xc0/0x110 [ 6009.696637] [<ffffffff817c44f0>] ? bit_wait_timeout+0x70/0x70 [ 6009.696638] [<ffffffff817c4162>] out_of_line_wait_on_bit+0x72/0x80 [ 6009.696639] [<ffffffff810b6240>] ? autoremove_wake_function+0x40/0x40 [ 6009.696640] [<ffffffff81227d46>] __wait_on_buffer+0x36/0x40 [ 6009.696641] [<ffffffff812c8df0>] jbd2_write_superblock+0xa0/0x190 [ 6009.696643] [<ffffffff812cb373>] jbd2_journal_update_sb_log_tail+0x33/0x80 [ 6009.696645] [<ffffffff812c39fa>] jbd2_journal_commit_transaction+0x57a/0x1820 [ 6009.696646] [<ffffffff810ab9c0>] ? dequeue_entity+0x140/0x680 [ 6009.696648] [<ffffffff8109ea5d>] ? ttwu_do_wakeup+0x1d/0xe0 [ 6009.696649] [<ffffffff810ac2e6>] ? dequeue_task_fair+0x3e6/0x6a0 [ 6009.696650] [<ffffffff810ad111>] ? put_prev_entity+0x31/0x430 [ 6009.696652] [<ffffffff810b04ab>] ? pick_next_task_fair+0x1ab/0x8a0 [ 6009.696653] [<ffffffff810ad53f>] ? put_prev_task_fair+0x2f/0x50 [ 6009.696654] [<ffffffff810dc35b>] ? lock_timer_base.isra.36+0x2b/0x50 [ 6009.696655] [<ffffffff810dd44f>] ? try_to_del_timer_sync+0x4f/0x70 [ 6009.696656] [<ffffffff812c85bb>] kjournald2+0xbb/0x250 [ 6009.696657] [<ffffffff810b6200>] ? wait_woken+0x90/0x90 [ 6009.696658] [<ffffffff812c8500>] ? commit_timeout+0x10/0x10 [ 6009.696660] [<ffffffff81094679>] kthread+0xc9/0xe0 [ 6009.696661] [<ffffffff810945b0>] ? kthread_create_on_node+0x1c0/0x1c0 [ 6009.696662] [<ffffffff817c8198>] ret_from_fork+0x58/0x90 [ 6009.696663] [<ffffffff810945b0>] ? kthread_create_on_node+0x1c0/0x1c0 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1435428 Title: vivid: systemd breaks qemu-nbd mounting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1435428/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
