From: Michael Breuer <mbreuer@majjas.com>
To: Jan Kara <jack@suse.cz>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Hung task - sync - 2.6.33-rc7 w/md6 multicore rebuild in process
Date: Wed, 17 Feb 2010 21:51:58 -0500 [thread overview]
Message-ID: <4B7CAB4E.2090002@majjas.com> (raw)
In-Reply-To: <20100218023934.GC8897@atrey.karlin.mff.cuni.cz>
On 2/17/2010 9:39 PM, Jan Kara wrote:
>> On 2/13/2010 11:51 AM, Michael Breuer wrote:
>>
>> Note: this cleared after about 90 minutes - sync eventually completed.
>> I'm thinking that with multicore enabled the resync is able to starve
>> out normal system activities that weren't starved w/o multicore.
>>
> Hmm, it is a bug in writeback code. But as Linus pointed out, it's not really
> clear why it's *so* slow. So when it happens again, could you please sample for
> a while (like every second for 30 seconds) stacks of blocked tasks via
> Alt-Sysrq-W? I'd like to see where flusher threads are hanging... Thanks.
>
> Honza
>
Ok - will do. On rc8 now - and up about 3 days without any issues. If I
have some time tomorrow I'll force a raid resync and see what happens.
next prev parent reply other threads:[~2010-02-18 2:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-13 16:51 Hung task - sync - 2.6.33-rc7 w/md6 multicore rebuild in process Michael Breuer
2010-02-13 17:09 ` Michael Breuer
2010-02-13 18:16 ` Michael Breuer
2010-02-18 2:39 ` Jan Kara
2010-02-18 2:51 ` Michael Breuer [this message]
2010-02-18 17:11 ` Michael Breuer
2010-02-19 1:43 ` Dave Chinner
2010-02-19 2:31 ` Michael Breuer
2010-02-19 4:02 ` Dave Chinner
2010-02-19 5:31 ` Michael Breuer
2010-02-19 21:05 ` Dave Chinner
2010-04-02 11:01 ` Pozsar Balazs
2010-04-02 13:58 ` mbreuer
-- strict thread matches above, loose matches on Subject: below --
2010-02-13 16:37 Michael Breuer
2010-02-13 16:17 Michael Breuer
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=4B7CAB4E.2090002@majjas.com \
--to=mbreuer@majjas.com \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
/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.