linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: jin zhencheng <zhenchengjin@gmail.com>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: "Joachim Otahal" <Jou@gmx.net>,
	"Kristleifur Daðason" <kristleifur@gmail.com>,
	neilb@suse.de, linux-raid@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: BUG:write data to degrade raid5
Date: Mon, 22 Mar 2010 09:41:38 +0800	[thread overview]
Message-ID: <de04351e1003211841i3c3070b1ob033ee09a21dc8f1@mail.gmail.com> (raw)
In-Reply-To: <20100321130426.GB15746@khazad-dum.debian.net>

don't have swap on the RAID.

On Sun, Mar 21, 2010 at 9:04 PM, Henrique de Moraes Holschuh
<hmh@hmh.eng.br> wrote:
> On Sun, 21 Mar 2010, jin zhencheng wrote:
>> ths for your test on "Debian 2.6.26-21lenny4".
>> if you want to see the oop ,you should always write to the raid5 ,and
>> pull 2 disks out.maybe you can see the error
>>
>> i think no matter what i do ,even if i pull out all the disk , kernel
>> should not oop.
>
> You don't have swap (file or partition, doesn't matter) on that RAID, do
> you?
>
> --
>  "One disk to rule them all, One disk to find them. One disk to bring
>  them all and in the darkness grind them. In the Land of Redmond
>  where the shadows lie." -- The Silicon Valley Tarot
>  Henrique Holschuh
>

  reply	other threads:[~2010-03-22  1:41 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
     [not found]   ` <73e903671003191123h1b7e1196v336265842f1b29e5@mail.gmail.com>
2010-03-19 18:26     ` Kristleifur Daðason
2010-03-19 18:37     ` Joachim Otahal
2010-03-21 10:29       ` jin zhencheng
2010-03-21 13:04         ` Henrique de Moraes Holschuh
2010-03-22  1:41           ` jin zhencheng [this message]
2010-03-19 18:30   ` Robin Hill
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=de04351e1003211841i3c3070b1ob033ee09a21dc8f1@mail.gmail.com \
    --to=zhenchengjin@gmail.com \
    --cc=Jou@gmx.net \
    --cc=hmh@hmh.eng.br \
    --cc=kristleifur@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    /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).