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: If separate md for /boot, OS, and /srv, must 'create' on disks with 3 partns?
Date: Sun, 19 Jan 2014 18:39:41 +0000	[thread overview]
Message-ID: <52DC1BED.7070901@tesco.net> (raw)

List, may I ask a query about partitions?

Our objective is to run a Debian Wheezy system as a data server using 
an LVM on top of 2 x 3TB discs in RAID-1 configuration.  A first 
attempt had the whole discs used for the data filesystem, using a 
single /dev/md(n), on whole unpartitioned disks.  We've dismantled 
that because of filesystem size problems (it had used only 2TB disks) 
and will make a second attempt and additionally, this time, we want to 
use the array for 3 purposes:

(a) Boot with Grub
(b) Hold the OS
(c) Use the remainder of the disk for the data server, on which we'll 
install an LVM and later grow that with another 2 x 3TB disks.

Assuming I am correct in needing something such as:

/dev/md0 for Grub, (and copied to both physical disks of the RAID-1)
/dev/md1 for the OS, and
/dev/md2 for the data files (on which we'll install the LVM)

then I think we need to partition our disks before creating the array. 
  Is that correct?

The wiki ( https://raid.wiki.kernel.org/index.php/Partition_Types , 
and https://raid.wiki.kernel.org/index.php/RAID_setup#General_setup ) 
is relatively silent on the 'numbers' of partitions that could or 
should be used, if creating a raid on new discs in the circumstances 
where boot 'partitions' and separate OS 'partitions' might be needed. 
  I couldn't see anything in man mdadm to guide me, either, but I 
could have missed something and apologies if I have.

Should I proceed to partition the disks, and then create 3 RAID-1 
arrays (one on each partition-pair), or should I use a different 
technique/layout to hold Grub, the OS, and an expandable LV for the 
datafiles?

I had always assumed that /dev/md(x) always mapped to /dev/sda(y), but 
I have a faint recollection that a discussion on the list a year or so 
ago had suggested that that mapping was not cast in stone, and 
multiple partitions on the physical devices were neither necessary nor 
desirable.  Grateful for any comment,  Ron


             reply	other threads:[~2014-01-19 18:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-19 18:39 Ron Leach [this message]
2014-01-19 20:46 ` If separate md for /boot, OS, and /srv, must 'create' on disks with 3 partns? 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
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=52DC1BED.7070901@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).