From: "Paweł Brodacki" <pawel.brodacki@googlemail.com>
To: "Steinar H. Gunderson" <sgunderson@bigfoot.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: [BUG] Soft lockups in 2.6.32-rc3
Date: Mon, 19 Oct 2009 11:02:29 +0200 [thread overview]
Message-ID: <b95c1fdd0910190202y7bbceef7vbe6db2d5f6833a55@mail.gmail.com> (raw)
In-Reply-To: <20091011201955.GA19308@uio.no>
2009/10/11 Steinar H. Gunderson <sgunderson@bigfoot.com>:
> Hello,
>
> I've just upgraded from 2.6.31-rc8 to 2.6.32-rc3, and I thought I would turn
> on the new multicore RAID-5 processing. I did, it booted up and started
> syncing RAIDs (since the last shutdown before that was not clean), and
> started syncing at the minimum speed (1000 K/sec). I've seen this before, so
> I upped it in /proc to about 100MB/sec minimum (which is well below what I've
> seen from that RAID; six 7200rpm SATA drives connected by SAS).
>
> However, it never wanted to go above about 8-10MB/sec, and md4_raid5 used
> 100% CPU while I/O was extremely slow. Suddenly the serial console flashed:
>
< snip >
Hi,
I'm not savvy enough to read traces, but on surface it looks similar
to a problem described in a thread started on the linux-raid list by
Holger Kiehl on Oct. 16. (Raid reconstructing and process hanging in D
state).
Hope it helps.
Regards,
Paweł
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2009-10-19 9:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-11 20:19 [BUG] Soft lockups in 2.6.32-rc3 Steinar H. Gunderson
2009-10-19 9:02 ` Paweł Brodacki [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=b95c1fdd0910190202y7bbceef7vbe6db2d5f6833a55@mail.gmail.com \
--to=pawel.brodacki@googlemail.com \
--cc=linux-raid@vger.kernel.org \
--cc=sgunderson@bigfoot.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).