From: Matti Aarnio <matti.aarnio@zmailer.org>
To: Riley Williams <Riley@Williams.Name>
Cc: Derek Yeung <dky@utcc.utoronto.ca>, linux-raid@vger.kernel.org
Subject: Re: Mirroring swap
Date: Thu, 26 Jun 2003 10:30:03 +0300 [thread overview]
Message-ID: <20030626073003.GJ28900@mea-ext.zmailer.org> (raw)
In-Reply-To: <BKEGKPICNAKILKJKMHCAEEFPEHAA.Riley@Williams.Name>
On Thu, Jun 26, 2003 at 08:07:47AM +0100, Riley Williams wrote:
> Hi Derek.
> > I'm running Red Hat 9 on stock kernel 2.4.20 with software
> > RAID 1.
> >
> > I was wondering if it's a good idea to also mirror the swap
> > partition? I was reading old posts in the newsgroups that
> > suggest this may not be a good idea but I can't seem to find
> > an answer as to why. I think mirroring swap would be a good
> > idea as it would increase redundancy. Any thoughts?
>
> Personally, I can't see the point. the contents of swap are by
> definition short term temporary data with copies held either in
> memory or elsewhere on the hard disk subsystem.
I do that mirroring routinely.
What Linux sends to swap has _no_ origin in anywhere else in
the system, e.g. shared library loading makes runtime modifications
into loaded program, modifications to RW DATA segment, and
of course the BSS segment, and all of heap, and stack...
Most of the executable will usually stay unmodified, and be
backed by its on-disk version, but never everything.
...
> Remember that using a raided swap partition means that the swap
> code has no idea which drive any particular part of that swap
> partition is on, so could result in the swap copy being on the
> same failed drive as the original copy.
Nope. swap-code does not see it at all. All of that is hidden with
under the mirroring code, and it does disconnect faulted drive from
the mirror set.
> Best wishes from Riley.
/Matti Aarnio
next prev parent reply other threads:[~2003-06-26 7:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-25 19:39 Mirroring swap Derek Yeung
2003-06-26 7:07 ` Riley Williams
2003-06-26 7:30 ` Matti Aarnio [this message]
2003-06-26 8:30 ` Gordon Henderson
2003-06-26 21:23 ` Gregory Leblanc
2003-06-26 21:44 ` Corey McGuire
2003-06-27 1:56 ` Scott McDermott
2003-06-27 2:14 ` Corey McGuire
2003-06-27 2:24 ` Scott McDermott
[not found] ` <200306261957360966.057B8F63@ilneval.coreyfro.com>
2003-06-27 3:22 ` Corey McGuire
2003-06-27 16:17 ` Ricky Beam
2003-06-27 18:04 ` Show me the cache, was " Corey McGuire
2003-06-27 18:24 ` Ricky Beam
2003-06-27 23:31 ` Corey McGuire
2003-06-27 8:49 ` Gordon Henderson
2003-06-26 9:46 ` Scott McDermott
-- strict thread matches above, loose matches on Subject: below --
2003-06-25 19:58 Bailey, Scott
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=20030626073003.GJ28900@mea-ext.zmailer.org \
--to=matti.aarnio@zmailer.org \
--cc=Riley@Williams.Name \
--cc=dky@utcc.utoronto.ca \
--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