From: Jens Axboe <jens.axboe@oracle.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Robert Hancock <hancockrwd@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: 2.6.32-rc4ish: task umount blocked for more than 120 seconds after USB drive removal
Date: Wed, 4 Nov 2009 08:41:37 +0100 [thread overview]
Message-ID: <20091104074137.GU8742@kernel.dk> (raw)
In-Reply-To: <20091103151812.2acc5259.akpm@linux-foundation.org>
On Tue, Nov 03 2009, Andrew Morton wrote:
> On Tue, 20 Oct 2009 23:26:17 -0600
> Robert Hancock <hancockrwd@gmail.com> wrote:
>
> > Running a post-2.6.32-rc4 git kernel, and just unmounted a USB drive
> > after writing a bunch of data to it, then pulled the plug after I
> > thought it had finished unmounting, but apparently it hadn't.. Ran into
> > a hung task warning that repeats every 120 seconds, the umount command
> > for the drive is stuck in D state.
> >
> > The full SysRq-T output is shown at the bottom.. any ideas what it's
> > waiting for?
>
> At a guess I'd say the new per-bdi writeback stuff blew up. Is this
> still happening in current mainline?
It happens in -rc6, it should be fixed in current -git. Robert, can you
try and confirm?
> It's remarkable how much harder these traces are to read post-wordwrapping.
Indeed, I always copy into a new buffer and un-wrap them :/
--
Jens Axboe
prev parent reply other threads:[~2009-11-04 7:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-21 5:26 2.6.32-rc4ish: task umount blocked for more than 120 seconds after USB drive removal Robert Hancock
2009-11-03 23:18 ` Andrew Morton
2009-11-04 7:41 ` Jens Axboe [this message]
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=20091104074137.GU8742@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=hancockrwd@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
/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.