From: Tim Southerwood <ts@dionic.net>
To: linux-raid@vger.kernel.org
Subject: Re: 2.6.24-rc6 reproducible raid5 hang
Date: Mon, 28 Jan 2008 17:29:42 +0000 [thread overview]
Message-ID: <479E1106.5000106@dionic.net> (raw)
In-Reply-To: <4798F577.20007@dionic.net>
Subtitle: Patch to mainline yet?
Hi
I don't see evidence of Neil's patch in 2.6.24, so I applied it by hand
on my server.
Was that the correct thing to do, or did this issue get fixed in a
different way that I wouldn't have spotted? I had a look at the git logs
but it was not obvious - please pardon my ignorance, I'm not familiar
enough with the code.
Many thanks,
Tim
Tim Southerwood wrote:
> Carlos Carvalho wrote:
>> Tim Southerwood (ts@dionic.net) wrote on 23 January 2008 13:37:
>> >Sorry if this breaks threaded mail readers, I only just subscribed
>> to >the list so don;t have the original post to reply to.
>> >
>> >I believe I'm having the same problem.
>> >
>> >Regarding XFS on a raid5 md array:
>> >
>> >Kernels 2.6.22-14 (Ubuntu Gutsy generic and server builds) *and*
>> >2.6.24-rc8 (pure build from virgin sources) compiled for amd64 arch.
>>
>> This has been corrected already, install Neil's patches. It worked for
>> several people under high stress, including us.
>> -
>> 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
>
> Hi
>
> I just coerced the patch into 2.6.23.14, reset
> /sys/block/md1/md/stripe_cache_size to default (256) and rebooted.
>
> I can confirm that after 2 hours of heavy bashing[1] the system has not
> hung. Looks good - many thanks. But I will run with a stripe_cache_size
> of 4096 in practise as it improves write speen on my configuration about
> 2.5 times.
>
> Cheers
>
> Tim
>
>
>
> [1] Rsync > 50GB to raid pluf xfs_fsr + dd 11GB of /dev/zero to same
> filesystem.
> -
> 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
next prev parent reply other threads:[~2008-01-28 17:29 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-23 13:37 2.6.24-rc6 reproducible raid5 hang Tim Southerwood
2008-01-23 17:43 ` Carlos Carvalho
2008-01-24 20:30 ` Tim Southerwood
2008-01-28 17:29 ` Tim Southerwood [this message]
2008-01-29 14:16 ` Carlos Carvalho
2008-01-29 22:58 ` Bill Davidsen
2008-02-14 10:13 ` Burkhard Carstens
-- strict thread matches above, loose matches on Subject: below --
2007-12-27 17:06 dean gaudet
2007-12-27 17:39 ` dean gaudet
2007-12-29 16:48 ` dean gaudet
2007-12-29 20:47 ` Dan Williams
2007-12-29 20:58 ` dean gaudet
2007-12-29 21:50 ` Justin Piszcz
2007-12-29 22:11 ` dean gaudet
2007-12-29 22:21 ` dean gaudet
2007-12-29 22:06 ` Dan Williams
2007-12-30 17:58 ` dean gaudet
2008-01-09 18:28 ` Dan Williams
2008-01-10 0:09 ` Neil Brown
2008-01-10 3:07 ` Dan Williams
2008-01-10 3:57 ` Neil Brown
2008-01-10 4:56 ` Dan Williams
2008-01-10 20:28 ` Bill Davidsen
2008-01-10 7:13 ` dean gaudet
2008-01-10 18:49 ` Dan Williams
2008-01-11 1:46 ` Neil Brown
2008-01-11 2:14 ` dean gaudet
2008-01-10 17:59 ` dean gaudet
2007-12-27 19:52 ` Justin Piszcz
2007-12-28 0:08 ` dean gaudet
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=479E1106.5000106@dionic.net \
--to=ts@dionic.net \
--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 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).