public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Denis Vlasenko <vda.linux@googlemail.com>,
	Michael Tokarev <mjt@tls.msk.ru>,
	Helge Hafting <helge.hafting@aitel.hist.no>,
	Marc Perkel <marc@perkel.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Raid 0 Swap?
Date: Sun, 31 Dec 2006 21:08:45 -0500	[thread overview]
Message-ID: <45986D2D.8090009@tmr.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0612281011530.15825@yvahk01.tjqt.qr>

Jan Engelhardt wrote:
> On Dec 28 2006 00:06, Mike Huber wrote:
>> I would like to point out one key argument against raid0 swap partitions,
>> which is that, should a drive failure occur, the least used programs in
>> memory are most drastically affected.  Unfortunately, in the case of a
>> drastic drive failure in a standalone server, one of the most likely
>> programs to be affected is getty, disallowing you from manually logging in.
> 
> However, the footprint of getty is rather small, so its chance to run is higher
> than an idle bigger task (dbus, resmgr, hal, perhaps cron or X)

RAID-0 swap is not the thing to run if reliability is a must, clearly. 
Interestingly, after a long fight with poor RAID-5 write speed, I moved 
my swap to RAID-10, only to find that recovery disks don't know how to 
use it. Tried Fedora and then a live CD (puppy, I think).

Detail on the RAID-5 performance thing in the linux-raid archives, won't 
rehash here.
-- 
bill davidsen <davidsen@tmr.com>
   CTO TMR Associates, Inc
   Doing interesting things with small computers since 1979

  reply	other threads:[~2007-01-01  2:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-03 22:43 Raid 0 Swap? Marc Perkel
2006-09-04  0:16 ` Bernd Eckenfels
2006-09-04  7:06 ` Michael Tokarev
2006-09-04  9:47   ` Helge Hafting
2006-09-04 10:29     ` Michael Tokarev
2006-09-04 10:46       ` Jan Engelhardt
2006-09-18  9:50         ` Denis Vlasenko
     [not found]           ` <e1a7ee0c0612272106y5e22dd21uc3f2fde567ab7532@mail.gmail.com>
2006-12-28  9:13             ` Jan Engelhardt
2007-01-01  2:08               ` Bill Davidsen [this message]
2006-09-04 15:29   ` Valdis.Kletnieks
2006-09-04 20:06     ` Bernd Eckenfels
2006-09-05 13:37       ` Helge Hafting
2006-09-05 23:44   ` Bill Davidsen
2006-09-06  6:53     ` Michael Tokarev
2006-09-06 17:21     ` Kyle Moffett
     [not found] <6R8WW-70v-7@gated-at.bofh.it>
     [not found] ` <6RgKP-1OA-9@gated-at.bofh.it>
2006-09-04 13:21   ` Bodo Eggert

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=45986D2D.8090009@tmr.com \
    --to=davidsen@tmr.com \
    --cc=helge.hafting@aitel.hist.no \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc@perkel.com \
    --cc=mjt@tls.msk.ru \
    --cc=vda.linux@googlemail.com \
    /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