From: Molle Bestefich <molle.bestefich@gmail.com>
To: Francisco Zafra <fzafra@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Troubles making a raid5 system work.
Date: Thu, 2 Jun 2005 02:56:12 +0200 [thread overview]
Message-ID: <62b0912f0506011756fa6f59d@mail.gmail.com> (raw)
In-Reply-To: <429df617.35a2a6be.0f63.ffffff9a@mx.gmail.com>
Francisco Zafra wrote:
> Finally I made the raid system work fine :-)
Cool beans ;-).
> 1.- This patch will be included in new kernels versions or I have to applied
> each time I compile a new kernel version?
It will be included at some point, probably "soon".
I'm not part of that process so can't really say for sure when..
> 2.- Working with big files (700megs) in the RAID comsumes a lot of cpu
> resources, is this normal? I have an Pentium 4, 3Ghz and 1GB RAM...
Probably depends how you define "working".
For simple operations, my *guess* would be that your CPU should
outperform your I/O subsystem, at least if you have DMA enabled. You
can check if that's the case with 'hdparm /dev/hd<x>'.
I'm not sure how to analyze your CPU problem. You're probably
interested in knowing whether it's MD doing XOR for raid5 or it's the
kernel busy waiting for your IDE disks. Unless you are doing other
things, like encryption for example. Perhaps a tool like 'top' can
help you. But again, I have no real good idea how to find out.
Perhaps others can be helpful?
With 8 disks and a standard PCI bus, my guess would be that your PCI
bus would be the first thing to get saturated.
prev parent reply other threads:[~2005-06-02 0:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-29 15:59 Troubles making a raid5 system work Francisco Zafra
2005-05-30 7:53 ` Molle Bestefich
2005-06-01 17:51 ` Francisco Zafra
2005-06-02 0:56 ` Molle Bestefich [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=62b0912f0506011756fa6f59d@mail.gmail.com \
--to=molle.bestefich@gmail.com \
--cc=fzafra@gmail.com \
--cc=linux-raid@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 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).