From: Brad Campbell <brad@wasp.net.au>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: lkml <linux-kernel@vger.kernel.org>,
RAID Linux <linux-raid@vger.kernel.org>
Subject: Re: Raid-6 hang on write.
Date: Tue, 01 Mar 2005 10:58:51 +0400 [thread overview]
Message-ID: <422412AB.8080907@wasp.net.au> (raw)
In-Reply-To: <16930.45319.682534.351648@cse.unsw.edu.au>
Neil Brown wrote:
>
> Could you please confirm if there is a problem with
> 2.6.11-rc4-bk4->bk10
>
> as reported, and whether it seems to be the same problem.
Ok.. are we all ready? I had applied your development patches to all my vanilla 2.6.11-rc4-*
kernels. Thus they all exhibited the same problem in the same way as -mm1. <Smacks forehead against
wall repeatedly>
I had applied the patch to correct the looping resync issue with too many failed drives, and just
continued and applied all the other patches also.
I have been unable to reproduce the fault using a vanilla 2.6.11-rc5-bk2 kernel.
Oh well, at least we now know about a bug in the -mm patches.
Regards,
Brad
--
"Human beings, who are almost unique in having the ability
to learn from the experience of others, are also remarkable
for their apparent disinclination to do so." -- Douglas Adams
next prev parent reply other threads:[~2005-03-01 6:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-24 14:50 Raid-6 hang on write Brad Campbell
2005-02-25 15:37 ` Brad Campbell
2005-02-28 5:49 ` Neil Brown
2005-02-28 9:42 ` Bigmem in Linux 2.6.8 Iwan Sanders
2005-02-28 12:23 ` Mathieu Segaud
2005-03-01 5:34 ` Raid-6 hang on write Brad Campbell
2005-03-01 6:58 ` Brad Campbell [this message]
2005-03-01 9:18 ` Neil Brown
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=422412AB.8080907@wasp.net.au \
--to=brad@wasp.net.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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.