All of lore.kernel.org
 help / color / mirror / Atom feed
From: mru@users.sourceforge.net (Måns Rullgård)
To: linux-kernel@vger.kernel.org
Subject: Re: Software RAID5 with 2.6.0-test
Date: Thu, 09 Oct 2003 01:44:13 +0200	[thread overview]
Message-ID: <yw1xad8bfg6q.fsf@users.sourceforge.net> (raw)
In-Reply-To: 1065655452.13572.50.camel@torrey.et.myrio.com

Torrey Hoffman <thoffman@arnor.net> writes:

> My experience:
>
> I'm running 2.6.0-test6 on a dual pentium 3 with software raid-5 across
> 5 disks on two different IDE hardware controllers (VIA and Promise). 
> I've got a 224 GB reiserfs partition on that.  
>
> After 8 days uptime, it doesn't seem to have blown up yet.  However I
> don't stress it heavily - just a nightly rsync or two which does a lot
> of reading and writing, and I export my music collection on it via NFS,
> which is a low level of read activity.  

When I tried it, I was running 2.6.0-test4.  The RAID5 was 4 120 GB
Seagate disks on a Highpoint controller.  On top of that, I had LVM,
with ext3 fs.  After just minutes, strange things started happening to
files.  Some had random bits changed in the inode, others were just
trashed.  e2fsck complained a great deal.

I went back to 2.4.21, which is working OK.  A couple of things bother
me, though.  In the dmesg output there are many of these:

raid5: switching cache buffer size, 8192 --> 1024
raid5: switching cache buffer size, 1024 --> 4096
raid5: switching cache buffer size, 4096 --> 1024
raid5: switching cache buffer size, 1024 --> 4096
raid5: switching cache buffer size, 4096 --> 1024

ISTR reading somewhere, that this has a bad impact on performance.

The other thing that I don't like, is the performance of the RAID
array.  The disks individually give ~40 MB/s read speed, but the array
only measures 25 MB/s.  I was of the impression, that RAID5 would give
read speeds at least equal to the underlying disks.  Is this
incorrect?

-- 
Måns Rullgård
mru@users.sf.net


  reply	other threads:[~2003-10-08 23:44 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-08 22:43 Software RAID5 with 2.6.0-test Måns Rullgård
2003-10-08 23:24 ` Torrey Hoffman
2003-10-08 23:44   ` Måns Rullgård [this message]
2003-10-09  0:51     ` Andre Tomt
2003-10-09  8:55       ` Måns Rullgård
2003-10-09  9:10         ` Andre Tomt
2003-10-09  9:28           ` Måns Rullgård
2003-10-17 17:07           ` Bill Davidsen
2003-10-17 17:44             ` Måns Rullgård
2003-10-17 18:39               ` Samuel Flory
2003-10-17 19:18                 ` Måns Rullgård
2003-10-17 19:37                   ` Jakob Oestergaard
2003-10-17 19:52                     ` Måns Rullgård
2003-10-18 22:55                   ` jw schultz
2003-10-17 19:24               ` Jakob Oestergaard
2003-10-19  9:25                 ` Pavel Machek
2003-10-21 21:44                 ` bill davidsen
2003-10-21 21:36               ` bill davidsen
2003-10-22 15:17                 ` Chuck Campbell
2003-10-18 11:50 Dr. David Alan Gilbert
2003-10-21 21:51 ` bill davidsen
2003-10-22  2:37   ` jw schultz

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=yw1xad8bfg6q.fsf@users.sourceforge.net \
    --to=mru@users.sourceforge.net \
    --cc=linux-kernel@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 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.