From: martin f krafft <madduck@madduck.net>
To: linux-raid mailing list <linux-raid@vger.kernel.org>
Subject: Re: why partition arrays?
Date: Wed, 18 Oct 2006 15:43:22 +0200 [thread overview]
Message-ID: <20061018134322.GA910@piper.madduck.net> (raw)
In-Reply-To: <1161178012.2917.529.camel@fc6.xsintricity.com>
[-- Attachment #1: Type: text/plain, Size: 908 bytes --]
also sprach Doug Ledford <dledford@redhat.com> [2006.10.18.1526 +0200]:
> There are a couple reasons I can think.
Thanks for your elaborate response. If you don't mind, I shall link
to it from the FAQ.
I have one other question: do partitionable and traditional arrays
actually differ in format? Put differently: can I assemble
a traditional array as a partitionable one simply by specifying:
mdadm --create ... /dev/md0 ...
mdadm --stop /dev/md0
mdadm --assemble --auto=part ... /dev/md0 ...
? Or do the superblocks actually differ?
Thanks,
--
martin; (greetings from the heart of the sun.)
\____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck
spamtraps: madduck.bogus@madduck.net
the images rushed around his mind and tried
to find somewhere to settle down and make sense.
-- douglas adams, "the hitchhiker's guide to the galaxy"
[-- Attachment #2: Digital signature (GPG/PGP) --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-10-18 13:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-18 12:42 why partition arrays? martin f krafft
2006-10-18 13:26 ` Doug Ledford
2006-10-18 13:43 ` martin f krafft [this message]
2006-10-18 21:42 ` Doug Ledford
2006-10-23 15:59 ` Mario 'BitKoenig' Holbe
-- strict thread matches above, loose matches on Subject: below --
2006-10-19 11:25 Ken Walker
2006-10-19 15:46 ` Doug Ledford
2006-10-21 4:26 ` Bodo Thiesen
2006-10-21 13:39 ` Henrik Holst
2006-10-21 19:25 ` Bodo Thiesen
2006-10-24 23:31 ` Bill Davidsen
2006-10-25 0:10 ` dean gaudet
2006-10-22 16:02 ` Nix
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=20061018134322.GA910@piper.madduck.net \
--to=madduck@madduck.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).