All of lore.kernel.org
 help / color / mirror / Atom feed
From: Iordan Iordanov <iordan@cdf.toronto.edu>
To: Joe Landman <joe.landman@gmail.com>
Cc: NeilBrown <neilb@suse.de>,
	"Mathias Burén" <mathias.buren@gmail.com>, b2 <b2@playtime.bg>,
	linux-raid@vger.kernel.org
Subject: Re: debian software raid1
Date: Wed, 20 Apr 2011 10:51:29 -0400	[thread overview]
Message-ID: <4DAEF2F1.8080204@cdf.toronto.edu> (raw)
In-Reply-To: <4DAE29EA.4040306@gmail.com>

Hi Joe,

On 04/19/11 20:33, Joe Landman wrote:
> This gets to my question, since we haven't tried this yet ... can we do
> whole device MD RAIDs, and boot from them? Is there anything special we
> need to do in their construction (use --auto=mdp or similar)? We'd
> really prefer to go this route rather than building multiple smaller
> RAIDs. We can manage the latter, but the former is far easier/cleaner to
> handle rebuilds with.

A few days ago (just before this thread started, coincidentally), I 
converted a single drive system to RAID1 by adding a second disk, and 
raiding the whole drive. This does have the drawback that any 
replacement drives have to be the same size or bigger than what you had 
to begin with. I am running Ubuntu 10.04.

A few things I had to make sure, and I disclaim that this is not an 
exhaustive list. I created the array and named it /dev/md0. Then, I had 
to do:

1) mdadm --examine --scan > /etc/mdadm/mdadm.conf
2) Rebuild initrd, so that upon boot the array will be assembled 
automatically based on this mdadm.conf. On Debian/Ubuntu, this can be 
done with update-initramfs.

When you partition /dev/md0 with whatever partitioner you prefer, the 
kernel does see the partitions, and makes /dev/md0pN for partition 
number N. Hence you can use these to mount/start swap.

For the record, I have been suspending/resuming that Ubuntu 10.04 with 
swap living on one of the RAID1 partitions with no ill effect, and will 
revisit this thread if I ever do experience issues!

Also, I was thinking of switching from RAID1 to RAID10 with near layout 
and two copies (effectively RAID1) in order to get faster reads - 
anybody have any opinion on this?

Cheers everyone, and thanks for all the discussion!
Iordan

  parent reply	other threads:[~2011-04-20 14:51 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-19 12:12 debian software raid1 b2
2011-04-19 12:25 ` Mathias Burén
2011-04-19 16:03   ` Iordan Iordanov
2011-04-19 21:10     ` Gordon Henderson
2011-04-19 21:33       ` Steven Haigh
2011-04-19 22:01         ` Roberto Spadim
2011-04-19 22:05           ` Mathias Burén
2011-04-19 22:51     ` NeilBrown
2011-04-20  0:33       ` Joe Landman
2011-04-20  1:12         ` NeilBrown
2011-04-20 14:59           ` Iordan Iordanov
2011-04-20 14:51         ` Iordan Iordanov [this message]
2011-04-21  6:15           ` Luca Berra
2011-04-21 14:50             ` Iordan Iordanov
2011-04-22  5:59               ` Luca Berra
2011-04-22 19:19                 ` Iordan Iordanov
2011-04-22 19:28                   ` Mikael Abrahamsson
2011-04-23  0:07                     ` Iordan Iordanov
2011-04-20 10:28       ` Asdo
2011-04-20 12:40         ` NeilBrown
2011-04-23  8:33     ` Jan Ceuleers
2011-04-22 19:21 ` Iordan Iordanov
2011-04-22 22:12   ` NeilBrown
2011-04-23  0:05     ` Iordan Iordanov
2011-04-23 12:54       ` David Brown
2011-04-23 14:23       ` Keld Jørn Simonsen

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=4DAEF2F1.8080204@cdf.toronto.edu \
    --to=iordan@cdf.toronto.edu \
    --cc=b2@playtime.bg \
    --cc=joe.landman@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=mathias.buren@gmail.com \
    --cc=neilb@suse.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.