All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Pavel Machek <pavel@ucw.cz>, kernel list <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.32-rc5: surprise removal of USB mass storage, and whole system goes to hell
Date: Wed, 28 Oct 2009 15:07:31 +0100	[thread overview]
Message-ID: <20091028140731.GP10727@kernel.dk> (raw)
In-Reply-To: <20091028095537.GD10727@kernel.dk>

On Wed, Oct 28 2009, Jens Axboe wrote:
> On Wed, Oct 28 2009, Jiri Kosina wrote:
> > On Tue, 27 Oct 2009, Pavel Machek wrote:
> > 
> > > I did remove one harddrive w/o unmounting, and now the whole system
> > > becomes unusable :-(: (whole dmesg attached).
> > > 
> > > Stuff like "sync" hangs, and I'll probably have to reboot soon.
> > 
> > From the traces it seems that it might be related to the new per-bdi 
> > writeback stuff ... adding Jens to CC.
> 
> It looks like the IO isn't being errored on the device side, or perhaps
> it just got stuck. Pavel, if you can reproduce, please try with this
> tracing patch. Apply it, and then do something ala:
> 
> # cd /sys/kernel/debug/tracing
> # echo 0 events/enable
> # echo 1 events/writeback/enable
> # echo 0 > trace
> 
> then start the act of reproducing, and finally
> 
> # cat trace > /tmp/foo
> 
> and send the output of foo here. Thanks!

I can reproduce this. The writeback work gets queued, we notice the task
isn't there and wake up the default task. And then nothing happens, I
wonder if the bdi is gone.

I'll fiddle around with this.

-- 
Jens Axboe


  reply	other threads:[~2009-10-28 14:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-27 21:19 2.6.32-rc5: surprise removal of USB mass storage, and whole system goes to hell Pavel Machek
2009-10-28  1:14 ` Jiri Kosina
2009-10-28  9:55   ` Jens Axboe
2009-10-28 14:07     ` Jens Axboe [this message]
2009-10-29  8:38       ` Jens Axboe
2009-11-15  9:46         ` Heinz Diehl
2009-10-28  1:18 ` Yong Zhang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20091028140731.GP10727@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=jkosina@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.