linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: martin f krafft <madduck@madduck.net>
To: linux-raid mailing list <linux-raid@vger.kernel.org>
Subject: why partition arrays?
Date: Wed, 18 Oct 2006 14:42:25 +0200	[thread overview]
Message-ID: <20061018124225.GA23653@piper.madduck.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 1688 bytes --]

As the Debian mdadm maintainer, I am often subjected to questions
about partitionable arrays; people seem to want to use them in
favour of normal arrays. I don't understand why.

There's possibly an argument to be made about flexibility when it
comes to resizing partitions within the array, but even most MD
array types can be resized now.

There's possibly an argument about saving space because of fewer
sectors used/wasted with superblock information, but I am not going
to buy that.

Why would anyone want to create a partitionable array and put
partitions in it, rather than creating separate arrays for each
filesystem? Intuitively, this makes way more sense as then the
partitions are independent of each other; one array can fail and the
rest still works -- part of the reason why you partition in the
first place.

Would anyone help me answer this FAQ?

(btw: [0] and [1] are obviously for public consumption; they are
available under the terms of the artistic licence 2.0)

0. http://svn.debian.org/wsvn/pkg-mdadm/mdadm/trunk/debian/FAQ?op=file&rev=0&sc=0
1. http://svn.debian.org/wsvn/pkg-mdadm/mdadm/trunk/debian/README.recipes?op=file&rev=0&sc=0

-- 
martin;              (greetings from the heart of the sun.)
  \____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck
 
spamtraps: madduck.bogus@madduck.net
 
"the liar at any rate recognises that recreation, not instruction, is
 the aim of conversation, and is a far more civilised being than the
 blockhead who loudly expresses his disbelief in a story which is told
 simply for the amusement of the company."
                                                        -- oscar wilde

[-- Attachment #2: Digital signature (GPG/PGP) --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2006-10-18 12:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-18 12:42 martin f krafft [this message]
2006-10-18 13:26 ` why partition arrays? Doug Ledford
2006-10-18 13:43   ` martin f krafft
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=20061018124225.GA23653@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).