From: Daniel Reurich <daniel@centurion.net.nz>
To: linux-raid <linux-raid@vger.kernel.org>
Subject: Raid Containers
Date: Thu, 25 Mar 2010 10:27:09 +1300 [thread overview]
Message-ID: <1269466029.5759.668.camel@localhost.localdomain> (raw)
Hi.
I'm wanting to know are containers properly supported now in mdadm and
recent kernels (I assume using only 1.X metadata)?
I'm wondering if containers might make a better approach than
partitioning and creating separate raid volumes. My thoughts are that
maybe using containers potentially simplify the management of drives, to
simply adding new or replacement drives to the raid container and having
them added into degraded arrays automatically or as spares (for live
migration when it gets implemented).
Is there any more documentation around on the usage of containers in md?
Thanks,
Daniel Reurich
--
Daniel Reurich.
Centurion Computer Technology (2005) Ltd
Mobile 021 797 722
next reply other threads:[~2010-03-24 21:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-24 21:27 Daniel Reurich [this message]
2010-03-24 22:22 ` Raid Containers Neil Brown
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=1269466029.5759.668.camel@localhost.localdomain \
--to=daniel@centurion.net.nz \
--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).