From: Joachim Otahal <Jou@gmx.net>
To: "Kristleifur Daðason" <kristleifur@gmail.com>
Cc: jin zhencheng <zhenchengjin@gmail.com>,
neilb@suse.de, linux-raid@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: BUG:write data to degrade raid5
Date: Fri, 19 Mar 2010 19:37:21 +0100 [thread overview]
Message-ID: <4BA3C461.5060209@gmx.net> (raw)
In-Reply-To: <73e903671003191123h1b7e1196v336265842f1b29e5@mail.gmail.com>
Kristleifur Daðason schrieb:
> On Fri, Mar 19, 2010 at 6:20 PM, Joachim Otahal <Jou@gmx.net
> <mailto:Jou@gmx.net>> wrote:
>
> jin zhencheng schrieb:
>
> hi;
>
> i use kernel is 2.6.26.2
>
> what i do as follow:
>
> 1, I create a raid5:
> mdadm -C /dev/md5 -l 5 -n 4 /dev/sda /dev/sdb /dev/sdc /dev/sdd
> --metadata=1.0 --assume-clean
>
> 2, dd if=/dev/zero of=/dev/md5 bs=1M&
>
> write data to this raid5
>
> 3, mdadm --manage /dev/md5 -f /dev/sda
>
> 4 mdadm --manage /dev/md5 -f /dev/sdb
>
> if i faild 2 disks ,then the OS kernel display OOP error and
> kernel down
>
> do somebody know why ?
>
> Is MD/RAID5 bug ?
>
>
> RAID5 can only tolerate ONE drive to fail of ALL members. If you
> want to be able to fail two drives you will have to use RAID6 or
> RAID5 with one hot-spare (and give it time to rebuild before
> failing the second drive).
> PLEASE read the documentation on raid levels, like on wikipedia.
>
>
> That is true,
>
> but should we get a kernel oops and crash if two RAID5 drives are
> failed? (THAT part looks like a bug!)
>
> Jin, can you try a newer kernel, and a newer mdadm?
>
> -- Kristleifur
You are probably right.
My kernel version is "Debian 2.6.26-21lenny4", and I had no oopses
during my hot-plug testing one the hardware I use md on. I think it may
be the driver for his chips.
Jin:
Did you really use the whole drives for testing or loopback files or
partitions on the drives? I never did my hot-plug testings with whole
drives being in an array, only with partitions.
Joachim Otahal
next prev parent reply other threads:[~2010-03-19 18:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-19 10:29 BUG:write data to degrade raid5 jin zhencheng
2010-03-19 18:20 ` Joachim Otahal
2010-03-19 18:30 ` Robin Hill
[not found] ` <73e903671003191123h1b7e1196v336265842f1b29e5@mail.gmail.com>
2010-03-19 18:26 ` Kristleifur Daðason
2010-03-19 18:37 ` Joachim Otahal [this message]
2010-03-21 10:29 ` jin zhencheng
2010-03-21 13:04 ` Henrique de Moraes Holschuh
2010-03-22 1:41 ` jin zhencheng
2010-03-20 15:50 ` Bill Davidsen
2010-03-23 3:16 ` 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=4BA3C461.5060209@gmx.net \
--to=jou@gmx.net \
--cc=kristleifur@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--cc=zhenchengjin@gmail.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).