linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ron Leach <ronleach@tesco.net>
To: Linux RAID Mailing List <linux-raid@vger.kernel.org>
Subject: Re: If separate md for /boot, OS, and /srv, must 'create' on disks with 3 partns?
Date: Mon, 20 Jan 2014 19:07:40 +0000	[thread overview]
Message-ID: <52DD73FC.7000801@tesco.net> (raw)
In-Reply-To: <52DD6B20.5030906@turmel.org>

On 20/01/2014 18:29, Phil Turmel wrote:
>
> Let me clarify:  /dev/md0 should be a v0.90 or v1.0 raid1 for /boot, no LVM.
 >
 > /dev/md1 is an LVM PV for the OS.


Ok.  That means I need physical partitions for those, on each of the 
drives.

Since I am using 3TB drives, I'll need to use a GPT which, if I 
understand correctly, requires to reveal a dummy 'partition' to make 
the BIOS think there is a boot sector thingy there.

So I'm assuming to pre-partition the physical devices this way:

/dev/sd[x]1 - 64k (? I'm checking the docs) empty, for BIOS to see
/dev/sd[x]2 - 128 MB /boot v0.90/v1.0 RAID1, /dev/md0
/dev/sd[x]3 - remainder ~3 TB for LVM, v1.2 RAID1, /dev/md1

and then make the two RAID1s, and then create the LVM.

>
>
> Having root in an LVM allows strange things like relocating and/or
> resizing it on the fly.  Particularly handy if physical access is difficult.
>

Yes, it was that potential aspect that set me deciding to try your 
approach.  Functional demands on our systems keep changing.

Much appreciated, Ron

  reply	other threads:[~2014-01-20 19:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-19 18:39 If separate md for /boot, OS, and /srv, must 'create' on disks with 3 partns? Ron Leach
2014-01-19 20:46 ` Phil Turmel
2014-01-19 21:29   ` David Brown
2014-01-20 16:53   ` Ron Leach
2014-01-20 18:29     ` Phil Turmel
2014-01-20 19:07       ` Ron Leach [this message]
2014-01-21  8:02         ` Wilson Jonathan

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=52DD73FC.7000801@tesco.net \
    --to=ronleach@tesco.net \
    --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).