All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Brown <david.brown@hesbynett.no>
To: linux-raid@vger.kernel.org
Subject: Re: Any pros or cons of using full disk versus partitons?
Date: Wed, 13 Apr 2011 22:55:03 +0200	[thread overview]
Message-ID: <io52j7$cg4$1@dough.gmane.org> (raw)
In-Reply-To: <20110413.132112.102552472.davem@davemloft.net>

On 13/04/11 22:21, David Miller wrote:
> From: "Matthew Tice"<mjtice@gmail.com>
> Date: Wed, 13 Apr 2011 13:38:39 -0600
>
>> So of course it technically doesn't matter but are there certain
>> (non-apparent) repercussions for choosing one over the other?  It seems to
>> save a couple steps by using the whole disk (not having to partition) - but
>> is that it?  One thing I'm thinking about the pros of using partitions is if
>> all your disks (or some) are different sizes - then you can set the
>> partition sizes the same.
>
> First, you sent this to "linux-raid-owner" instead of just
> "linux-raid".  The former goes to me, not to the mailing list.
>
> I've corrected it in the CC:
>
> Second, to answer your question, for some disk label variants you
> risk over-writing the disk label if you use the whole device
> as part of your RAID volume.  This definitely will happen, for
> example, with Sun disk labels.

Using whole disks in the raid will make it easier for replacing disks - 
you don't have to worry about partitioning them.  You can just plug them 
in and use them.  If you have some sort of monitoring scripts and hot 
plug disks, you may be able to avoid any interaction at all on disk 
replacement.

On the other hand, using partitions gives you lots more flexibility. 
You can do things such as use a small partition on each disk to form a 
raid10 array for swap, while using a bigger partition for data.  Or 
perhaps you want a very small partition on each disk as a wide raid1 
mirror, for your /boot (not that you need so much safety for /boot, but 
that it's easier to boot from a raid1 with metadata format 0.90 than 
from other raid types).



  reply	other threads:[~2011-04-13 20:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <07a801cbfa12$64b8a950$2e29fbf0$@gmail.com>
2011-04-13 20:21 ` Any pros or cons of using full disk versus partitons? David Miller
2011-04-13 20:55   ` David Brown [this message]
2011-04-14  7:57     ` CoolCold
2011-04-14  8:11       ` NeilBrown
2011-04-14  8:30         ` Roman Mamedov
2011-04-14 10:23           ` Mikael Abrahamsson

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='io52j7$cg4$1@dough.gmane.org' \
    --to=david.brown@hesbynett.no \
    --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 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.