From: Nathan Dietsch <njd@ndietsch.com>
To: coreyfro@coreyfro.com, linux-raid@vger.kernel.org
Subject: Re: RAID5 crash and burn
Date: Mon, 01 Nov 2004 00:54:20 +1100 [thread overview]
Message-ID: <4184EE8C.2020408@ndietsch.com> (raw)
In-Reply-To: <1867.63.204.219.3.1099216777.squirrel@63.204.219.3>
Hello Corey,
coreyfro@coreyfro.com wrote:
>Ahhhhhh... doesn't use the raidtab... nothing needs raidtab anymore... i
>guess its time i got with the program...
>
>About swap failing, would there be much of a performence hit if i mirrored
>swap?
>
>
From what I read earlier in the thread, you already have a swap
partition on software RAID5, so how would going to RAID1 hurt performance.?
With swap on RAID5 -- unless you are paging very heavily (enough for a
full-stripe write) -- it seems you would go into Read-Modify-Write
anyway and this will hurt ... badly.
Mirroring swap is a good idea to avoid crashes as Guy suggests.
If you are seriously considering the performance implications of RAID1
vs RAID5 for swap, you are already done for performance wise.
Personally I would not consider software RAID5 suitable for tasks which
require performance. An exception would be for heavy I/O that causes
full-stripe writes, in which case you would probably get a win out of
the extra disks.
I hope this helps.
Kind Regards,
Nathan Dietsch
next prev parent reply other threads:[~2004-10-31 13:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-31 4:59 RAID5 crash and burn coreyfro
2004-10-31 5:18 ` Guy
2004-10-31 9:59 ` coreyfro
2004-10-31 11:26 ` Robin Bowes
2004-10-31 17:19 ` coreyfro
2004-10-31 13:15 ` Guy
2004-10-31 13:54 ` Nathan Dietsch [this message]
2004-10-31 19:41 ` Mark Hahn
2004-11-01 4:26 ` Nathan Dietsch
2004-11-01 5:29 ` Mark Hahn
2004-11-01 6:05 ` Nathan Dietsch
2004-11-01 6:32 ` Mark Hahn
2004-11-01 7:01 ` Guy
2004-11-01 9:01 ` Nathan Dietsch
2004-11-01 8:58 ` Nathan Dietsch
2004-10-31 19:05 ` Michael Robinton
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=4184EE8C.2020408@ndietsch.com \
--to=njd@ndietsch.com \
--cc=coreyfro@coreyfro.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 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.