From: Chris Allen <chris@cjx.com>
To: linux-raid@vger.kernel.org
Subject: Re: raid5 hang on get_active_stripe
Date: Sun, 08 Oct 2006 00:25:46 +0100 [thread overview]
Message-ID: <4528377A.2010001@cjx.com> (raw)
In-Reply-To: <17551.18061.160356.35034@cse.unsw.edu.au>
Neil Brown wrote:
> On Tuesday June 13, davidsen@tmr.com wrote:
>
>> Will that fix be in 2.6.17?
>>
>>
>
> Probably not. We have had the last 'rc' twice and I so I don't think
> it is appropriate to submit the patch at this stage.
> I probably will submit it for an early 2.6.17.x. and for 2.6.16.y.
>
>
>
What is the status of this?
I've been experiencing exactly the same get_active_stripe lockup
on a FC5 2.6.17-1.2187_FC5smp stock kernel. Curiously we have ten
similar heavily loaded
servers but only one of them experiences the problem. The problem
happens consistently after 24 hours or so
when I hammer the raid5 array over NFS, but I've never managed to
trigger it with local access. I'd also
say (anecdotally) that it only started happening since I added a bitmap
to my array.
As with the other poster, the lockup is released by increasing
stripe_cache_size.
next prev parent reply other threads:[~2006-10-07 23:25 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-06 11:46 raid5 performance question Raz Ben-Jehuda(caro)
2006-03-06 11:59 ` Gordon Henderson
2006-03-06 12:56 ` Raz Ben-Jehuda(caro)
2006-03-13 22:36 ` raid5 hang on get_active_stripe Patrik Jonsson
2006-03-13 23:17 ` Neil Brown
2006-05-11 15:13 ` dean gaudet
2006-05-17 18:41 ` dean gaudet
2006-05-19 3:46 ` Neil Brown
2006-05-23 2:33 ` Neil Brown
2006-05-26 16:07 ` dean gaudet
2006-05-26 23:55 ` Neil Brown
2006-05-27 0:28 ` dean gaudet
2006-05-27 15:42 ` dean gaudet
2006-05-28 12:04 ` Neil Brown
2006-05-29 20:56 ` dean gaudet
2006-05-29 23:51 ` Neil Brown
2006-05-31 0:15 ` dean gaudet
2006-05-31 0:46 ` Neil Brown
2006-05-31 1:03 ` dean gaudet
2006-05-31 1:38 ` Neil Brown
2006-05-31 1:46 ` dean gaudet
2006-06-01 2:51 ` Neil Brown
2006-06-02 7:10 ` dean gaudet
2006-06-02 7:27 ` Neil Brown
2006-06-10 19:49 ` dean gaudet
2006-06-13 18:53 ` Bill Davidsen
2006-06-13 19:05 ` dean gaudet
2006-06-13 23:13 ` Neil Brown
2006-10-07 23:25 ` Chris Allen [this message]
2006-10-09 11:03 ` Chris Allen
2006-10-09 23:06 ` Neil Brown
2006-10-09 23:21 ` Chris Allen
2006-10-10 0:08 ` Neil Brown
2006-10-10 10:27 ` Bas van Schaik
2006-11-14 10:28 ` Chris Allen
2006-11-15 20:39 ` dean gaudet
2006-03-06 22:17 ` raid5 performance question Guy
2006-03-06 22:24 ` Neil Brown
2006-03-07 8:40 ` Raz Ben-Jehuda(caro)
2006-03-07 23:03 ` Neil Brown
2006-03-22 13:22 ` Bill Davidsen
2006-03-24 4:40 ` Neil Brown
2006-03-08 6:45 ` thunder7
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=4528377A.2010001@cjx.com \
--to=chris@cjx.com \
--cc=linux-raid@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.