public inbox for linux-raid@vger.kernel.org
 help / color / mirror / Atom feed
From: Wols Lists <antlists@youngman.org.uk>
To: Phil Turmel <philip@turmel.org>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: Linux raid wiki - setting up a system - advice wanted :-)
Date: Mon, 26 Sep 2016 16:48:09 +0100	[thread overview]
Message-ID: <57E94339.4060504@youngman.org.uk> (raw)
In-Reply-To: <e5651061-1404-30be-2777-9ae02a640f42@turmel.org>

On 26/09/16 15:13, Phil Turmel wrote:
> On 09/26/2016 02:50 AM, Wols Lists wrote:
> 
>> Bare metal -> raid [-> lvm] -> /
>>
>> Is there any room on the disk to install grub?
> 
> No.

Ten out of ten. Thanks.

(Hint to examinees - please answer the question on the paper, not the
question you want to answer :-)
> 
>> (Note that - and I know you shouldn't believe everything you read on the
>> internet - apparently Neil Brown prefers passing the entire
>> unpartitioned disk to raid ...)
> 
> I'm with Neil for my large arrays.  I partition a pair of SSDs for UEFI
> boot and a raid mirror holding an LVM volume group for the OS.  All
> other drives are unpartitioned, given entirely to a raid6 w/ a small
> chunk size (16k lately).  A separate LVM volume group on top of that.
> 
> ( I no longer use any bootloader, either, as UEFI will boot a kernel
> directly that's been built with EFI_STUB and a nested initramfs. )
> 
That's good to know. I don't have any experience with UEFI as yet, so I
can document that as a hint to others.

Cheers,
Wol


  reply	other threads:[~2016-09-26 15:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-25 21:16 Linux raid wiki - setting up a system - advice wanted :-) Wols Lists
2016-09-26  0:59 ` Francisco Parada
2016-09-26  8:17   ` keld
2016-09-26  2:16 ` Andreas Klauer
2016-09-26  3:40   ` Adam Goryachev
2016-09-26  6:50   ` Wols Lists
2016-09-26 14:13     ` Phil Turmel
2016-09-26 15:48       ` Wols Lists [this message]
2016-09-26  9:30 ` keld

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=57E94339.4060504@youngman.org.uk \
    --to=antlists@youngman.org.uk \
    --cc=linux-raid@vger.kernel.org \
    --cc=philip@turmel.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