From: Wols Lists <antlists@youngman.org.uk>
To: "David C. Rankin" <drankinatty@suddenlinkmail.com>,
mdraid <linux-raid@vger.kernel.org>
Subject: Re: Setup Recommendation on UEFI/GRUB/RAID1/LVM
Date: Thu, 16 Apr 2020 12:16:03 +0100 [thread overview]
Message-ID: <5E983E73.8010309@youngman.org.uk> (raw)
In-Reply-To: <461be4bb-a86b-dca0-605f-cda13bc1602d@suddenlinkmail.com>
On 16/04/20 02:50, David C. Rankin wrote:
> On 04/14/2020 09:20 AM, Wols Lists wrote:
>> That's true, but is it worth it? RAM is cheap, max out your motherboard,
>> and try and avoid falling into swap at all. I have one swap partition
>> per disk, but simply set them up as equal priority so the kernel does
>> its own raid-0 stripe across them. Yes a disk failure would kill any
>> apps swapped on to that disk, but my system rarely swaps...
>
> That's a neat approach, I do it just the opposite and care RAID1 partitions
> for swap (though I rarely swap as well). I've never had an issue restarting
> after a failure (or me doing something dumb like hitting the wrong button on
> the UPS)
>
> So that I'm understanding, you simply create a swap partition on each disk not
> part of an array, swapon both and let the kernel decide?
>
Don't forget the mount option "pri=1" ... the following is the relevant
lines from my fstab ...
# /dev/sda2 none swap sw,pri=1 0 0
UUID=184b6322-eb42-405e-b958-e55014ce3691 none swap sw,pri=1
0 0
# /dev/sdb2 none swap sw,pri=1 0 0
UUID=48913c8d-e4c4-482d-9733-e44be3889f07 none swap sw,pri=1
0 0
# /dev/sdc2 none swap sw,pri=1 0 0
If you don't use the priority option, each partition is allocated a
different priority and it fills them up one after the other (raid
linear). Make them all equal priority, and it'll stripe them.
Cheers,
Wol
next prev parent reply other threads:[~2020-04-16 11:16 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-14 13:02 Setup Recommendation on UEFI/GRUB/RAID1/LVM Stefanie Leisestreichler
2020-04-14 14:20 ` Wols Lists
2020-04-14 14:27 ` Reindl Harald
2020-04-14 15:12 ` Stefanie Leisestreichler
2020-04-14 17:35 ` Wols Lists
2020-04-14 19:13 ` Stefanie Leisestreichler
2020-04-14 19:36 ` Wols Lists
2020-04-17 23:06 ` Nix
2020-04-20 9:23 ` Stefanie Leisestreichler
2020-04-20 9:45 ` Stefanie Leisestreichler
2020-04-20 11:05 ` Nix
2020-04-20 12:01 ` Stefanie Leisestreichler
2020-04-16 1:50 ` David C. Rankin
2020-04-16 11:16 ` Wols Lists [this message]
2020-04-16 1:58 ` David C. Rankin
2020-04-14 16:00 ` G
2020-04-14 16:14 ` Stefanie Leisestreichler
2020-04-17 23:10 ` Nix
2020-04-24 19:15 ` Phillip Susi
2020-04-24 20:24 ` Nix
2020-04-14 16:20 ` Reindl Harald
2020-04-14 16:41 ` Stefanie Leisestreichler
2020-04-16 17:00 ` G
2020-04-14 18:14 ` Phillip Susi
2020-04-14 19:00 ` Stefanie Leisestreichler
2020-04-14 20:05 ` antlists
2020-04-17 23:24 ` Nix
[not found] ` <394a3255-251c-41d1-8a65-2451e5503ef9@teksavvy.com>
2020-04-15 15:53 ` Stefanie Leisestreichler
2020-04-15 16:10 ` Stefanie Leisestreichler
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=5E983E73.8010309@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=drankinatty@suddenlinkmail.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).