From: NeilBrown <neilb@suse.de>
To: jose.spam@netvisao.pt
Cc: jose.calhariz@netvisao.pt, linux-raid@vger.kernel.org,
ns-list@dsi.ist.utl.pt
Subject: Re: md raid6 deadlock on write
Date: Wed, 4 Jul 2012 11:38:11 +1000 [thread overview]
Message-ID: <20120704113811.180be107@notabene.brown> (raw)
In-Reply-To: <20120702221508.GA24801@calhariz.com>
[-- Attachment #1: Type: text/plain, Size: 912 bytes --]
On Mon, 2 Jul 2012 23:15:08 +0100 Jose Manuel dos Santos Calhariz
<jose.calhariz@netvisao.pt> wrote:
>
> We have a group of servers with a LVM over a RAID6 of 16 drives.
> During normal work loads, sometimes, the md raid enter on deadlock for
> writes and only a power off/power on allows to recover the machine.
This might be fixed by the following commit which was recently included in
3.5-rc. If could test with that I'd appreciate it.
>
> - there is information from "SysRq : Show State", not attached
> because is too big,
How big is too big? It is very hard to see if there is anything useful in
there if I cannot see it....
NeilBrown
>
> - in attach the output of "iostat -dx 1",
>
> - the "avgqu-sz" of the logical volume used for fio tests was
> 76280.00,
>
> - in attach the output of "ps ax".
>
>
> Jose Calhariz
>
>
>
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2012-07-04 1:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120629194600.GA23859@calhariz.com>
2012-07-02 22:15 ` md raid6 deadlock on write Jose Manuel dos Santos Calhariz
2012-07-04 1:38 ` NeilBrown [this message]
[not found] ` <20120704102411.GG15287@calhariz.com>
2012-07-06 13:55 ` Jose Manuel dos Santos Calhariz
2012-07-09 3:46 ` NeilBrown
2012-07-09 11:22 ` Jose Manuel dos Santos Calhariz
2012-07-04 2:43 ` Igor M Podlesny
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=20120704113811.180be107@notabene.brown \
--to=neilb@suse.de \
--cc=jose.calhariz@netvisao.pt \
--cc=jose.spam@netvisao.pt \
--cc=linux-raid@vger.kernel.org \
--cc=ns-list@dsi.ist.utl.pt \
/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