From: Another Sillyname <anothersname@googlemail.com>
To: linux-raid@vger.kernel.org
Subject: Re: Fwd: Installing Linux directly onto RAID6 Array...........
Date: Tue, 26 May 2015 12:18:09 +0100 [thread overview]
Message-ID: <CAOS+5GHWktYuV2Q7NhsqybgFY5-QKRaGih0YcerD08_rKZp4Ng@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1505261005260.9487@uplift.swm.pp.se>
Mikael
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.
On 26 May 2015 at 09:06, Mikael Abrahamsson <swmike@swm.pp.se> wrote:
> On Tue, 26 May 2015, Another Sillyname wrote:
>
>> Not bothered about raiding the swap thanks, my way will suffice as it
>> gives me maximum flexibility and resilience......I'm not really
>> performance driven on this project.
>
>
> I don't see how running swap natively on the drives gives "maximum
> resilience". Higher resilience is gained by running raid1 for swap.
>
>
> --
> Mikael Abrahamsson email: swmike@swm.pp.se
next prev parent reply other threads:[~2015-05-26 11:18 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 [this message]
2015-05-26 14:08 ` Mikael Abrahamsson
2015-05-26 20:11 ` Wols Lists
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=CAOS+5GHWktYuV2Q7NhsqybgFY5-QKRaGih0YcerD08_rKZp4Ng@mail.gmail.com \
--to=anothersname@googlemail.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 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).