linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gewj <geweijin@sinosoft.com.cn>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: Lars Marowsky-Bree <lmb@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: A puzzling thing about RAID5: syslogd write the log success but another process can not read the /var/log/messages
Date: Fri, 09 Apr 2004 09:49:57 +0800	[thread overview]
Message-ID: <40760145.5030109@sinosoft.com.cn> (raw)
In-Reply-To: 16500.35602.13336.290506@cse.unsw.edu.au

thank for your comments

I should say that this question maybe end up without any reasonable result,
the system is now work well , I have give up investigating this problem 
any more.
maybe the question is just cause by the RAID card crash.

Neil Brown wrote:

>On Wednesday April 7, lmb@suse.de wrote:
>  
>
>>On 2004-04-07T21:24:01,
>>   Gewj <geweijin@sinosoft.com.cn> said:
>>
>>    
>>
>>>hammm,tonight is funny because I got a puzzling thing just as....
>>>
>>>my setup is a two-scsi-disk raid5 configuration...
>>>      
>>>
>>Impossible. RAID5 requires at least three disks.
>>    
>>
>
>Wrong.  RAID5 works fine with just two drives.  Try it.
>
>NeilBrown
>
>(I admit that there isn't a lot of point doing raid5 with two drives
>as raid1 should provide identical functionality with better
>performance, but it makes an interesting base-line for performances
>tests on N-drive arrays).
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at  http://www.tux.org/lkml/
>
>  
>




      reply	other threads:[~2004-04-09  1:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-07 13:24 A puzzling thing about RAID5: syslogd write the log success but another process can not read the /var/log/messages Gewj
2004-04-07 14:51 ` Lars Marowsky-Bree
2004-04-07 23:13   ` Neil Brown
2004-04-09  1:49     ` Gewj [this message]

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=40760145.5030109@sinosoft.com.cn \
    --to=geweijin@sinosoft.com.cn \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lmb@suse.de \
    --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 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).