linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wols Lists <antlists@youngman.org.uk>
To: Mikael Abrahamsson <swmike@swm.pp.se>,
	Another Sillyname <anothersname@googlemail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Fwd: Installing Linux directly onto RAID6 Array...........
Date: Tue, 26 May 2015 21:11:31 +0100	[thread overview]
Message-ID: <5564D373.30705@youngman.org.uk> (raw)
In-Reply-To: <alpine.DEB.2.02.1505261605450.9487@uplift.swm.pp.se>

On 26/05/15 15:08, Mikael Abrahamsson wrote:
> On Tue, 26 May 2015, Another Sillyname wrote:
> 
>> Very easy to understand......any way that requires entering the swaps
>> into /etc/fstab therefore means that if any drive and it's contained
>> swap fails the reboot can fail (plus the overhead of all those uuid
>> numbers in fstab).  My way means that as the swaps don't get loaded
>> unless the drive is alive the reboot has more resilience.
> 
> If you have RAID1 for swap, you only need a single component drive to
> work for the RAID1 to be able to start. It also means any drive can fail
> and your swap information still works.

And you're wasting a lot of disk space. What's important to you (that a
live swap disk shouldn't fail) is not important to me and doesn't seem
to be important to Another Sillyname.

My disk drives have 32Gb swap partitions. Overkill? Dunno. But I'd
rather linux raid 0's them for 64Gb swap than mdadm raid 1's them for
32Gb swap. I have a couple of 20Gb tmpfs partitions :-)

I don't know why Another Sillyname wants to chain his swap partitions,
but it's his choice. Maybe like me, his system gets rebooted a couple of
times a day, and failure to start is a far more real risk than failure
in use. He's running Fedora - that seems likely then ...

Cheers,
Wol

  reply	other threads:[~2015-05-26 20:11 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-12 10:08 Installing Linux directly onto RAID6 Array Another Sillyname
2015-05-12 10:20 ` Rudy Zijlstra
2015-05-12 12:20   ` Phil Turmel
2015-05-12 12:31     ` Roman Mamedov
     [not found]       ` <CAOS+5GHhUoYxTTYOWU7cdN6GSdffSMGrhWHU5ZtWEjc4jEm3eg@mail.gmail.com>
2015-05-12 13:12         ` Fwd: " Another Sillyname
2015-05-12 13:42           ` Roman Mamedov
2015-05-12 13:27 ` Wilson, Jonathan
2015-05-12 14:05   ` Another Sillyname
2015-05-13  0:02 ` Adam Goryachev
     [not found]   ` <CAOS+5GEP6+7OAHkqQjeyGHAB5u-_-Vq2JWGpcOemYHdCjmR5Lg@mail.gmail.com>
2015-05-24  1:18     ` Fwd: " Another Sillyname
2015-05-24  8:36       ` Mikael Abrahamsson
2015-05-24  9:08         ` Another Sillyname
2015-05-24  9:46           ` Mikael Abrahamsson
2015-05-24 10:07             ` Another Sillyname
2015-05-24 10:35               ` Mikael Abrahamsson
2015-05-24 10:42                 ` Another Sillyname
2015-05-26  8:29           ` NeilBrown
2015-05-26 13:18             ` Another Sillyname
2015-05-24 11:12         ` Fwd: " Wols Lists
2015-05-24 11:57           ` Brad Campbell
2015-05-24 12:41             ` Wols Lists
2015-05-24 13:48               ` Brad Campbell
2015-05-24 14:06               ` Mikael Abrahamsson
2015-05-24 14:53                 ` Wols Lists
2015-05-24 14:57                   ` Mikael Abrahamsson
2015-05-25 21:03                     ` Another Sillyname
2015-05-25 23:20                       ` Wols Lists
2015-05-26  7:08                         ` Another Sillyname
2015-05-26  8:06                           ` Mikael Abrahamsson
2015-05-26 11:18                             ` Another Sillyname
2015-05-26 14:08                               ` Mikael Abrahamsson
2015-05-26 20:11                                 ` Wols Lists [this message]
2015-05-26 21:02                                   ` Another Sillyname
2015-05-27  4:59                                   ` Mikael Abrahamsson

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=5564D373.30705@youngman.org.uk \
    --to=antlists@youngman.org.uk \
    --cc=anothersname@googlemail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=swmike@swm.pp.se \
    /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).