All of lore.kernel.org
 help / color / mirror / Atom feed
From: jw schultz <jw@pegasys.ws>
To: Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: lilo/raid?
Date: Tue, 2 Jul 2002 03:26:27 -0700	[thread overview]
Message-ID: <20020702032627.D28771@pegasys.ws> (raw)
In-Reply-To: <Pine.LNX.4.44.0207021111050.21320-100000@netfinity.realnet.co.sz>; from zwane@mwaikambo.name on Tue, Jul 02, 2002 at 11:12:03AM +0200

On Tue, Jul 02, 2002 at 11:12:03AM +0200, Zwane Mwaikambo wrote:
> On Tue, 2 Jul 2002, Helge Hafting wrote:
> 
> > > > /dev/md1                swap                    swap    defaults        0 0
> > > 
> > > One small thing, you do know that you can interleave swap?
> > 
> > There are sometimes reasons not to do that.
> > Heavy swapping may be caused by attempts to cache 
> > massive io on some fs.  You better not have swap
> > on that heavily accessed spindle - because then
> > everything ends up waiting on that io.
> > 
> > Keeping swap somewhere else means other programs
> > just wait a little for swap - undisturbed by the massive
> > io also going on.
> 
> True, but what i meant was that instead of creating a RAID device to swap 
> to, he could have just interleaved normal swap partitions and gotten the 
> same effect.

Not a config i would recommend.  While spreading swap over
multiple spindles that way is good for speed it multiplies the
likelihood that a disk failure will down the system.  If you
think a dead filesystem is a mess, just watch what happens
when swap goes dead.

Much better to put swap on several RAID-1 volumes if
you want to spread it around.  Disks just aren't that
expensive anymore.  RAID-5 though would be a bad move since
swap gets an order of magnitude more writes than reads.  On
account of the heavy write tendencies i lean toward
so-called hardware RAID for swap in order to offload the PCI
buss.

-- 
________________________________________________________________
	J.W. Schultz            Pegasystems Technologies
	email address:		jw@pegasys.ws

		Remember Cernan and Schmitt

  reply	other threads:[~2002-07-02 10:24 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-01 14:04 lilo/raid? Roy Sigurd Karlsbakk
2002-07-01 15:52 ` lilo/raid? Bill Davidsen
2002-07-01 16:02   ` lilo/raid? Roy Sigurd Karlsbakk
2002-07-01 18:36     ` lilo/raid? Bill Davidsen
2002-07-01 15:59 ` lilo/raid? Andries Brouwer
2002-07-01 16:15   ` lilo/raid? Roy Sigurd Karlsbakk
2002-07-01 15:59     ` lilo/raid? Zwane Mwaikambo
2002-07-02  8:16       ` lilo/raid? Helge Hafting
2002-07-02  9:12         ` lilo/raid? Zwane Mwaikambo
2002-07-02 10:26           ` jw schultz [this message]
2002-07-02 10:28           ` lilo/raid? Jakob Oestergaard
2002-07-02 11:33         ` lilo/raid? Roy Sigurd Karlsbakk
2002-07-03  9:43           ` lilo/raid? Helge Hafting
2002-07-03 10:02             ` lilo/raid? Roy Sigurd Karlsbakk
2002-07-02 11:27       ` lilo/raid? Roy Sigurd Karlsbakk
2002-07-01 16:05 ` lilo/raid? Fabio Massimo Di Nitto
2002-07-01 16:07   ` lilo/raid? Roy Sigurd Karlsbakk

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=20020702032627.D28771@pegasys.ws \
    --to=jw@pegasys.ws \
    --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.